pull down to refresh
43 sats \ 8 replies \ @ek 6 Sep \ parent \ on: Stacker Saloon
I might have found the issue on our side, we should subscribe before we send the request for ephemeral events according to the spec. Going to verify and give an update 👀
reply
reply
reply
reply
TL;DR: NWC vs LN address doesn't really matter; just use what is available to you. It probably looks cleaner in your wallet to use NWC since it can send+recv.
Mhh, it's a bit nuanced:
I wouldn't say NWC is the most reliable since you're using infrastructure that you don't control (nostr relays). However, @Alby runs their own relay, so there is some guarantee that this relay is well maintained. Additionally, this is more a theoretical problem. I haven't had any problems with Primal's relay ever for example.
The advantage of NWC is that you don't need to have a public IP and mess with firewall settings. You can simply use any relay to connect both ends.
However, if you already run your own node and have a public IP so we can reach you directly, you could run LNbits or phoenixd since both work with simple HTTP requests. Websockets are a bit more complicated so more could go wrong which is what nostr is using.
But I think in practice, it doesn't really matter if you use HTTP (LNbits, LN address, phoenixd, CLN), websockets (NWC) or gRPC (LND).
LNC is the only connection that does something really unique. Imo it's over-engineered and you can't even run it in multiple tabs at once so we need to always initiate a connection for every zap and then disconnect; making it pretty slow.
reply
Thanks! I've been patiently following your communication. Thank you so much! The way you explained this, I couldn't help to appreciate you. It is really amazing! Thanks @siggy47! Please do as much discussion on the 'connect wallet' as possible so that tech normies like me can enlighten.
reply