this post was submitted on 17 Oct 2024
50 points (96.3% liked)

Rust

6023 readers
1 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

[email protected]

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago
MODERATORS
 

It's possible that the .io cctld is going to go away [0]. Does crates.io have a backup plan at all? Does anyone know what problems it would end up causing?

I imagine the package registry having to move domains is going to cause a ton of problems.

Frankly, it's concerning to me that so much of the Rust ecosystem has chosen to standardize on shaky ccTLDs. The Indian Ocean Territory (.io) is a small island territory whose only inhabitants are a single military base, it is crazy to use that domain for something important. Serbia (.rs) is more stable, but they could still cut off access for non-Serbians if they wanted to.

[0] - https://en.wikipedia.org/wiki/.io#Phasing_Out

you are viewing a single comment's thread
view the rest of the comments
[–] BatmanAoD 8 points 1 month ago (10 children)

Obviously this isn't specific to Rust, but frankly it's bizarre to me that ICANN chose to tie top-level domains to country codes in the first place. Languages might have made sense, but a major feature of the internet is that it's less beholden to political boundaries than most of the physical world is.

[–] jeff 6 points 1 month ago (2 children)

It makes a lot of sense for businesses, especially where different countries might have different regulations. E.g., amazon.ca and amazon.in. Both sites are in English but it makes way more sense to split them up by country.

[–] BatmanAoD 1 points 1 month ago (1 children)

Why top-level, though? Why not amazon.in.com?

[–] nebeker 2 points 1 month ago

Interestingly enough, you also have amazon.co.uk, which combines the nature (commercial) and location served (UK), but in the opposite order.

load more comments (7 replies)