{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihn3bmbve7kr55autql67cfzpq4ehdzm7uym6tpg7i3fs5aymvf7u",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mf72xbiawty2"
  },
  "path": "/t/fork-basement-as-baseplate/12415#post_12",
  "publishedAt": "2026-02-19T00:21:33.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "i read through all the commentary, and this honestly smells to me as somewhat intellectually dishonest.\n\n“oh my package needs updating but you need my permission to use the unique identifier i own? your package manager should just be better and not let someone cause that problem.”\n\n“i don’t want to be responsible for supply chain attacks if i give someone else the commit bit. also, there shouldn’t be trustees at all who would take this responsibility.”\n\nthe whole thing is more FUD and aesthetic theorycraft than practical concerns.\n\ndefinitely agree this is a package takeover loophole. Package versioning exists and is the solution to his problem. Future version could easily have different maintainers etc - his older versions are still sitting there unscathed by this would-be development.",
  "title": "Fork `basement`? As `baseplate`?"
}