I feel like I missed the start of a big fight here.
Anyone want to boil that ocean down for me?
Login to reply
Replies (10)
Amethyst's Viktor went Gleason-levels of chaos and added on-chain zapping with a re-usable address. Damus dev is having a no-good, terrible, horrible very time time with it.
Now it makes more sense. Thank you.
Alex is covered in jizz 💦💦 from some select devs, Will is keeping it real
Since your nsec/npub are actually bitcoin-compatible keys, you can actually send on-chain transactions to npubs.
Ditto and now Amethyst are adding that as a feature. Some people have opinions about that.
because @jb55 is actually competent.
while I disagree with them a bunch about nostr + bitcoin (rereading the DB on every frame should be a crime), they still understand most of this better than the average vibeslopper
what nostr client do you recommend for android?
Gleason is gaslighting/trolling everyone who raises the obvious issues of address reuse, dust, chain fees, non hd derivations and linking real world id in an nsec to a utxo as cultist bitcoin retards who hate bitcoin.
I think it's a nothing burger
nostrdb is not much slower than an in memory hash table tho. benchmarks confirm this. nothing wrong with doing it per frame
there is the initial page fault loading time which should be done async, but once its in page cache its 🏎️