@GabesArcade@gabesarcade.com Did you by change edit or otherwise delete the Twt you replied to (2nd last in your feed) with the reply/thread id lleeypvkzbw2? That Twt was never ingested by twtxt.net (and likely the search engine) so umm hmmm threading breaks 🤣

It’s no big deal of course, we are fully aware of the couple of rare(ish) edge cases with the threading model.

@GabesArcade@gabesarcade.com Yes, because if you edit/delete a Twt after the ecosystem has ingested it, well there then are two versions 😅 Just be aware of edits/deletes, especially if someone has already replied to said Twt 🤣

@GabesArcade@gabesarcade.com Wiath what client? 🤔

I see the same thing, @prologic@twtxt.net. They will eventually disappear.

Oh if we’re talking about the twtxt.app client, that’s a different story. I still consider that alpha/beta quality. Lemme look into that. It has it’s own cache of course (using IndexDB) and it’s entirely possible some behaviours are still not quite right yet…

I think I fixed this bug!

@GabesArcade@gabesarcade.com You’re welcome! ☺️