Closed staab closed 3 weeks ago
Ack
Looks good to me.
Is this a breaking change?
I think e
tag and a
tag should be distinguished to parse.
If the tags are the same name, they cannot be parsed correctly.
Please use Q
or another tag name. (I'm in favor of supporting the address.)
["q", <32-bytes lowercase hex of the id of another event>, <relay-url>]
["q", <kind integer>:<32-bytes lowercase hex of a pubkey>:<d tag value>, <relay-url>]
I think e tag and a tag should be distinguished to parse.
Clients still have to be defensive, and it's easy to tell an address from an event. I believe we do this overloading elsewhere and it's ok. But I'm open to using Q
instead.
Also, sorry about merging so quickly, I thought it had been 24 hours. Today has been a long day.
reverted
Yes this is a breaking change.
Gossip currently pushes an "a" tag with the third field being "mention". You can complain about how wrong you think that is with plenty of logical justification, but that used to be right. That was what the NIPs said to do at some time in the past.
The same was true of e tags, and both should still work, but it is ambiguous because both 3-deep replies and mentions will have mention tags, but with different meanings. For compatibility quotes should probably include both, but use of q clarifies what is intended.
If a
naddr
is added to a note's content, it should be referred to in the tags. But using ana
tag will cause the quote to be treated as a reply (as used to happen with events). In some cases, using aq
tag with the event's id rather than address may work, but it goes against user intention, and it may not always be possible to convert an address to an id if the event is not loaded by the client. Adding an address variant toq
tags fixes this.Related conversation: https://github.com/cesardeazevedo/nostr-editor/pull/8