-
Notifications
You must be signed in to change notification settings - Fork 578
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A proposed recommendation for using 'e' and 'p' tags in nostr clients. #1
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what happens when it's not a reply but there's a mentioned event? would't that conflict and look like a direct reply?
In my opinion "mentions" should be rendered as replies too, but since other clients may not like that it's probably fine to keep that out of this set of recommendations. Let's make this NIP-10. |
NIP-13 |
Renamed to NIP-10. |
Could have been 13 too, I'm just assigning numbers based on how I feel them. But 10 it is! |
@unclebob you think instead of writing |
two parts to this: 1. explicitly calling out 'delegation' as an exception to only single letter tags being queryable 2. adding use case of 'l' being used to identify language I think nostr-protocol#1 should definitely be added. happy to drop nostr-protocol#2 if people disagree.
additional clarity around message content and tags
This appears to conform to the conventions used in branle, damus, and more-speech.