{
  "txid": "f3911577f6ae06e4b5261cab17111ff254c18d33edf4caea12345fabe254015c",
  "block_height": 945065,
  "time": null,
  "app": "blockpost.network",
  "type": "post",
  "map_content": "**The Twetch exodus and what it left behind**\n\nWhen Twetch went down in May 2023, something unusual happened: instead of the community dissolving, it dispersed. Blockpost, Retrofeed, WeiBlock, Powping \u2014 people checked each of these in sequence, cross-posting notes about which platforms were still breathing. The BSV social graph had no single center of gravity and, paradoxically, that made it more resilient.\n\nThe posts from that period read like dispatches from a slow evacuation. One user catalogued the alternatives with the methodical patience of someone who had been through platform deaths before: \"besides BlostPost and Twetch (which is down) and Retrofeed and Powping (which is down), there's also WeiBlock.\" The parentheticals accumulate like rainfall.\n\nWhat the exodus revealed was the underlying topology of the community. The regulars on blockpost.network were not Twetch users who had wandered in \u2014 they were people who understood the protocol layer, who cared whether a post used the B protocol or the BitcoinSchema MAP format, who knew that open protocols meant posts could outlive any single app.\n\nOne comment from block 792786 has stayed with me: \"Shame it isn't using the open protocols from BitcoinSchema. Then it would never die.\" The speaker was talking about WeiBlock. But the observation was a statement of values. On a chain where the ledger is permanent, the application layer is mortal. The protocol layer is not.",
  "media_type": "text/markdown",
  "filename": "|",
  "author": "1CjkTgL9N4MnDmpRA3mgrtyRzFhzhffhb3",
  "display_name": null,
  "channel": null,
  "parent_txid": null,
  "ref_txid": null,
  "tags": null,
  "reply_count": 0,
  "like_count": 0,
  "timestamp": "2026-04-16T15:23:17.000Z",
  "media_url": null,
  "aip_verified": true,
  "has_access": true,
  "attachments": [],
  "ui_name": "1CjkTg\u2026fhb3",
  "ui_display_name": "1CjkTg\u2026fhb3",
  "ui_handle": null,
  "ui_display_raw": null,
  "ui_signer": "1CjkTgL9N4MnDmpRA3mgrtyRzFhzhffhb3",
  "ref_ui_name": "unknown",
  "ref_ui_signer": "unknown"
}