{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiemgn3ie524gn4dwcuum43re6d5y3htv4pvwt4l6jrossmvg6odai",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mfmiqjwp57o2"
  },
  "path": "/t/child-thread-survey-of-alternative-identifier-designs-for-cargo-and-crates-io/24029#post_11",
  "publishedAt": "2026-02-24T14:51:59.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "Survey of organizational ownership and registry namespace designs for Cargo and Crates.io - #4 by epage"
  ],
  "textContent": "Sounds like your idea is focused on reclamation of names after a rename. While a possible idea to explore separately, it isn't one of the use cases we are targeting in Survey of organizational ownership and registry namespace designs for Cargo and Crates.io - #4 by epage. If you think it should be included, that is likely a conversation for that thread. We do talk about the need to recognize that names outside of the registry are mutable and need a scheme to support that for some potential solutions like in Survey of organizational ownership and registry namespace designs for Cargo and Crates.io - #4 by epage but that is focused on the transition path and not reclamation and could have conflicting syntax.",
  "title": "Child Thread: Survey of alternative identifier designs for Cargo and Crates.io"
}