What I find promising are recurring subscriptions from people who find value in the work.
I like Gigi's approach here. At the end of each article, he puts a LN address and a link to a donations page.
NIP05 alias is good.
Sometimes a new concept comes up, for which there's no word yet.
Like pizza. There's a reason every language adopted this italian word.
Payment to your LN Address worked (just tested).
Could be it didn't work for Mike because of the DNS issues he mentioned. Paying to LN Address involves resolving domains.
In this case, the most resilient way would have been to send an invoice. Paying it doesn't touch DNS.
Zap = LN payments + nostr metadata.
For privacy I'd just use simple LN tips.
Here's someone doing great work on NIP26: #[0]
There are ways to view nostr notes on websites, like
https://www.nostr.guru/e/3775df1714bb6ec14f5db0447bc0d6468d39ba2931f384e4f5f978389b86e114
Dark mode. The new Bootstrap should support it out of the box.
Pointer to better UX, agree. NIP-05 is very handy.
But sharing npub keys is not wrong. NIP-5 is a pointer to the pubkey after all.
Cause that's like saying "this girl looks so hot in this picture, here check it out, but if you go talk to her in real life that's wrong"
All I'm saying is zaps are a step backward re privacy.
Compared to LN by itself (LNURL or LN Address) which is more private by default.
And easy to DoS because monitoring all those invoices means keeping state, which takes resources.
Especially when creating a zap request (i.e. binding resources on the zapper) is free, just takes sending a nostr message.
No, they have the power to publicly cryptographically document who is supporting dissent
You only need to add the hex, not the npub.
Check out gigi's json: https://dergigi.com/.well-known/nostr.json
I hope Alby will still suppot normal LNURL tho :)
It's not all about adoption. Fiat has the highest adoption. UBI is certainly very poppular with the people.
Sometimes the right thing to do is not the popular thing.
By "read the NIP", I mean read the PR comments and feedback.
The reason is that NIP-57 is badly designed, with no interoperability with existing LNURL or LN Addresses. In fact, you cannot support both zaps and normal LN Addresses or your profile.
Read the NIP.
People celebrate that it was merged as a sort of accomplishment.
No, it was merged because it turned out feedback was being ignored and multiple parallel implementations were being pushed, regardless of the issues raised or improvements suggested.