pull down to refresh
236 sats \ 12 replies \ @itsTomekK 6 Sep \ parent \ on: Stacker Saloon
Hey, could you remind what exactly is the problem? (can be on our team chat, to solve)
@siggy47 do you have your Hub launched and Alyb Account linked? Do other NWC connections work for you?
Yes, I have my hub linked to my original Alby account. I am using the Alby NWC connect app on an Umbrel node for NWC send. It works well. When I generate a new secrets phrase and enter it in the app to receive, it times out without connecting. @ek can provide you with the technical details of why it's not connecting.
reply
Here's a video of the issue:
We are not receiving a response for the
get_info command which we need to check permissions. The bottom left shows all websocket messages. We send the request, we receive that the relay accepted (OK), we subscribe to the response (REQ) and it responds with EOSE which means it doesn't have the response yet (which is expected). But then silence.It works fine with cashu.me:
reply
reply
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.
I was also wondering about something else. Is there any chance you guys would consider a custom Stacker News wallet either as a standalone or part of the hub? I'm not sure what form it would take. It seems like it would be a perfect symbiotic relationship with Alby since SN is heading in the same direction with self custody and decentralization? I'm not sure what form it would take. SN users would jump on board pretty quickly, I'd imagine. The important thing would be ease of use to make the transition as smooth as possible for new stackers.
reply