@mckinley I also see repeated Lyse twtxts, and I can’t even mention him on this twtxt. When I type `@Lyse` the pop up shows up, but when I tap on it, it just autocompletes as `@lyse@`, nothing else.
Yeah, this looks like a hash collision to me right? Same twt, same timestamp, same twter, produces two different hashes? I'm not even sure how da fuq this is even possible?
I can't explain this. I'm leaning towards a peering pod being responsible for producing a different hash, and twtxt.net pulling that in from a peer. But that would only happen if my pod doesn't have the Root Twt ans asked its peers for it. And that implies other pods are producing incorrect/different hashes "somehow". So all of that seems highly unlikely tbh.