@prologic@twtxt.net why would you think it is changed in jenny? Falsifian (I still can’t mention while on mobile) said jenny, and the manual calculation match. Yarn seems to be the one at odd.

⤋ Read More

@prologic@twtxt.net it hasn’t been solved, that’s why we are here on this yarn, still. LOL. I believe the hash mismatch is happening because of an edited twtxt. I don’t follow the OP, so I have no way to check (not that I am certain it could be possible), but I have seeing similar issues in the past as a result of an edit. That’s one of the reasons I don’t edit anymore. 😬

⤋ Read More

@falsifian@www.falsifian.org @prologic@twtxt.net @bender@twtxt.net The twt was edited. In my cache, it also has hash st3wsda and it started like this:

(<a href="https://twtxt.net/twt/yqke7sq">#yqke7sq</a>) I've been sketching out some …

When fetching the feed now, the twt starts like this and the current twt gets the hash 6mdqxrq:

(<a href="https://txt.sour.is/search?q=tags:yqke7sq">#yqke7sq</a>) I've been sketching out some …

This can’t be avoided, really. Publishing twts and then editing them is like doing a git push --force after rewriting the commit history. Chaos will ensue. 😅

⤋ Read More

Participate

Login to join in on this yarn.