{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicpddccwuor22nsx25afmlfvy5mqrzzqhp5cvol6muaytfcakmife",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mffw4dsvmrm2"
  },
  "path": "/t/child-thread-survey-of-registry-namespace-designs-for-cargo-and-crates-io/24030#post_3",
  "publishedAt": "2026-02-21T04:28:47.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "crates.io"
  ],
  "textContent": "epage:\n\n> organizations only want a single publisher for their packages.\n\nIn my experience that depends how the organization is structured, and whether the namespace is per project or actually per org. If it's per project, then it could work - large orgs would create project namespaces when needed (but then the org would want to have a reserved namespace and visible ownership for its projects, making it a 3-level namespace...).\n\nBut if the namespace is the org, then it can be a problem for large complex organizations. They can have many different teams/departments/divisions/subsidiaries/regions and half-merged acquisitions, making them behave like multiple different orgs that operate separately (publishing things of varying importance and visibility, by different teams, at different schedules), but externally share one namespace.\n\nThis problem comes up in Web specs, where the same-origin policy is a fundamental unit of separation. Features get designed with per-origin assumptions (quotas, permissions, isolation), but then a task like \"just add a metatag at the root of the domain\" turns out to be very hard when hundreds of teams share a major namespace like `microsoft.com`. If crates.io literally got a namespace like `microsoft`, having it owned by a single account wouldn't suffice. They'd build their own account management and publishing pipeline in front of it, and crates-io would lose detailed information about who actually published what. Complex orgs want complex account management. That's why \"SSO tax\" exists",
  "title": "Child Thread: Survey of registry namespace designs for Cargo and Crates.io"
}