{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidzrf5cn3aycqdy5vbhj7q72vbctomajy2u7pviyu3lixwmjwdera",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mkp52d4xwry2"
  },
  "path": "/t/pre-rfc-dns-domains-as-package-namespaces/24202?page=3#post_47",
  "publishedAt": "2026-04-30T06:32:34.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "crates.io"
  ],
  "textContent": "jmillikin:\n\n> The package `jmillikin.github.io/json` contains the crate `json`, whereas the package `jmillikin_json` contains the crate `jmillikin_json`.\n\nAs already mentioned in this thread you can make the package `jmillikin_json` contain the crate `json`. It can be a bit confusing to users, but there's no technical difference between the two. You could get the exact same result by allowing the characters `/` and `.` in package names, there's no need to use namespacing for it. Hence there must be some other more important reason for namespacing. My point is that you should focus more on them.\n\njmillikin:\n\n> It's not a particularly big change (see the diffstat for the linked branches in the first post)\n\nIt might not be big in code, but it is big in how users interact with crates.io",
  "title": "[Pre-RFC] DNS domains as package namespaces"
}