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

Back to Collection

Record JSON

{
  "$type": "app.bsky.feed.post",
  "createdAt": "2025-03-17T23:01:17.011Z",
  "embed": {
    "$type": "app.bsky.embed.external",
    "external": {
      "description": "",
      "thumb": {
        "$type": "blob",
        "ref": {
          "$link": "bafkreigurilfe3p7rl7cpuikydbvr66xe3vfyb4qn6c5oj7w4k4pklppme"
        },
        "mimeType": "image/jpeg",
        "size": 327122
      },
      "title": "handlr: DNS TXT wrapper for handle resolution by bnewbold · Pull Request #665 · bluesky-social/indigo",
      "uri": "https://github.com/bluesky-social/indigo/pull/665"
    }
  },
  "langs": [
    "en"
  ],
  "reply": {
    "parent": {
      "cid": "bafyreiayclmvlvymnieotvkdpbnsxuaanos3koufqryfbpvucbom7i7pbq",
      "uri": "at://did:plc:hdhoaan3xa3jiuq4fg4mefid/app.bsky.feed.post/3lkmaoq6qek2b"
    },
    "root": {
      "cid": "bafyreiacmvz2eywtt7j4fulnnvohcugvh2jl3xxfofd7ik62h3bblahr3a",
      "uri": "at://did:plc:hdhoaan3xa3jiuq4fg4mefid/app.bsky.feed.post/3lkm6nhmj2k2b"
    }
  },
  "text": "if you end up trying to do dynamic stuff, might be interested in this DNS server.\n\npragmatically, i'd def start with the NSID-as-rkey pattern though!\n\nif nested records are `unknown` and have `$type`, then schema validators could (optionally?) use that to resolve+validate examplars"
}