Implement Retention Policies from NIP-11a

[cameri]

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.

Additional context
https://github.com/nostr-protocol/nips/pull/163/files#diff-e2738305ed5e49cb3b4cb1295e8028c000b203b4e74a4c5fe599dc884e7a92d3R116

[a-khushal]

@cameri can i work on this issue?

[cameri]

@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]

@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?

@cameri yes, I am interested in integrating NIP-11 to nostream

[a-khushal]

@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]

let's go with constant

[cameri]

Thank you @a-khushal !