{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifsqjwgfk5t7gyjebzekjrl6eioixme5gbmhjrqnowlv6twpe2meu",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mffpenzn6so2"
  },
  "path": "/t/child-thread-survey-of-registry-namespace-designs-for-cargo-and-crates-io/24030#post_8",
  "publishedAt": "2026-02-21T20:31:11.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "kornel:\n\n> The Homebrew core tap is curated, which is reassuring it won't suddenly spring drive-by typosquatted packages\n\nI feel this is a big part of what makes this design of implicit merging work. Along with the fact that taps generally are for adding packages that don't exist, so that in general `brew install $package` is almost always going to install it from where you expect, or give a \"not found\" error if you forgot to add the tap.",
  "title": "Child Thread: Survey of registry namespace designs for Cargo and Crates.io"
}