-
Notifications
You must be signed in to change notification settings - Fork 526
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
NIP-15 must be mandatory #421
Conversation
sending an `EOSE` message from the relay must be mandatory not optional.
just fyi, you don't need to create a new PR every time you need to make a change, just add a new commit to the branch 😉 -- otherwise discussions are lost |
Thanks man. it's too late here and I ran out of caffeine 😄 |
15.md
Outdated
|
||
The motivation for this proposal is to reduce uncertainty when all events have been sent by a relay to make client code possibly less complex. | ||
Clients may use the `supported_nips` field to learn if a relay supports end of stored events notices. | ||
Clients MUST unsubscribe when they get an `EOSE` message from the relay. |
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.
Clients MUST unsubscribe when they get an `EOSE` message from the relay. |
Co-authored-by: Semisol <45574030+Semisol@users.noreply.github.com>
Sorry for asking you to open this PR, but I've decided it would be simpler and clearer for everybody to just merge NIP-15 into NIP-01. |
great decision 👍 |
sending an
EOSE
message from the relayMUST
bemandatory
not optional.