In-reply-to » @lyse ` `` `

@prologic@twtxt.net Hm, I think there’s some edit confusion going on.

When my client fetched @xuu@txt.sour.is’s twt, it read like this (I’m posting screenshots here to avoid something parsing this as markdown):

Download

The hash I got for this was v6kvlma. That’s what’s still stored in my client.

Note the wrong mention. xuu must have edited it, because it now reads like this:

Download

And I get dmypf5q for that.

This latter hash also exists on twtxt.net, but it’s not the one that @lyse@lyse.isobeef.org replied to: https://twtxt.net/conv/dmypf5q

lyse replied to u4bs34q (https://twtxt.net/conv/u4bs34q), but I can’t find out what the original raw content of that twt was. Can someone show me that raw twt line? Then I can check which hash I get. 🙂

The simplest explanation is that xuu edited several times and lyse replied to something other than the current/final twt.

(For that original twt from your test cases (the one the say “Great, last system update broke something …”), I get bd3yzvq, just like your test suite.)

⤋ Read More