Where hello is REQ and bye is CLOSE
Zapping is virtue signalling.
If someone wanted to send some sats, he / she would send some sats.
If someone wanted to send sats AND be known for it, he / she would zap.
Ideally no sound.
Sats are best received quietly and privately.
#[0]
Pick some from here: #[0]
It's less about what happened, more about what *could* happen.
Lots of good ideas in there!
Oak Node has a Nostr DM bot, where you control it via DMs.
Those steps become:
- find author's LN Address, copy
- go to bot DM thread
- /s user@ln-address.com 5000
Done. The bot sends 5000 sats to that LN Address, self-custodially.
The most recent version also supports "Shadowy LN Tips":
- click Like on a post (from any Nostr client)
- bot sends the author LN sats
Works from any Nostr client. Amount configurable. Self-custodial.
I do that via email, its fun to experiment.
What most zap providers don't realize is they have to be careful with state management.
Unlike receiving LN, receiving zaps = active tracking of pending invoices = memory + ongoing CPU cycles
Unless a zap provider adds a sort of "max pending zaps" ceiling, above which it wont accept new ones, until some are processed or expire -- then they're like sitting ducks for script kiddies.
That's the ultimate stress test IMO. On loop, open as many pending zaps as possible (but don't pay).
One of the many ways to attack a zap recipient
https://github.com/btcpayserver/btcpayserver/discussions/4642#discussioncomment-5074094
AFAIK Muun doesn't properly support LN Addresses: #[0]
What you have now is a LN invoice.
What you want is either a LN Address (like an email, user@domain.com) or a LNURL (lnurl...)
#[0]
Awesome, you figured it out.
Kudos for keeping an open mind and trying out new things like nostr!
Don't feed the trolls.
Influencers will make a killing on nostr.
Thanks. Got them as a simpe plain LN sats tho, my node doesn't talk zaps.
But bro, 69 sats? Change that amount, it has simp written all over it.
Anon zaps still link the recipient with amount received and time.
The difference is, with zaps you're documenting how much you sent, when, and to whom.
Cryptographically linked to sender and receiver.
With LN, that stuff's private, only you and the receiver know.
There are ways to do it privately, without zaps: #[0]