I found it. There's actually a few hardware wallets that support nostr keys. The Passport by Foundation, the COLDCARD MK-4 and the Q support nostr addresses, and LNBits makes a dedicated Nostr signing device.
The Primal Wallet is backed by Strike, which has strict KYC requirements. It's likely they don't service Canada, which is causing your problem. If you're on Android, you can connect an external wallet via NWC instead of using the built-in Primal wallet. I don't believe that ability is present in the iOS version.
I strongly suspect they have their own master keys that would allow them to access all your data, like if law enforcement came knocking with a warrant.
Given that there's a large number of techies from different disciplines on Nostr, I also think the instinct to resolve problems flows through most of the community. Whatever the motivations, it all comes together to create an altruistic problem-solving machine. It's really a remarkable thing to witness, and to be a part of.
That I cannot say. I'm deducing its methodology based on what we can see as users. I suspect it may not be preserving signatures, but I just don't know.
I think there is. I seem to recall a hardware bitcoin signer that also holds nostr keys. If it doesn't actually facilitate air-gapped signing, it's at least 90% of the way there. You'd just need a companion app, maybe even built into Amber, that read the NFC, or the QR and executed the signing. I just can't remember which device had the Nostr key feature.
I think it's a server (or collection of servers) that's running redis or something like it. It caches everything posted to whatever relays it's monitoring, and delivers it to the user on request. But posting new notes or replies goes through a user's defined relays.
I followed you regardless of whether I get the shirt or not! ✌️
I don't think It matters because Nostr isn't one thing, it's everything. I'd certainly welcome more platforms that are supporting freedom, but there doesn't need to he because everything can built on Nostr. It's a protocol that's wide open, and welcoming of development of all sorts.
I think your instincts are right on. An automatic process has the potential to go haywire. Providing an opportunity to manually retry is, I think, the smarter solution.
I use Rizful for my Lightning node, connected to Amethyst via NWC, and zaps are almost instantaneous. The purple wheel of death spins around very quickly, and the zap indicator lights up almost immediately. I don't use Alby anymore, but when I did it was similarly fast. I think the only times when it lagged were due to issues on the receiving end. Are you running your own backend, or are you using Alby Cloud to host your node?
If it's an Alby NWC, it would be using Alby's NWC relay, right? I think we'd expect the problem to manifest across the Alby user base if the embedded relay was the issue. No?
One of the things I really like about Nostr is if you're having trouble with something, whether it an issue with Nostr, or something with your wallet, or node, all sorts of people respond and start helping. It's like an ad hoc tech support. This is what community is all about. We're helping each other get over the speed bumps.
That was fine. It took a little under 10 seconds to complete from the moment I submitted the send.
That's a good point. It could be an issue with the backend node, and not with Alby.
Is it limited to zaps via NWC, or is this lag also apparent with direct sends and invoices payments?