nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-14 07:49:07 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

simplify

Browse Source
This commit is contained in:
Ricardo Arturo Cabral Mejía 2024-06-23 20:09:33 -04:00
parent f85d60f49e
commit 5c1f978fca
No known key found for this signature in database
GPG Key ID: 5931EBF43A650245
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
122.md
View File

@ -62,15 +62,14 @@ const encrypted_content = nip44_encrypt(events, ...);
### Guidelines for Responding Clients ### Guidelines for Responding Clients
- Clients SHOULD send back the actual requested events to the relay from which it received the request when relay URL hints are missing or when publishing to the relay hint is not possible. - Clients SHOULD send back the actual requested events to the relay from which it received the request when relay URL hints are missing or when publishing to the relay hint is not possible.
- Clients SHOULD NOT respond with any ephemeral events they may have in store. - Clients SHOULD NOT respond with any ephemeral events they may have in store including the original Request For Events nor issue a new Request For Events for the same event IDs.
- Clients SHOULD NOT resend the original Request For Events or issue a new Request For Events for the same event IDs.
- Clients MAY respond to requests from users they follow or that belong to their Web of Trust. - Clients MAY respond to requests from users they follow or that belong to their Web of Trust.
- Clients MAY respond to a fraction of requests (e.g. 5% sample rate) and/or adhere to data caps if they have limited resources (i.e. mobile clients). - Clients MAY respond to a fraction of requests (e.g. 5% sample rate) and/or adhere to data caps if they have limited resources (i.e. mobile clients).
- Clients MAY reject requests without sufficient Proof-of-Work. (e.g. [NIP-13](13.md)) - Clients MAY reject requests without sufficient Proof-of-Work. (e.g. [NIP-13](13.md))
### Guidelines for Relays ### Guidelines for Relays
- Relays SHOULD forward public requests to a fraction of connected clients (e.g. 10% sample rate).
- Relays SHOULD implement rate limits to prevent denial-of-service (DoS) attacks. - Relays SHOULD implement rate limits to prevent denial-of-service (DoS) attacks.
- Relays MAY forward public requests to a fraction of connected clients (e.g. 10% sample rate).
- Relays MAY reject public request for events if at least one of the requested events is already in their store. - Relays MAY reject public request for events if at least one of the requested events is already in their store.
- Relays MAY reject request for events that have insufficient Proof-of-Work. - Relays MAY reject request for events that have insufficient Proof-of-Work.