{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihfec5aqkrgxifztlx7qckbgymyozx2vhtc6fujtz6fssov4klqna",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mkibraslvyd2"
  },
  "path": "/t/pre-rfc-dns-domains-as-package-namespaces/24202?page=2#post_22",
  "publishedAt": "2026-04-27T14:17:56.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "crates.io",
    "Child Thread: Survey of registry namespace designs for Cargo and Crates.io"
  ],
  "textContent": "jmillikin:\n\n> However, 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.\n\nThe problem isn't the concept of namespaces but solving the very problems being raised in this thread. I've already called this out before. Most of these concerns were included in Child Thread: Survey of registry namespace designs for Cargo and Crates.io which I was expecting your reply to cover.\n\nI'd also recommend posting relevant content on the relevant threads from that previous summary and focus your points on your incremental differences so people can more easily identify and talk to what is new you are bringing to the table rather than having to sift it out of long, detailed posts. Even knowing content is present in your post, it is hard to find.\n\njmillikin:\n\n> A cheap `.com` is like $15 a year, and these namespaces are _optional_.\n\nDismissing it as \"small\" I think says more about you then the problem.\n\nBeing \"optional\" is an escape hatch proportionate with the expected value. We would be rolling out a major feature to address a problem but those without a domain name would not be able to participate.\n\njmillikin:\n\n> If someone doesn't want to pay a DNS registrar then they can use a free host like `github.io`\n\nRelying on hosting services has a couple of problems (1) those domains are mutable because orgs / usernames are mutable and (2) migrating hosting services is a breaking change.\n\njmillikin:\n\n> if they don't want to do _that_ then they can file an RFC asking the crates.io team to set aside the `.user.crates.io` namespace for free namespaces. There's lots of options here, and more importantly they're easy to adopt at any point in the future if it becomes at all important.\n\nWhile I am for small, incremental RFCs, we need to consider what behavior we will cause with our actions and if that is right. If our answer is to push people to `github.io` and that is an option with significant problems, then we need to take ownership of that and ensure there is a viable option with a paved path.\n\njmillikin:\n\n> ### **Regarding ownership transfer, or: the Cargo / crates.io team's requirements are unreasonable**\n>\n> These requirements (summarized), if combined together, are in conflict with the concept of namespaces:\n\nYes, they are seemingly in conflict with each other. Calling it unreasonable is not accurate and is like saying \"memory safety without garbage collection\" is unreasonable. We shouldn't shy away from solving apparent contradictions.\n\nAs I discussed at Child Thread: Survey of registry namespace designs for Cargo and Crates.io , there may be ways to solve the transfer / rename case. Or maybe we see a strong justification for why we should flex on one of these. Or maybe we go with a completely different solution, like organizational tags, that cover most of the use cases without stepping into this quagmire.",
  "title": "[Pre-RFC] DNS domains as package namespaces"
}