{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreia5abaxid7mci4f3xue6bmk6oly3trw34an6p5fgdk64dmos3lzgi",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mkhgwbq6z652"
  },
  "path": "/t/pre-rfc-dns-domains-as-package-namespaces/24202?page=2#post_21",
  "publishedAt": "2026-04-27T06:22:50.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "crates.io"
  ],
  "textContent": "> While it's not _likely_ that the domains will lapse, it is definitely something that needs to be considered as an inevitability for _something_ .\n\nI think the exact details of the policy for guarding against lapsed domains for major projects would make for a great section in the eventual RFC, if this thread ever gets to the point where an RFC gets written. It may involve some combination of associating namespaces with a set of crates.io users / teams allowed to push to those namespaces, a non-GitHub source of truth for crates.io teams, and/or requiring 2FA for namespaced crates.\n\nHowever, right now, this thread is a pre-RFC because I don't know whether the Cargo or crates.io teams are OK with any form of namespaces. Any brain power spent pondering what to do if `tokio.rs` expires is wasted if I can't convince the relevant authorities that the packages `xml` and `example.com/xml` should be allowed to coexist.",
  "title": "[Pre-RFC] DNS domains as package namespaces"
}