nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-25 17:55:51 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

renames property to attribute for consistency

Browse Source
This commit is contained in:
Vitor Pamplona 2024-01-04 11:07:46 -05:00
parent 5d06af8af5
commit 97fc0fb081
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
01.md
View File

@ -68,7 +68,7 @@ To verify the authenticity of an event:
## Kinds ## Kinds
The `.kind` property specifies the meaning of an event, its tags and it is further defined in the various NIPs in this repository The `.kind` attribute specifies the meaning of an event, its tags and it is further defined in the various NIPs in this repository
Specific ranges define storage behaviors: Specific ranges define storage behaviors:
@ -152,15 +152,15 @@ To open and update, and close subscriptions, Clients MUST use the following form
A `REQ` message may contain multiple filters which are interpreted as an OR statement: events that match any of the filters are to be returned. A `REQ` message may contain multiple filters which are interpreted as an OR statement: events that match any of the filters are to be returned.
Properties in each filter are a logical AND statement: all present properties must match for the filter to pass. Attributes are a logical AND statement: all present attributes must match for the filter to pass.
Array properties (i.e. `ids`, `authors`, `kinds`, and tag filters) represent a logical OR statement. At least one of the arrays' values must match the respective field in the event to be considered a match. In the case of tag attributes such as `#e`, for which an event may have multiple values, the event and filter condition values must have at least one item in common. Array attributes (i.e. `ids`, `authors`, `kinds`, and tag filters) represent a logical OR statement. At least one of the arrays' values must match the respective field in the event to be considered a match. In the case of tag attributes such as `#e`, for which an event may have multiple values, the event and filter condition values must have at least one item in common.
The `ids`, `authors`, `#e`, and `#p` filter lists MUST contain exact 64-character lowercase hex values. The `ids`, `authors`, `#e`, and `#p` filter lists MUST contain exact 64-character lowercase hex values.
The `since` and `until` properties are used to specify the time range of events returned in the subscription. An event matches the filter if `since <= created_at <= until` holds. The `since` and `until` attributes are used to specify the time range of events returned in the subscription. An event matches the filter if `since <= created_at <= until` holds.
The `limit` property informs the maximum number of events to return, sorted by `.created_at` desc. It operates over the previously stored events and is ignored afterward. The `limit` attribute informs the maximum number of events to return, sorted by `.created_at` desc. It operates over the previously stored events and is ignored afterward.
### Subscription Responses ### Subscription Responses