Right now, the app communicates with Amber through a few hard-coded default relays, so users have no options to change them. I was considering ways to ease this problem, like letting users select some relays or adding 127.0.0.1:4869 to the default list.

However, if other apps aren't having major issues, it might not be a relay connection problem. Amethyst and Primal are native clients, so they wouldn't use relays in the same way, but zap.stream is a web app and should be communicating through relays.

nostr:npub1vxd0dfst8ljvwva2egrpc53ve8ru78v8aaxfpravchkexmfmmu3sqnrs50, has your connection issue been completely resolved since we added some other relays?

Reply to this note

Please Login to reply.

Discussion

Oh I'm using the zapstream app. Let me try the web app.. Looks like there is no option to use a bunker on the web app. Only extensions.

So I created an nsecbunker with local Citrine as the only relay and that seems to work 🤞

Yes. Never had any more problems since more relays was added.