` `` ` 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? 🤔
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? 🤔
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? 🤔
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? 🤔
When my client fetched @xuu’s twt, it read like this (I’m posting screenshots here to avoid something parsing this as markdown):
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:
And I get
dmypf5q for that.This latter hash also exists on twtxt.net, but it’s not the one that @lyse 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.)
When my client fetched @xuu’s twt, it read like this (I’m posting screenshots here to avoid something parsing this as markdown):
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:
And I get
dmypf5q for that.This latter hash also exists on twtxt.net, but it’s not the one that @lyse 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.)
When my client fetched @xuu’s twt, it read like this (I’m posting screenshots here to avoid something parsing this as markdown):
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:
And I get
dmypf5q for that.This latter hash also exists on twtxt.net, but it’s not the one that @lyse 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.)
When my client fetched @xuu’s twt, it read like this (I’m posting screenshots here to avoid something parsing this as markdown):
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:
And I get
dmypf5q for that.This latter hash also exists on twtxt.net, but it’s not the one that @lyse 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.)
> 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 🤣
> 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 🤣
> 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 🤣
> 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 🤣
curl https://txt.sour.is/twt/u4bs34q -H 'Accept: application/json' That exfiltrated the original twt from @xuu's yarnd instance, which I cast into a test case: https://git.mills.io/lyse/go-lextwt/commit/66d8e56141233af66026cfb72ebd74b02cc02201
though now i am seeing a weird cache corruption.. that seems to come and go.
though now i am seeing a weird cache corruption.. that seems to come and go.
u4bs34q here, too.Phew. 🥴
u4bs34q here, too.Phew. 🥴
u4bs34q here, too.Phew. 🥴
u4bs34q here, too.Phew. 🥴