Nostr Web Client

I believe #[5] implemented it, maybe worth tagging him as well

Just realized there was a plugin. A bit annoying that it needs (?) a private key to receive zaps, but I guess that's part of the protocol.

Please try again...

Reply to this note

Please Login to reply.

Discussion

quinsolo 2y ago

Zapped 10 sats just now

0xtr 2y ago

On Damus:

0xtr 2y ago

nvm, worked on second try

Sjors Provoost 2y ago

OMG!

faisal 2y ago

What changed? Can’t fetch invoice now

Sjors Provoost 2y ago

Mmm, I'm seeing this in the log:

fail: BTCPayServer.Plugins.NIP05.Zapper: Error zapping to wss://nostr.sethforprivacy.com

faisal 2y ago

That’s weird. Zapped now with a work around

faisal 2y ago

#[2] I think my connection is being rate limited unlike the rest of the crazies

kukks 2y ago

Yeah sorry, protocol design unfortunately :(

jb55 2y ago

Huh? The zapper key can be random

kukks 2y ago

Wtf? I assumed it was supposed to have been signed by the zapper else anyone can just lie about zaps from everyone?

jb55 2y ago

It does, but the zapper key itself can be a random key. Is the concern that #[5] had to use his privkey ? Maybe I misunderstood.

jb55 2y ago

Damus validates that the nostrPubkey matches the zap pubkey, and also validates the deschash

thesimplekid 2y ago

More clients should probably check this not all of them do

jb55 2y ago

That’s really bad. zaps are completely broken without that check.

Carman 2y ago

Yeah I did a fake zap to #[9] and could see it on snort

Sjors Provoost 2y ago

The plugin asked, so I gave it. I'm a simple man.

0xtr 2y ago

😂

jb55 2y ago

It should probably just generate a random key… it’s not supposed to be your key

kukks 2y ago

I was under the assumption that the nostrpubkey provided in the lnurlp should match the nip5 or the user being zapped so that the payment request is actually receipted by that same user? Maybe we cna make the nip a bit clearer if that isn't the case.