nostr:nprofile1qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0spzcs8wumn8ghj7un9d3shjtnyv9kh2uewd9hj7qguwaehxw309ahx7um5wgknztnwvfhjuctwvasku6fwvdhj78w5jyy after a few days I notice that apps connected to my alby hub (nostr:nprofile1qqs9xtvrphl7p8qnua0gk9zusft33lqjkqqr7cwkr6g8wusu0lle8jcpzamhxue69uhkummnw3ezuurpwfjhgmeww3hhwmspr9mhxue69uhkummnw3exx6r9vd4jumt99aex2mrp0yn7plng, nostr:nprofile1qqsrf5h4ya83jk8u6t9jgc76h6kalz3plp9vusjpm2ygqgalqhxgp9gpzemhxue69uhkzarvv9ejumn0wd68ytnvv9hxgqgkwaehxw309a3xjarrda5kuetj9eek7cmfv9kqs6xl8h, et c) become really slow when try to zap and sometimes fail. If I then renew the NWC connection it all speeds up fine. Any advice on steps I can take to resolve this?
Login to reply
Replies (3)
Annnnnddd I just saw the service status on my albyhub affecting nwc 😅 that explains it!
This is perfect timing to share something I have been thinking about. NWC over pear stack for P2P connections!
This could remove the need for a relay to facilitate connections using NWC. My first draft proposal can be found here: https://github.com/bjrb20/nwc-pear
You could also try having a second connection in ZEUS with NWC using a different relay.
Is that just adding an additional relay address in the URL?