I still maintain that alot of the recent issues around clients only reading from the top 5 relays would be alleviated by having http relay. Managing WebSocket subscriptions is a pain, I'd much rather just shoot out http requests to the different relays that a one off note may be found in.
Just like a website could show 100 images from different domains, we can fetch 100 notes from different relays with http reqs. I don't believe the narrative that http relays would impair client perf.
Agreed. Plus HTTP relays and clients could leverage standards like ETags and Range Requests to reduce network load, and include signing proofs for key ownership in headers.
WebSockets have their place when realtime communication is necessary. But the vast majority of Nostr clients don't require realtime communication, so why force developers to jump through the hoops to set up a full websocket subscription interface?
Yes. WebSockets have been the most annoying part of Nostr development thus far. Just had to refresh Primal a few minutes ago because the WebSocket connection was broken. ðŸ«
