#[3] If you do get the time, please check this reply JSON. Only on Amethyst it is shown as reply to the first "e" tag. On all other clients it's shown as a reply to Corndelorian's post which is how it seems to have been intended.
(I was trying to look at Amethyst code but I'm rusty & couldn't figure out where the issue is in threaded posts 😕)
Cordelorians post is cited in the message. That e is a quote. The other one doesn't have a mark, so it's a reply by the old rules. Maybe the issue is the presence of the first e tag.
Thanks Vitor for checking🙏
I think it's because the NIP10 deprecated version says this:
Two "e" tags: ["e",
I think most clients have interpreted this as the second/final "e" tag is the event being replied to, irrespective of root, but not Amethyst. Sharing a snort screenshot of this reply for your reference.
I only wish I could've raised a PR instead of bothering you but it looked like that would take months 😔
Correct. But snort is wrong. This should not be a reply to the quoted message.
Okay. But many clients implement NIP10 like that - Snort, Primal, Satellite & maybe Damus?
Also, checked on Amethyst, if I reply to a note mentioning another, the replied to note is in first "e" tag and the mention is 2nd. Is this how it's supposed to work?
In any case, since it looks like changes to any client will lead to breaking flow of threads of the old notes in some client, and this happens only in reply + note mentions, I should probably let it go (&pray NIP-27 & marked tags becomes commonplace)
Thanks for explaining & helping me understand Vitor!
