{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreic6p7wv264qijxmaphysivmbm4cmoexyytdsghrjcfwklvnurvibi",
    "uri": "at://did:plc:q2k4ilmlzzrnoog5dccpqwor/app.bsky.feed.post/3mjooxgkop6o2"
  },
  "path": "/post/46045366",
  "publishedAt": "2026-04-17T03:25:47.000Z",
  "site": "https://lemmy.ml",
  "tags": [
    "Privacy",
    "SuspciousCarrot78",
    "26 comments",
    "…claude.com/…/14328960-identity-verification-on-c…"
  ],
  "textContent": "submitted by SuspciousCarrot78 to privacy\n35 points | 26 comments\n\nI’m a big proponent of self-hosting, right to repair, and rolling your own whatever when you can. That probably started as teenage rebellion that got baked in - I was lucky enough to read both Walden and The Hobbit during a week-long cyclone lockdown several decades ago - but I suspect there’s a non-trivial overlap between that space and privacy-minded people in general.\n\nMy endgame is a self-sufficient intranet for myself and family: if the net goes down tomorrow, we’d barely notice.\n\nI also use LLMs as a tool. True self-hosted equivalence to state-of-the-art models is still an expensive proposition, so like many, I use cloud-based tools like Claude or Codex for domain-specific heavy lifting - mostly coding. Not apologising for it; I think it’s a reasonable trade-off while local hardware catches up.\n\nThat context is just to establish where I’m coming from when I say this caught my attention today:\n\n…claude.com/…/14328960-identity-verification-on-c…\n\nTo be accurate about what it actually says: this isn’t a blanket “show us your passport to use Claude.” Not yet.\n\nThe policy as written is narrower than it might first appear.\n\nMy concern isn’t what it says - it’s that the precedent now _exists._ OAI will do doubt follow suite.\n\nScope creep is a documented pattern with this kind of thing, and “we only use it for X” describes current intent, not a structural constraint.\n\nGiven the nature of this community, figured it was worth flagging.",
  "title": "Claude: papers please?"
}