at://bnewbold.net/app.bsky.feed.post/3ll7t6fobzk2z

Back to Collection

Record JSON

{
  "$type": "app.bsky.feed.post",
  "createdAt": "2025-03-25T17:45:18.678Z",
  "langs": [
    "en"
  ],
  "reply": {
    "parent": {
      "cid": "bafyreifivshf4ol6u3my2gjdjem5dgkwwjnglcfnajfpj4gs4cah5aevmm",
      "uri": "at://did:plc:44ybard66vv44zksje25o7dz/app.bsky.feed.post/3ll7szu7dzc2z"
    },
    "root": {
      "cid": "bafyreicisdyhg7br5mvh3esz2uihoy2cjixf2jfjqn7iuz34gh75xiy4w4",
      "uri": "at://did:plc:ragtjsm2j2vknwkz3zp4oxrd/app.bsky.feed.post/3ll5idg2p522t"
    }
  },
  "text": "ActivityPub has similar challenges and uses \"dynamic client registration\". we went with \"client id metadata documents\", which is an IETF draft (and came from AP community!).\n\nIIRC, OIDC basically has a single auth server per \"brand\". we could do OIDC for \"Bluesky\", but not for \"atproto\""
}