{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihy6pfryzeufdekimjgtgdff2kyw56a5flkglkphpily6g3qsy4am",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mfgqwbtbox52"
  },
  "path": "/t/child-thread-survey-of-alternative-identifier-designs-for-cargo-and-crates-io/24029#post_2",
  "publishedAt": "2026-02-22T07:44:41.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "IMHO, a human readable name is always better than a nonsense uuid, and different package owner that use the same name might make beginners hard to choose which crate to use.\n\nMaybe there is a better way: combine crate name with editions.\n\nFirstly, if you register a crate name that is never used before, you can own that crate name until a new _**challenge**_ occurs and no response is submitted. Each crate could have 2 different crate names (for example, `reqwest` could also registered as `request#seanmonstar`, which has the right to submit challenge to own `request` crate. )\n\nA _**challenge**_ could be submitted by another crate with the same name and different owner, which is actively maintained in the latest 2 editions, and the challenged crate has at least one of the following conditions:\n\n  1. No updates in the latest 2 editions. In this case, the challenge cannot be responsed, and the crate name transferred asap.\n  2. No updates in the newest edition, In this case, the challenge could be responsed by publish an upgraded version in (for example) 90 days.\n\n\n\nAn _official_ short name might guide users to use the correct crate, that's a very good feature and thus should not be discarded easily.",
  "title": "Child Thread: Survey of alternative identifier designs for Cargo and Crates.io"
}