@lyse@lyse.isobeef.org ` `` `
@movq@www.uninformativ.de Ahh this was a bug that @lyse@lyse.isobeef.org triggered and I think I discovered and then @xuu. fixed 😅
@movq@www.uninformativ.de It was this
@movq@www.uninformativ.de I’d say that tt, jenny and lextwt all had their own respective bugs 😅 I think its not a problem with the Hashing per se, but how the content is handled/parsed? 🤔 This is the commit that @xuu published to fix the bug in lextwt – Maybe it’ll help you figure out a similar edge case with jenny? 🤔
The simplest explanation is that xuu edited several times and lyse replied to something other than the current/final twt.
This is probably what you were actually referring to, I got confused and thought you were asking about something else 😅 Sorry! 🙏 Needless to all this craziness was because we found a weird edge case 🤣
@movq@uninformativ.de yeah.. i rewrote it a few times because i thought there was something breaking.. but was mistaken
though now i am seeing a weird cache corruption.. that seems to come and go.
Me too 😅