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

Back to Collection

Record JSON

{
  "$type": "app.bsky.feed.post",
  "createdAt": "2024-02-14T05:49:50.279Z",
  "embed": {
    "$type": "app.bsky.embed.external",
    "external": {
      "description": "Last year, we made some changes to atproto repositories, resulting in \"version 3\". We mostly removed the concept of prev pointers (as CID Links) to previous commits, forming a chain of history. But...",
      "thumb": {
        "$type": "blob",
        "ref": {
          "$link": "bafkreid543vgbycltr3k2epc6ltxnrtralxbywgjtm5jvm547o5ov6y6um"
        },
        "mimeType": "image/jpeg",
        "size": 343481
      },
      "title": "Resolution of repo v3 commit `prev` being both nullable and optional · bluesky-social atproto · Discussion #2181",
      "uri": "https://github.com/bluesky-social/atproto/discussions/2181"
    }
  },
  "facets": [
    {
      "$type": "app.bsky.richtext.facet",
      "features": [
        {
          "$type": "app.bsky.richtext.facet#mention",
          "did": "did:plc:vwzwgnygau7ed7b7wt5ux7y2"
        }
      ],
      "index": {
        "byteEnd": 151,
        "byteStart": 142
      }
    }
  ],
  "langs": [
    "en"
  ],
  "text": "our plan for resolving a wart in atproto specs, with repo v3 commit objects having a 'prev' field which is both nullable and optional\n\nh/t to @retr0.id for getting this on our radar back in september"
}