Depends on the circumstances.
If you have a channel with a mostly trusted counterparty, B.
But in a decentralized environment where you have channels with totally untrustworthy peers, A.
When client side AI dick detection?
What specific setup are you using for receiving nostr zaps?
Well they're used to things like Facebook which take weeks or even months to actually delete anything.
One UI compromise could be to require people to enter in their seed (or part of their seed) for delete to work.
Do you guys also ever make finger guns when zapping? 😆
https://giphy.com/gifs/stephen-colbert-finger-guns-television-2CcKiHPDsJqVi
"Finger Gun" would be a hilarious name for a lightning wallet.
#[0]I tip with a wallet connected to my own node, so I'm earning routing fees every time I tip! 😁😁😁
Words can be investment advice. No surprise that emojis can be in the right context.
Same.
Low value payments have really good reliability.
It's a pet name, not a global name space. So no such thing as reserving one.
NIP-3 specifies how to use OpenTimestamps to timestamp events, proving they existed prior to a point in time: https://github.com/nostr-protocol/nips/blob/master/03.md
But it may also be useful to prove events were created _after_ a point in time. The easiest way to do that would be to add a tag with a recent block hash to every event you create.
Speaking of... https://github.com/rust-nostr/nostr/pull/40
NIP-3 specifies how to use OpenTimestamps to timestamp events, proving they existed prior to a point in time: https://github.com/nostr-protocol/nips/blob/master/03.md
But it may also be useful to prove events were created _after_ a point in time. The easiest way to do that would be to add a tag with a recent block hash to every event you create.