upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorfiatjaf <fiatjaf@gmail.com>2025-12-12 13:52:53 -0300
committerfiatjaf <fiatjaf@gmail.com>2026-02-02 00:08:24 -0300
commitb62a595fb654bcdfdfb4b6b8795b41673353f081 (patch)
treefced0b9b96f8c537085dced0cbff7601fe92265e
parentcef73cc4218801c5740e7a0de112378dac05bf97 (diff)
add individual pay-per-view events as a future possibility.
-rw-r--r--63.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/63.md b/63.md
index 1494aab..f0191d0 100644
--- a/63.md
+++ b/63.md
@@ -80,3 +80,4 @@ This NIP is payment agnostic, but that doesn't mean one shouldn't use zaps or nu
80- 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. 80- 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.
81- 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. 81- 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.
82- relays for premium content different from the outbox relays? 82- relays for premium content different from the outbox relays?
83- individual "pay-per-view" content.