diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2026-02-02 00:19:06 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2026-02-02 00:19:06 -0300 |
| commit | 25273a1431b61221dc364710b58a011c57cd6a49 (patch) | |
| tree | 145eab62facd3e357ca7e7b263d6d4a8f0fa848e | |
| parent | b62a595fb654bcdfdfb4b6b8795b41673353f081 (diff) | |
allow referencing existing lists as members.
| -rw-r--r-- | 63.md | 19 |
1 files changed, 19 insertions, 0 deletions
| @@ -35,6 +35,25 @@ The lists are constituted of one event for each _premium-reader_, and their remo | |||
| 35 | } | 35 | } |
| 36 | ``` | 36 | ``` |
| 37 | 37 | ||
| 38 | Besides marking individual public keys as readers it's also possible to tag a replaceable list, identified by its address: | ||
| 39 | |||
| 40 | ```yaml | ||
| 41 | { | ||
| 42 | "kind": 1163, | ||
| 43 | "pubkey": "<content-creator>", | ||
| 44 | "tags": [ | ||
| 45 | ["a", "<kind>:<pubkey>:<d-tag>"], | ||
| 46 | ], | ||
| 47 | // ...other fields | ||
| 48 | } | ||
| 49 | ``` | ||
| 50 | |||
| 51 | This allows for an easy way to, for example, automatically mark all the people the _content-creator_ follows as allowed to read. Or people who are in a specific `kind:30000` follow-set. | ||
| 52 | |||
| 53 | More importantly, it allows the _content-creator_ to delegate inclusion of readers to, for example, a payment provider, such that someone can pay and immediately become a _premium-reader_ without having to wait until the _content-creator_ is online again to update sign a new event. | ||
| 54 | |||
| 55 | It remains a requirement that lists referenced in `"a"` tags here are sent directly to the relays that will implement the paywall, although such relays may try to fetch those in a best-effort basis. | ||
| 56 | |||
| 38 | ### Relay behavior | 57 | ### Relay behavior |
| 39 | 58 | ||
| 40 | A relay that implements this NIP should: | 59 | A relay that implements this NIP should: |