Depends on the client. I'm afraid I can't help you there. I only play around with iris to. https://nostr.how/clients
https://nostr.how/relays Those are the servers relaying the notes. Unlike email they don't talk to each other. Hence, you need to connect to the relays of others to talk to them. 90 seems a bit much.
ah, okay. that makes sense. didn't see that. But without authentication i can reply spam any relay, but thats normal spam handling, I guess.
Its more complicated than just whitelisting zappers, but its open and general. Delegated authentication would be nice in any case, I guess. Unfortunately it adds more work to the ln node too, so
its harder to support as they need to login to each relay.
Use NIP-26 to delegate authentication with NIP-42 to have zappers authenticate to payed relays on behalf of the user zapping.
The client would create a NIP-26 time limited delegation for kind 22242 and add it to the NIP-57 zap request. The zapper can then use this delegation to authenticate against payed relays and deliver the kind 9735 note. Relays would need to add a check of the delegation to their auth workflow.
This adds a little more load as as a relay needs to look for a delegation tag before dropping incoming notes. However there is no need to validate the delegation if the pubkey does not belong to a whitelisted user.
#[0]
#[1]
Good idea or bs?
How about delegations with a kind filter? github.com/nostr-protocol/nips/blob/master/26.md
I think there is a nip for that https://github.com/nostr-protocol/nips/blob/master/26.md
Your profile says GANDALF@BTCGandalf.com the part before the @ needs to be the username i.e. BTCGandalf not GANDALF. Make sure to use the same case in nostr.json as in your username At least thats what I think I figured out.
