Event JSON
{
"id": "21f89747573e60ee5668c8f8b7cab4f837fdfa3fc439c7decae76423f877fe79",
"pubkey": "308761407319e2c9faefe341a5cfa17060e25320e7c6bb4e33e3f2fecffb1126",
"created_at": 1725143679,
"kind": 1,
"tags": [
[
"t",
"nostr"
],
[
"t",
"relays"
],
[
"t",
"visualizations"
],
[
"t",
"dataviz"
],
[
"t",
"coder"
],
[
"t",
"coders"
],
[
"t",
"codersofnostr"
],
[
"t",
"programmer"
],
[
"t",
"programmers"
],
[
"t",
"programmersofnostr"
],
[
"t",
"nostrdevs"
],
[
"t",
"dev"
],
[
"t",
"devs"
],
[
"t",
"devsofnostr"
],
[
"t",
"nostrprogrammers"
],
[
"t",
"nostrcoders"
],
[
"t",
"protocol"
],
[
"t",
"nostrprotocol"
],
[
"t",
"websocket"
],
[
"t",
"http"
],
[
"t",
"tcpip"
],
[
"t",
"tcp-ip"
],
[
"t",
"nextjs"
],
[
"t",
"lambda"
],
[
"t",
"serverless"
]
],
"content": "Does anyone know why the Nostr protocol specifically requires a WebSocket connection? Has the matter been well discussed before? \n\n\n#nostr #relays #visualizations #dataviz #coder #coders #codersofnostr #programmer #programmers #programmersofnostr #nostrdevs #dev #devs #devsofnostr #nostrprogrammers #nostrcoders #protocol #nostrprotocol #websocket #http #tcpip #tcp-ip #nextjs #lambda #serverless",
"sig": "3fbfecb1ac0eb447fd87e1bffb3f50d34160f8518a251dca87cdbbe61510f7343c7608271ffc6184cc1b719f39aac23c6839f7e5f11c1a990b917eef98d169e2"
}