search

PrimalHQ / primal-caching-service

Primal’s caching service for Nostr connects to the specified set of relays, collects all events in real time, stores them locally, and makes them available to nostr clients through a web socket-based API.
https://primal.net
MIT License
85 stars 13 forks source link

Web client only connects to the cache #4

Open franzaps opened 1 year ago

franzaps commented 1 year ago

Primal only connects to its cache websocket 99% of the time, effectively making it read-only for me.

Liking, commenting, posting, zapping... nothing that involves writes works.

Just twice I saw it connect to a bunch of other relays which are not even my preferred relays, and those times likes etc did work (as expected).

Running it on Brave (Mac) but also tried Firefox - no luck.

nikolalukovic commented 1 year ago

Did you notice any errors in the console concerning those relays? Can you please update the issue with those error messages if there are any?

Also keep in mind that Brave shield is notorious for being too rigorous with websocket connections and it will just straight up block everything sometimes.

Have you tried doing this in Brave?

franzaps commented 1 year ago

For some reason it started working better lately (not 100% yet). I'll try disabling trackers next time it doesn't work, and paste here errors in the console. Should happen to all Brave users though right? You think it allows connection to the cache ws because of the same domain?

Interesting that I had the same happen in other browsers.

That said - the relays Primal connects to are not my preferred relays, not at all. All clients get this wrong (Coracle a bit less so). Maybe for another ticket 😄