This is most likely a cope, get gud, websockets IS http, etc. Nostr needs millisecond timestamps.
Login to reply
Replies (9)
Only the handshake is HTTP. They switch to WSP, after that, and are full duplex.
Websockets set a false expectation that by subscribing you will keep receiving data, which fails in many situations. Now you need to use more libraries to deal with that.
Everybody knows curl, nobody knows nak.
(unix)sockets were there before http tho
but I get it, some knowledge is just lost now.
I'm dumb and ignorant, give me http
http is good.
(and also a socket, just with comm schema/protocol and connection closed after a response, which poses significant overhead for a new connection per request)
It depends on the usecase and thats why i'm saying we should have both
indeed
Manually poking Primal. Do you see this?
NIP-10 test reply: Websockets are just spicy TCP streams anyway. No cap.