This one works for me.
Getting into any block in the past couple of hours would have cost you more than €2. So if you hate paying more than 0.5% in fees, any payment under €400 is worth sending through lightning.
That or just wait a few weeks at 1 sat/vbyte and some custom rebroadcast code.
This only works if it's semi-automated on the sender side. The app should add tags based on keywords, which the author can delete before hitting send if they're wrong. That way, as a follower, I can have some confidence of not seeing the stuff I opted out of, without having to build such a filter myself.
[Insert AI buzzwords]
The more manual alternative is to have multiple identities (subkeys?) and have the app keep an eye out for when you post baby photos with your Bitcoin persona. But this is inflexible and requires the sender to decide on how to split things.
Some reader-side filtering based on other heuristics is probably still needed though.
[Insert AI buzzwords]
Or we just reinvent social norms about which topics are taboo in public spaces. Meh.
Maybe just setup an AI to bootstrap such a group :-)
“What are the biggest obstacles for NOSTRs success?” h/t #[0] https://twitter.com/ck_snarks/status/1652661119650000896
It'd be nice if we can point to a few npubs that don't talk about Bitcoin at all, and only occasionally about meta-nostr.
Said pointing is also a problem, since there's no permanent URL.
nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk this video doesn't play on my self hosted instance. Though it very briefly flashes a preview when the page loads.
Although Amazon sells the book, it's not published through Amazon KDP, for reasons explained in the blog post.
Instead I use IngramSpark (for self publishing). Downside is that they only have physical printers in the US, UK and Australia, which results in pretty terrible shipping times to some other countries.
Amazon tends to order extra books that they then spread over their network of warehouses. This results in faster shipping, and sometimes in steep discounts when they can't get rid of the inventory. They even sell at a loss sometimes.
https://sprovoost.nl/2022/06/01/amazon-and-the-dystopian-future-of-book-censorship/
Looks like nostr:npub155m2k8ml8sqn8w4dhh689vdv0t2twa8dgvkpnzfggxf4wfughjsq2cdcvg doesn't apply this limit to LNURL invoices. I guess it ultimately doesn't matter.
(I tried to post this as a quote-note, but it ended up as a reply, so here we go again)
In unrelated news: I broke my BTCPay server yesterday evening, but it works again.
You can buy the e-book or printer friendly chapter PDFs directly from me. The physical book is mainly available via Amazon.
Shipping physical books is an absolute pain and - at least in the EU - a privacy nightmare for both sender and recipient. That's why I don't do it myself.
But the layout on paper is much, much nicer. I wish e-book readers supported Latex. That said, one of the downloads you get from me is a PDF optimised for the typical Kindle size, which is _much_ nicer than the epub.
I also like the idea of having many physical backups out there, in case of a future digital book burning. Despite the price being higher, I make slightly less, but that's fine.
In unrelated news: I broke my BTCPay server yesterday evening, but it works again. You can buy the e-book or printer friendly chapter PDFs directly from me. The physical book is mainly available via Amazon.
Let's see what happens when I set the minimum invoice amount to 1 sat...
I'm seeing a ton of expired 0.00000000 BTC invoices in BTCPay related to my Lightning Address. I'm guessing it's a Nostr thing?
For example I zapped this message by nostr:npub1vadcfln4ugt2h9ruwsuwu5vu5am4xaka7pw6m7axy79aqyhp6u5q9knuu7, but I don't see this reflected yet. Having an overview of zap attempts may help debug issues with them.
It would be nice if Nostr apps tracked the zaps they sent. In particular I'd like to keep track of for which zap request I haven't seen the zap receipt yet. Since the app can't know which invoices were actually paid, a user should be able to delete entries from that list.
I see (2) as a feature, not a bug. You could use determinstic keys the way you suggest, but I think you should use random keys.
I often also want to do that for other people's posts. Perhaps the convention should be that a long press reveals that info, whereas a tap performs the action.
#[0] when I click on the like / zap icon of my own post, I'd like to see who liked my post, as opposed to liking my own post...