diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2026-02-20 08:04:27 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2026-02-20 08:04:27 -0300 |
| commit | 57cf995a474b76f5af2e3358a9dcc1c3dacec85d (patch) | |
| tree | cb6fb30357d80c44da7f34c32cb273587ab43801 | |
| parent | 25273a1431b61221dc364710b58a011c57cd6a49 (diff) | |
add @pablof7z's groups.
| -rw-r--r-- | 63.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -95,7 +95,7 @@ This NIP is payment agnostic, but that doesn't mean one shouldn't use zaps or nu | |||
| 95 | 95 | ||
| 96 | ### Future additions | 96 | ### Future additions |
| 97 | 97 | ||
| 98 | - more private list membership: perhaps doing an HMAC with the public key of the reader and a key that is shared with the relays will be enough for this. | 98 | - private group announcements: NIP-29 closed groups for subscribers can be announced on the `kind:10163`. |
| 99 | - tiered membership: custom tiers for fine-grained content access control can be added by adding a tag like `["tier", "a"]` to the `kind:1163` event and using a `["nip63", "a"]` tag in the events, for example. | 99 | - tiered membership: custom tiers for fine-grained content access control can be added by adding a tag like `["tier", "a"]` to the `kind:1163` event and using a `["nip63", "a"]` tag in the events, for example. |
| 100 | - teaser events: perhaps a `["nip63", "", "-"]` (negative) tag could cause an event to be displayed only to those that do not have access to its premium counterpart, this would also be managed by the relay. | 100 | - teaser events: perhaps a `["nip63", "", "-"]` (negative) tag could cause an event to be displayed only to those that do not have access to its premium counterpart, this would also be managed by the relay. |
| 101 | - relays for premium content different from the outbox relays? | 101 | - relays for premium content different from the outbox relays? |