nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-30 08:50:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

add note about default case for most relays.

Browse Source
This commit is contained in:
fiatjaf 2024-02-08 14:03:36 -03:00
parent ccb0cd4ea0
commit 47579ced55
No known key found for this signature in database
GPG Key ID: BAD43C4BE5C1A3A1
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
70.md
View File

@ -44,7 +44,9 @@ This NIP gives these authors and relays the means to know when a given event is
## How ## How
In practice, authors of protected events would have to have some kind of relationship with some specific relays -- for example, using [NIP-29](29.md) -- that would enable relays to know to whom these events can be served once they're published by the author. The default behavior for most relays will be to reject all events with the `protected` tag. Only relays previously programmed to enforce access-control on these events would have to write special code for handling them.
Authors of protected events would have to have some kind of relationship with some specific relays -- for example, using [NIP-29](29.md) -- that would enable relays to know to whom these events can be served once they're published by the author.
If someone tries to copy the event and publish it to other relays that wouldn't enforce the rules intended by the author that won't work as these relays will reject the event. If someone tries to copy the event and publish it to other relays that wouldn't enforce the rules intended by the author that won't work as these relays will reject the event.