protip:
don't use sockets on a protocol unless you build clients in paralel with the servers
most front end languages don't cope with concurrency and keeping track of 3-50 separate relay connections and what has been going on with them is like,
"computer says no"
javascript = 1 interface thread, one service worker thread
to manage all those sockets, ping and poing and all that?
why do you think HTTP is a simple request/response protocol and that's what 99% of the web uses?
yeah. think about it.
mleku
npub1fj…mleku
2025-05-24 20:24:23
Author Public Key
npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmlekuSeen on
wss://nostr.momPublished at
2025-05-24 20:24:23Event JSON
{
"id": "ac7adec22623c8d4e43175049cbebc5fdd1bbec87960014ee1eced1c16c039a2",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1748118263,
"kind": 1,
"tags": [
[
"client",
"noStrudel",
"31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546"
]
],
"content": "protip:\n\ndon't use sockets on a protocol unless you build clients in paralel with the servers\n\nmost front end languages don't cope with concurrency and keeping track of 3-50 separate relay connections and what has been going on with them is like, \n\n\"computer says no\"\n\njavascript = 1 interface thread, one service worker thread\n\nto manage all those sockets, ping and poing and all that?\n\nwhy do you think HTTP is a simple request/response protocol and that's what 99% of the web uses?\n\nyeah. think about it.",
"sig": "c8dac94b3e9d7443fa997114d9b4447493511564fb27c16ded867933e5846cff16c9a4d2aa64ac21c5bbf5539b583b3a1c84c863bbb32fd9506175ec028d187d"
}