{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiezhgru52hbbdbaxbofhxkotu7zpd64kboo7lzwhrex5yq4bqr7w4",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mkklmdrqnty2"
  },
  "path": "/t/pre-rfc-dns-domains-as-package-namespaces/24202?page=2#post_34",
  "publishedAt": "2026-04-28T10:30:36.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "> I'm not following this argument. If you published `jmillikin/fuse` with namespaces would you be ok with others not being able to publish their `jmillikin/fuse` ? To me it's exactly the same. If you then argue I could publish my own `skifire13/fuse` why can't I publish `skifire13_fuse` right?\n\nIf I were writing a FUSE mount server and needed a FUSE library I would look into `skifire13/fuse` as a possible candidate, but would probably not look at `skifire13_fuse` because I don't know what sort of technology `skifire13` is.\n\nedit: For example, there is a program called Ghidra that has its own dialect of XML, and the library I wrote to parse it is `ghidra-xml`. It's not a general-purpose XML library, it's specific to the Ghidra dialect.",
  "title": "[Pre-RFC] DNS domains as package namespaces"
}