You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Implement retention policies.
Describe the solution you'd like
Allow relay operator to configure the retention policy in time or count of events per kind or kind ranges.
Display retention policy in relay information document as per NIP-11a.
@cameri quick question about nip-11 default_limit.
right now relay uses 500 when client does not send a limit. for this parity, do you recommend it to be a constant, or a setting, or removed unless configurable? i think constant is the best behaviour for now
Activity
a-khushal commentedon Apr 19, 2026
@cameri can i work on this issue?
cameri commentedon Apr 19, 2026
@a-khushal so NIP 11a was closed. What we need to ensure now is compliance with NIP-11 which looks like it has diverged from our implementation.
See https://github.com/nostr-protocol/nips/blob/master/11.md
Are you interesting in bringing NIP-11 support to parity with the spec?
a-khushal commentedon Apr 19, 2026
@cameri yes, I am interested in integrating NIP-11 to nostream
a-khushal commentedon Apr 20, 2026
@cameri quick question about nip-11 default_limit.
right now relay uses 500 when client does not send a limit. for this parity, do you recommend it to be a constant, or a setting, or removed unless configurable? i think constant is the best behaviour for now
cameri commentedon Apr 21, 2026
let's go with constant
cameri commentedon Apr 21, 2026
Thank you @a-khushal !