Replying to Avatar fiatjaf

I've made this other relay now: https://zapbox.fiatjaf.com/

First you have to set up a zap threshold, afterwards anything you publish there will only be shown to people who have zapped you at least that threshold in the past 3 months.

All the rest is the same as a Lockbox:

nostr:nevent1qqsqqqzxnr8xcfku28py2nwvg4p8hh8va7zy0kps6wn9tfld0me8aagpz4mhxue69uhkzet8d9ejuat50phjummwv5hszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9udxdewy

Really cool. This zapbox relay can work really well as a "Patreon style" reserved area for subscribers, without the hassle of managing a monthly payment. You can also have more zabox relays with different thresholds, and users will automatically fetch notes for their tier.

Reply to this note

Please Login to reply.

Discussion

Exactly, that is the idea.

Maybe the relay could return an explicative note (every 24 hours) when the user queries a specific author but the threshold is insufficient, so he is alerted, can zap him and access again the content.

A nice variant of the relay could be use its pubkey as zap target, and allow reading all notes from authors that have write access. This would work well for a team (e.g. a magazine, a project, etc).

The problem is that if you're querying a specific author then the relay can't return a note from someone else, that will be discarded automatically.

I like the idea of relays as zap targets. That fixes a lot of things. Would be nice to have that built in clients somehow.

genius

You are right, a note by the relay could be filtered out if the client enforce the the REQ filter on the results. Maybe it's a job for the NOTICE response, is it currently used somehow?