{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreickke37kwippcu7gypd5q2xl6xcbips3t6yf4ipyrvjdr6rbkxvzq",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mkz7ntapyc72"
  },
  "path": "/t/pre-rfc-dns-domains-as-package-namespaces/24202?page=3#post_60",
  "publishedAt": "2026-05-04T06:05:26.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "jmillikin:\n\n> there is a wide variety of ways that people can get access to a DNS domain name for free\n\nAnd there are just as many ways to loose access to it, especially the free ones, as you often are not the actual owner. Which brings you back to the \"names change\" and how domain expiry is handled, which has caused significant issues in the website space (e.g. advertizing and bookmarks to previously trusted domains being used for scams). And there are enough people that setup \"temporary\" domains without being aware/acknowledging potential issues once you no longer own the domain because you think it is no longer relevant to you. At that point it becomes a liability you either continue paying for or risk it being abused if it has become popular enough.\n\nI really don't think we should or want to extend that into a dependency system, where a domain expiry could easily lead to RCE on a dev machine unless cases like these are really solved.",
  "title": "[Pre-RFC] DNS domains as package namespaces"
}