I guess I can configure neomutt to hide the feeds I don’t care about.

@falsifian@www.falsifian.org have you tried jenny’s fetch-context branch? It works great!

@movq@www.uninformativ.de pretty cool! Switched, and pulled. Nice update on README!

@movq@www.uninformativ.de Thanks, it works!

But when I tried it out on a twt from @prologic@twtxt.net, I discovered jenny and yarn.social seem to disagree about the hash of this twt: https://twtxt.net/twt/st3wsda . jenny assigned it a hash of 6mdqxrq but the URL and prologic’s reply suggest yarn.social thinks the hash is st3wsda. (And as a result, jenny –fetch-context didn’t work on prologic’s twt.)

I just manually followed the steps at https://dev.twtxt.net/doc/twthashextension.html and got 6mdqxrq. I wonder what happened. Did @cuaxolo@sunshinegardens.org edit the twt in some subtle way after twtxt.net downloaded it? I couldn’t spot a diff, other than ‘ appearing as ’ on yarn.social, which I assume is a transformation done by twtxt.net.

@movq@www.uninformativ.de Jenny hasn’t changed the way it computes hashes has it? (yarnd certainly hasn’t).

@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.

@bender@twtxt.net I’ve sort of lost the plot here a bit 🤦‍♂️ What’s the problem we’re trying to figure out? 🤔

@prologic@twtxt.net One of your twts begins with (#st3wsda): https://twtxt.net/twt/bot5z4q

Based on the twtxt.net web UI, it seems to be in reply to a twt by @cuaxolotl@sunshinegardens.org which begins “I’ve been sketching out…”.

But jenny thinks the hash of that twt is 6mdqxrq. At least, there’s a very twt in their feed with that hash that has the same text as appears on yarn.social (except with ‘ instead of ’).

Based on this, it appears jenny and yarnd disagree about the hash of the twt, or perhaps the twt was edited (though I can’t see any difference, assuming ’ vs ’ is just a rendering choice).

The actual end-user problem is that I can’t see the thread properly when using neomutt+jenny.

@falsifian@www.falsifian.org Ahh but this is solved now with the new single shot fetch?

@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. 😬

@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://we.loveprivacy.club/search?tag=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. 😅

@movq@www.uninformativ.de This ☝️

@movq@www.uninformativ.de thanks for getting to the bottom of it. @prologic@twtxt.net is there a way to view yarnd’s copy of the raw twt? The edit didn’t result in a visible change; being able to see what yarnd originally downloaded would have helped me debug.

@prologic@twtxt.net Specifically, I could view yarnd’s copy here, but only as rendered for a human to view: https://twtxt.net/twt/st3wsda

@falsifian@www.falsifian.org Yes hit a Twt permalink URI and ask for application/ json

@prologic@twtxt.net come on, provide us with a one liner curl foo that does just that, don’t be lazy! :-P

@prologic@twtxt.net Perfect, thanks. For my own future reference: curl -H ‘Accept: application/json’ https://twtxt.net/twt/st3wsda