TCP has checksums to guarantee perfect transmission and always acks every transmission. And websockets live on top of that, meaning more complexity/delays.
1) In Nostr events, the checksum is already in the event itself (id/signature)
2) Nostr is stream based (more like udp), we don't have to ack everything.
3) Nostr events have a standard format, meaning you can strip off the json during transport.
So in layer terms:
WebSocket -> TCP -> IP -> PHYSICAL
becomes
'NoStride' -> IP -> PHYSICAL
In a fully nostrified world, i can see a protocol for JUST nostr subscriptions be justifiable.
K, GN
quotingInteresting deep dive into TCP
nevent1q…h465
https://www.youtube.com/watch?v=rmFX1V49K8U
