Oddbean new post about login | logout holy cow thanks for explaining this! I’ve been tinkering with rendering replies and keep seeing inconsistencies with e tag ordering vs the last element of the tag containing “reply” or “root”. great to see an explanation.
I’ve gotten so familiar with NIP-10 in the last few days because I’m implementing it right now in Nostr SDK. For maximum compatibility with older clients, Amethyst could probably be updated so that it orders event tags such that the event being replied to is still positioned last.
Fuck it. I’ll try to fix it myself. Diving into Amethyst code for the first time!
Done. @Vitor Pamplona Here’s the fix for Amethyst to add write support for NIP-10 deprecated positional tags in text notes to maximize backwards compatibility. https://github.com/vitorpamplona/amethyst/pull/737 It’s a much larger lift to add support for the recommended approach of NIP-10 event tag markers on the Damus side, though, so I’ll leave that alone for now.
This doesn’t work if you’re replying directly to the root thread and also mention other events, or if you’re not replying at all and just want to mention events. The ambiguity is why positional event tags were deprecated. For the former case when it’s a direct reply to the root, I suppose I could update the PR such that the root event tag comes last to make it slightly less bug inducing, but it’ll still be wrong.
