change create_at limits to be relative to now

This commit is contained in:
Vitor Pamplona 2024-08-20 16:46:31 -04:00
parent d5ed30b994
commit d4c3f2a2cc

8
22.md
View File

@ -20,7 +20,7 @@ Where `limit_properties` includes properties that are specifically designed to c
- `accepted_event_kinds: [<unsigned int>, <unsigned int>, ...]`, Clients MUST filter publishing events by these types. - `accepted_event_kinds: [<unsigned int>, <unsigned int>, ...]`, Clients MUST filter publishing events by these types.
- `blocked_event_kinds: [<unsigned int>, <unsigned int>, ...]`, Clients MUST remove these types from publishing actions. - `blocked_event_kinds: [<unsigned int>, <unsigned int>, ...]`, Clients MUST remove these types from publishing actions.
<br/><br/> <br/><br/>
- `min_pow_difficulty: <int>`: Clients MUST filter publishing events if they don't have at least this PoW bit difficulty. - `min_pow_difficulty: <int>`: Clients MUST filter publishing events to have PoW (number of bits equal to zero) >= this value
<br/><br/> <br/><br/>
- `max_message_length: <int>`, Clients MUST filter publishing events and crop/chunk `REQ` filters by this length. - `max_message_length: <int>`, Clients MUST filter publishing events and crop/chunk `REQ` filters by this length.
- `max_subscriptions: <int>`, Clients MUST reduce the number of subscriptions to this amount. - `max_subscriptions: <int>`, Clients MUST reduce the number of subscriptions to this amount.
@ -29,12 +29,12 @@ Where `limit_properties` includes properties that are specifically designed to c
- `max_event_tags: <int>`, Clients MUST filter publishing events by this `.tags` length. - `max_event_tags: <int>`, Clients MUST filter publishing events by this `.tags` length.
- `max_content_length: <int>`, Clients MUST filter publishing events by this `.content` length. - `max_content_length: <int>`, Clients MUST filter publishing events by this `.content` length.
<br/><br/> <br/><br/>
- `created_at_lower_limit: <unix timestamp>`, Clients MUST filter publishing events whose `.created_at` is smaller than this number - `created_at_msecs_ago: <int, milliseconds>`, Clients MUST filter publishing events whose `.created_at` is > than now - this number
- `created_at_upper_limit: <unix timestamp>`, Clients MUST filter publishing events whose `.created_at` is bigger than this number - `created_at_msecs_ahead: <int, milliseconds>`, Clients MUST filter publishing events whose `.created_at` is < than now + this number
<br/><br/> <br/><br/>
- `filter_rate_limit: <int, milliseconds>`: Clients MUST debounce filter changes after this amount in milliseconds. - `filter_rate_limit: <int, milliseconds>`: Clients MUST debounce filter changes after this amount in milliseconds.
- `publishing_rate_limit: <int, milliseconds>`: Clients MUST debounce publishing events by this amount in milliseconds. - `publishing_rate_limit: <int, milliseconds>`: Clients MUST debounce publishing events by this amount in milliseconds.
<br/><br/> <br/><br/>
- `required_tags: [ [ <key>, <value, optional> ], [ <key>, <value, optional> ] ]`, Clients MUST filter publishing events that don't include all listed tag names and values. - `required_tags: [ [ <key>, <value, optional> ], [ <key>, <value, optional> ] ]`, Clients MUST filter publishing events to contain all listed tag names and values.
This payload SHOULD be cached in the Client's Relay connection object and updated as many times as the relay requests. Clients should use the information here to apply filters when sending events and `REQs` to the relay. This payload SHOULD be cached in the Client's Relay connection object and updated as many times as the relay requests. Clients should use the information here to apply filters when sending events and `REQs` to the relay.