{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreic5xtjtr7hpsbcatedhnijeckz3demwnljursvbmtbq6tlk3wn6p4",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mkpxvicyka72"
  },
  "path": "/t/pre-rfc-dns-domains-as-package-namespaces/24202?page=3#post_52",
  "publishedAt": "2026-04-30T13:53:44.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "crates.io"
  ],
  "textContent": "> Why does this require namespaces vs. just expanding the character set allowed in package names?\n\nIf you just expand the character set without introducing some form of access control then individual users could publish with names like `google.com/protobuf` or `rust-lang.org/libc`.\n\nThis would violate the crates.io team's requirement that the name of a crate should not mislead regarding which individual or organization is responsible for it.\n\n(my understanding is that in today's world the rules against publishing `google-protobuf-official` or `rust-libc` are enforced manually; namespaces are an opportunity to bake that enforcement into the ACL layer)",
  "title": "[Pre-RFC] DNS domains as package namespaces"
}