Is it just me that get random "bad handshake" errors when trying to connect to healthy relays sometimes?
Discussion
I think these Golang websocket libraries are all broken.
Alternatively, the websocket protocol is another victim of Google stepping in and "embracing" it but adding pseudo-optional features to it such as compression and weird parameters that not all libraries support in the same way but some will assume others do support.
What was the motivation to use websockets over grpc streams?
grpc is not an application level protocol, it a rpc technology on top of http2. Different level of abstraction, not a direct comparison. Plus it’s a pain in the ass to setup grpc.
The motivation was that I had never heard of gRPC streams. The only alternative I've considered was SSE, but since that is one-way communication I thought websocket would be much much simpler to implement and the performance/reliability would be basically the same.
Maybe in the future we just have Nostr as an application level protocol on top of UDP just like http3. We don’t need all these http websocket bullshit then.
It's not bullshit, it is really simple and helpful -- except for the fact that there are these weird "protocol extensions".
No, happens to me too sometimes.
Relays are probably overloaded and the initial connection fails.
Would be good if that was the case, then I wouldn't have to write my own websocket library.
Eu não consigo excluir alguns alguns, identifiquei um q é a causa da poluição no meu global! Existe alguma razão para isso? Será que sigo alguém que usa esse relay específico q me obriga a estar conectado?