@bender@twtxt.net Nothing that isn’t already a known side effect. Really it is up to clients to figure this out and have storage or caching mechanisms that can cope with diverging threads.

@prologic@twtxt.net but the problem is with Yarn too (the front end)! You know it has happened before a few times. Now the chances increase.

@bender@twtxt.net This is true! (as we spoke!) It’s okay though, I think we’ll eventually solve this as it becomes a thing that annoys us too much 🤣 I like your idea of having some optional, but recommended of handling edits. Like having something like (#d4acmcq was:zllu75a) just for an example. Extending the Subject Extension to support (#hash [was:<hash>])? 🤔