{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreie4c2th3gm7bspxa6sp7i5m3g72j4rqhhkq6gztqhunoksk3tp2fm",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mkpr6devbo72"
  },
  "path": "/t/pre-rfc-dns-domains-as-package-namespaces/24202?page=3#post_51",
  "publishedAt": "2026-04-30T13:47:52.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "jmillikin:\n\n> If you're OK with a package being published with the name `\"john-millikin-com-json\"` and `lib.name = \"json\"`, then why would you not want to allow the semantically equivalent and much easier to work with `\"john-millikin.com/json\"` package name?\n\nWhy does this require namespaces vs. just expanding the character set allowed in package names?",
  "title": "[Pre-RFC] DNS domains as package namespaces"
}