fiatjaf is so toxic, he invented his own social network, so wokies cannot fire him
Words of wisdom.
There is no way to ensure a zap matches an actual payment.
At best, it can loosely represent a payment if both sender and receiver are honest. But then, they might as well use a more private payment method, like LNURL.
I suppose the best scenario zaps can aim for is an honest receiver + a fixed enough zap protocol, such that senders cannot fake it. Then build on top.
But IMO that comes with so much downside (centralization, newbies seeing zaps as LN standard, newbies being scammed by receivers who fake their zap counters, etc) that its not worth it.
Pushing the limits, love it
A bunch of reasons:
- Can be faked (at least two ways), skewed incentives: #[1]
- PR was rushed, feedback was ignored: https://github.com/nostr-protocol/nips/pull/224#issuecomment-1429286164
- Fragile design, not interoperable with paid relays or client auth: #[2]
- Easy to DDoS zap receivers = encourages centralization of LN nodes: #[0]
- Much less private than LN sats
- Requires LNURL changes (not interoperable with plain LN / LNURL, no graceful fallback)
You're fast! Yep nostr.band is much faster, thanks.
Not a fan of zaps, I'm more into plain simple LN sats :)
#[0] #[1] can you please put your NIP-05 aliases in the podcast ep description, instead of the pubkeys?
Tried to follow you, copy pasting pubkeys from phone to laptop was kind of a hassle :)
#[0] sometimes nostr.band loads slowly (>5s) because it's loading resources from unpkg.com.
Would it work to host them on the nostr.band domain?
It's a religion.
Many believers, which clouds judgement around zap pros and cons.
But at least the amount you want to be seen zapping
Since they're public and all
Depends how many core you have. For me, 8 hex chars took about 2 days, on a 8 core machine with 29 000 hashes/sec.
You can also mine on GPU: https://nitter.sethforprivacy.com/afilini/status/1609576086920171521#m
In the same vein, I was thinking to add "toggle buttons" at the top of the feed, one for each follow. Each would have the name and in paranthesis the number of new posts. Buttons sorted by no. of new posts.
Un-selecting one would hide all new notes from that contact.
Because of the 80/20 rule, a few profiles will have most of the new replies. So un-selecting a couple of them would free up the view.
This is the way
Good point. Are there wallets that support BOLT12?
Does LND see an issue with BOLT12? Or they just haven't prioritized it yet.
Maybe #[0] can help?
Same, although I do see a quasi-benefit to NIP-05: it's easier to tell others how to add you, compared to pubkeys.