nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-22 16:35:52 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

remove rationale

Browse Source
This commit is contained in:
Sandwich 2024-09-23 23:43:48 +02:00 committed by GitHub
parent b0491854f8
commit c7da9d7409
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
119.md
View File

@ -11,15 +11,8 @@ filters: {
// returns kind `1` events with `t` tags that have both "meme" and "cat" that have the tag "black" or "white" // returns kind `1` events with `t` tags that have both "meme" and "cat" that have the tag "black" or "white"
``` ```
## Rationale
- Reduce bandwidth for all, with an emphasis on mobile users: `meme AND cat` objectively consumes less bandwidth than `meme OR cat `
- Reduce clock-time for relays, indexing with `AND` is fast for all common index formats, and faster compared to `OR` for some index formats. (See section below)
- Reduce client-side caching requirements
- Reduce centralization vectors by reducing or even eliminating the need for centralized REST, GraphQL APIs or specialized relay "feed" endpoints.
- Give relays the option to be more useful at the protocol level while improving efficiency for all parties.
## Rules ## Rules
- `AND` **MUST** take precedence over `OR` - `AND` **MUST** take precedence over `OR`
- Tags used in `AND` **SHOULD NOT** be used in standard `OR` tags [`#`] - Tags used in `AND` **SHOULD NOT** be used in standard `OR` tags [`#`]
- Any tag used in `AND` **SHOULD** be ignored in `OR` - Any tag used in `AND` **SHOULD** be ignored in `OR`