🐦 Archived X post

A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-11 01:33 UTC.

@kyronis_talkson X · 2026-09-10

YOU CAN SEARCH TELEVISION. NOT SHOW TITLES. THE ACTUAL WORDS PEOPLE SAID, ACROSS 4,430,000 BROADCASTS, GOING BACK TO 2009. https://t.co/NWGe59pd7x the Internet Archive has been quietly recording news channels for seventeen years and indexing every closed caption. so any sentence ever said on air is now a search box away, with the clip attached. type a phrase. get the channel, the date, the timestamp, and the thirty seconds around it. which means you can do things television never intended. watch a phrase enter the language and count it. pull up how four networks described the same hour differently. find the exact broadcast that was on while something happened to you. I tested it on the things anchors say on autopilot. "folks" is in 1,087,798 clips. "unprecedented" is in 374,273. "no one saw this coming" is in 767. "we reached out for comment", in those exact words, appears 485 times in seventeen years of television. it isn't just American channels. BBC, DW, France 24, Al Jazeera and Russian state television are all in there, all searchable the same way. free. no account. no paywall. the strangest part is that this has existed the whole time and almost nobody uses it.
🔗 linkInternet Archive TV NEWS : Search Captions. Borrow Broadcasts (archive.org)
descriptionWelcome to Internet Archive TV News! This research library service enables you to: Search more than 3 million U.S. broadcasts using closed captioning; Borrow broadcasts on flash drives; View and Cite short streamed clips; Compare and Contrast perspectives across networks, stations and time; and Place video quotes within your commentary. Dive in and Share your insights!

Linked media above is notarized by reference — bsv.cx captured the link's title and preview image at archive time; it does not host the linked video or page.

posthttps://x.com/kyronis_talks/status/2097918210482069875
author id1901793039766413312
posted2026-09-10T05:20:53.000Z
manifest sha25682d94225e2fd389e83c84f872db73a31906ff6294806858b6dad0d6473c7702f
text sha256357c8c6c65fffc87446d90fe607cb308e7da293149ca5b95e0af33b7c9c505ed
media sha256d955995d31bd89dcbe4451cbd2e469ef709bb91e7b2f8977cec7cd3a58783dd9 (video, 2502481 bytes)
on-chain⛓ anchored — 32920c51066eeeadbd4d44b53edc6764ce6f7a4b79d318bc318ecef5ba59d882

Verify it yourself: the manifest is the exact JSON whose SHA-256 is 82d94225e2fd389e83c84f872db73a31906ff6294806858b6dad0d6473c7702f; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 357c8c6c65fffc87446d90fe607cb308e7da293149ca5b95e0af33b7c9c505ed, and read the anchor transaction's OP_RETURN bsv.cx / x1 / 82d94225e2fd389e83c84f872db73a31906ff6294806858b6dad0d6473c7702f — the block's timestamp proves the post said this at or before that time, with no trust in bsv.cx. Content archived via the X API.

← bsv.cx · JSON · ⚠ Report