{"type":"rich","version":"1.0","title":"Arjen wrote","author_name":"Arjen (npub1hw…465gr)","author_url":"https://nostr.now/npub1hw6amg8p24ne08c9gdq8hhpqx0t0pwanpae9z25crn7m9uy7yarse465gr","provider_name":"njump","provider_url":"https://nostr.now","html":"Thinking about it. Transmitting Nostr events over WebSockets doesn't make much sense from a networking perspective. It's quite inefficient...\n\nTCP has checksums to guarantee perfect transmission and always acks every transmission. And websockets live on top of that, meaning more complexity/delays.\n\n1) In Nostr events, the checksum is already in the event itself (id/signature)\n\n2) Nostr is stream based (more like udp), we don't have to ack everything.\n\n3) Nostr events have a standard format, meaning you can strip off the json during transport.\n\nSo in layer terms:\nWebSocket -\u003e TCP -\u003e IP -\u003e PHYSICAL\nbecomes\n'NoStride' -\u003e IP -\u003e PHYSICAL\n\nIn a fully nostrified world, i can see a protocol for JUST nostr subscriptions be justifiable.\n\nK, GN\n\nnostr:nevent1qvzqqqqqqypzpwa4mkswz4t8j70s2s6q00wzqv7k7zamxrmj2y4fs88aktcfuf68qy88wumn8ghj7mn0wvhxcmmv9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpq08yxppud2mgp6c37vj528rfqqt82gytzrve2szjkw67r9ymlshhqy3h465 "}