#[2] is definitely trying to simplify things for newcomers into the space!
#[0]

Sorry just over here nerding out over how freaking smooth #zaps are on #[2] 🫠🫠🫠🫠 https://nostr.build/av/c94d0075ea63bda078d9ac490c625278b4d9b23e58e856b803e6bcdd6a2bec4d.mov
buttery smooth
Is this why your npub spells EARN?
nostr:npub1rvg76s0gz535txd9ypg2dfqv0x7a80ar6e096j3v343xdxyrt4ksmkxrck
There's a spelling error here in the app "Adress" 🤝.
Also one question, what happens to old gamertag/lightning address if changed?
Is available to register by someone else, is banned or is redirected to user's new one?

Nice catch! We'll fix that up real quick.
And yes, think of it like a username. If you're no longer using it, someone else can claim it.
#zbd makes #Bitcoin cool
🤙 
They’re coming. Stay tuned 👀
That’s not how it works. Keys are hot in memory, not on disk. They’re different.
Oh I fully agree. Not saying otherwise. PIs are NOT for Lightning nodes imo 🤷♀️
Yeah for sure. My issue is not at all w hosting nodes. I think that’s wonderful and necessary. My concern is more w those that use marketing tactics to suggest something that is factually untrue.
Yeah I’d argue AWS has even more control indeed.
My problem isn’t with how this is handled, my problem is with the disingenuous marketing that states “run a node noncustodially in our servers and keep your keys”. It is categorically false.
How does it sign for channel updates? Sounds really cool.
https://primal.net/thread/note1unuvhr7wjg2h3eg2py9lwmvltwh7g08ra5w8g2qm3zmspf2nh9esx68r8f
I think the original post explains it well
Yeah I think this is where we'd want to be moving to in the future. Though I agree not sure if it's `verifiable`. It's very tricky.
