pull down to refresh
Thank you so much for your kind words! Honestly putting the whole piece out on StackerNews isn't that much extra work at all, so I really don't mind (quite the opposite actually!). I was more thinking that maybe stackers prefer links to discussions (when applicable), but if that's not the case I'm quite happy to continue posting the whole thing here.
PS: thanks for the shoutout on nostr 🙏
PPS: I'm running the whole newsletter stack myself, so there are good chances that emails fall in the spams folder. I see that you've successfully confirmed your subscription so you're all set, but some providers tend to put my emails back into the spam folder from time to time. I think adding to contacts or marking as non-spam helps, but I'm still a bit cargo-culting here. Anyway, thanks for subscribing!
Pretty neat UI, reminds me of UberEats, which arguably nails food ordering experience.
They don't say it on their website, but I'm guessing the way it works is that BitBite is hosting an instance of BTCPay Server and the merchant is just connecting their wallet to it.
Yup, Victor explains that users connect their Aqua wallet via the SamRock protocol.
Yup. To add to what @DarthCoin said, here's the basic rule around how changes are merged into the common Lightning spec:
Spelling, typo and formatting changes are accepted once two contributors ack and there are no nacks. All other changes get approved and minuted at the spec meeting. Protocol changes require two independent implementations which successfully inter-operate; be patient as spec changes are hard to fix later, so agreement can take some time.[1]
The splicing spec was merged now that discussions are over and there's interrop between Eclair and LDK[2] (and I think also Core Lightning[3]) it has been merged with 2+ ACKs into the main spec.
Yes, specification work takes time between drafting and reaching interoperability. Merged this morning.
Yep, node data doesn't even seem to load for me on mobile.