rich1.0Arjen wroteArjen (npub1hw…465gr)https://nostr.now/npub1hw6amg8p24ne08c9gdq8hhpqx0t0pwanpae9z25crn7m9uy7yarse465grnjumphttps://nostr.nowThinking about it. Transmitting Nostr events over WebSockets doesn't make much sense from a networking perspective. It's quite inefficient...
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
nostr:nevent1qvzqqqqqqypzpwa4mkswz4t8j70s2s6q00wzqv7k7zamxrmj2y4fs88aktcfuf68qy88wumn8ghj7mn0wvhxcmmv9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpq08yxppud2mgp6c37vj528rfqqt82gytzrve2szjkw67r9ymlshhqy3h465