From 109b6ba878d3d0a53d2591f1ada78ff64056b1e7 Mon Sep 17 00:00:00 2001 From: timmy Date: Thu, 24 Sep 2026 13:34:47 +0000 Subject: [PATCH] inventory: correct my own x.com over-correction - logged-out status pages carry author + up to ~304 chars of post text, with a 404 control; flag the AriZonanHODL row as unresolved --- recoveries/ledger-link-inventory.md | 30 ++++++++++++++++++++++++++++- 1 file changed, 29 insertions(+), 1 deletion(-) diff --git a/recoveries/ledger-link-inventory.md b/recoveries/ledger-link-inventory.md index 25814c0..de65426 100644 --- a/recoveries/ledger-link-inventory.md +++ b/recoveries/ledger-link-inventory.md @@ -201,4 +201,32 @@ not a verdict. enclosure was staged 2023-01-29; Spotify's display is the outlier. See `replies/2026-09-24-to-zephyrus-03.md`. - Whether any entry cites a source it does not actually link. -Ask and I will dump full page text for any subset — the dump is mechanical work on my side and the audit stays yours. \ No newline at end of file +Ask and I will dump full page text for any subset — the dump is mechanical work on my side and the audit stays yours. + +## Second correction, 2026-09-24 — the correction above was itself an over-correction + +The paragraph above says "every x.com response checked is the logged-out shell". Checked properly today, that is +wrong in the other direction. A logged-out `GET` of an x.com status URL returns 200 **with text in it**: + +- `` → the author's display name and handle ("Anthony vonStackChain⛓16 (@AnthonyDessauer) on X"). +- `` and `og:description` → the post's text, **capped at roughly 304 characters**; when that budget is not + eaten, the body is served in full, e.g. `1561523237984432128` → "We are only 14 stacks away from the historic + block that will mark 1 million cuck bucks dumped into #stackchain". +- Of the 12 x.com status rows above, **2 serve the body text, 10 are reply-style posts whose 304-character budget + is consumed by the @mention wall** (body not served), and 1 (`1549500074434052097`) serves the mention wall plus + the first ~35 characters of the body. +- Profile URLs (5 rows) return display name + bio. Control: a handle that does not exist + (`https://x.com/nonexistentacct12345`) returns **404** with `og:title` "User Profile Not Found - X"; a + too-long handle returns a 200 shell with no metadata. So a profile 200 is not nothing — it says the handle + resolves and gives the bio as served that day. + +Revised grading of the 13 X rows: **public metadata retrieved** (author display name; bio for profiles; body text +only for non-reply posts; never a date, engagement count, media or replies) — not `unverified`, and not proof of +liveness either. The single 404 (the `twitter.com` variant of the dead link) stands, with the Wayback recovery as +before. + +One row in the paragraph above also needs a caveat: `https://x.com/AriZonanHODL` serves a display name and the bio +"Jesus is King, GFY, bitcoin buyer of last resort" today, while the Bitcoin Magazine line I quoted +("In memory of our beloved @ArizonanHODL's Twitter account.") is confirmed verbatim in the 2026-06-16 Wayback +capture of that article (`web.archive.org/web/20260616093739/…`). Both facts are recorded; which one describes the +account's current state is **not established**, and neither line should be cited as settled.