1 files changed, 1 insertions, 1 deletions
diff --git a/63.md b/63.md
index bffcd8c..732df18 100644
--- a/63.md
+++ b/63.md
@@ -95,7 +95,7 @@ This NIP is payment agnostic, but that doesn't mean one shouldn't use zaps or nu
 ### Future additions
- 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.
+- private group announcements: NIP-29 closed groups for subscribers can be announced on the `kind:10163`.
 - 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.
 - 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.
 - relays for premium content different from the outbox relays?

diff --git a/63.md b/63.md index bffcd8c..732df18 100644 --- a/63.md +++ b/63.md
@@ -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?