Yeah was just thinking aloud. Elsat pointed out that highlighter.com offers subs to creators, but can't find out whether they actually work. From a function design perspective you want something with the least amount of efford for the user and as close to their existing frame of referrence as possible. Zap per post requires this shift in mindset that's quite high to overcome it seems...

There's also Fanfares but that makes more sense for larger pieces of content like audiobooks and such.

Reply to this note

Please Login to reply.

Discussion

It would be best to have a “subscription” feature built into a popular client such as nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg . It could even be something as simple as receiving a reminder/notification to support a creator you’ve opted into supporting, with a button to zap them. That keeps it optional and leaves the user in control. Typically subscribers would get access to content that others aren’t privy to, or at least access it earlier than others get it. They would eventually need to figure out how that would work on Nostr. Probably “early access” is easier to achieve than “exclusive access” because of the nature of digital content and how easily events are broadcasted around nostr.

"It would be best to have a “subscription” feature built into a popular client such as @primal"

I agree, the function fits with content specialized apps. especially since they already have a build-in wallet. This makes it much easier to configure compared to connecting a 3rd party wallet through NWC.

"Typically subscribers would get access to content that others aren’t privy to, or at least access it earlier than others get it."

nostr:npub16lvpp8hyxetuuczk4kjx2vqxhwmyruc72r59ysmgrsnjg5rcz8kqk07j3k build a function for this where notes containing content are decrypted upon LN payment.

Oh interesting, encrypted with the subscriber’s key? That’s clever.

The - tag should prevent trivial republishing; the rest is just good old pirating which will always exist.

Personally i think the zapbox relay model would work best:

follow = get free feed;

Pay = instantly just get the free+paid content aswell in the feed.

Most frictionless, client independent experience for the user. Publishers need to make sure they use the right relays that will comply with their chosen witholding scheme/metrics.

I lean toward the zabox approach too. A client could display those notes in a subscriber’s main feed, marked with a special tag or badge indicating that they’re seeing those notes because they’ve supported that author/creator. That communicates it as a reward and also encourages them to keep zapping that author if they want to continue seeing those notes, without feeling like the author is begging.

Zapbox itself might be a little bit bare; but a simple NIP for some receipt such that regardless of payment method, publishers could make it clear to the relays used what npubs are supposed to receive what should cover most usecases (including tiers and whatever).

The 'badge' is a nice idea, could indeed be a simple tag inside the event.

Boom, we just fixed substack, podcast subscriptions and whatever else.

Now im busy figuring out the spec for kidstr/TEPP (trust extended permission protocol), so someone else picks this up including a decent podcast standard and we can kiss RSS goodbye.