{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifk27qpazxgjjcebzmgopbzmo2zms5yltxlleutqcoiplraiehkye",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3ml5cc2szoni2"
  },
  "path": "/t/pre-rfc-dns-domains-as-package-namespaces/24202?page=4#post_63",
  "publishedAt": "2026-05-05T20:40:27.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "yaksher:\n\n> There is no important relationship between `example.com/xml` and `example.com/http` for any purposes except a dependency audit to view your attack surface for supply chain vulnerabilities.\n\nI think I disagree with this statement. If the `example.com` part was the namespace, there can be more reasons for it to be related other than supply chain risks from my (as user) perspective. This namespace could be famous for high quality no_std implementations, or have provide interoperability guarantees (functionally).",
  "title": "[Pre-RFC] DNS domains as package namespaces"
}