at://did:plc:44ybard66vv44zksje25o7dz/app.bsky.feed.post/3me3hfbfb722d

Back to Collection

Record JSON

{
  "$type": "app.bsky.feed.post",
  "createdAt": "2026-02-05T03:33:35.908Z",
  "langs": [
    "en"
  ],
  "reply": {
    "parent": {
      "cid": "bafyreiarwq3di5qlhv6aqtjykqlu2457zwnxkjicgc6vnewnkbueedagt4",
      "uri": "at://did:plc:44ybard66vv44zksje25o7dz/app.bsky.feed.post/3me3hawyelk2d"
    },
    "root": {
      "$type": "com.atproto.repo.strongRef",
      "cid": "bafyreichvq6kj5an74pe7e62hfgfdlnu6irsvxr3266xh5b7jpqgfnnqxe",
      "uri": "at://did:plc:44ybard66vv44zksje25o7dz/app.bsky.feed.post/3me3exqz3222v"
    }
  },
  "text": "I don't think it all needs to be \"on protocol\", and pragmatically i'd guess most of the flexibility would be regular old server code?\n\nControl of long-term account identity is important though, and is rooted in protocol and cryptography (eg, DID PLC)."
}