so, since the clients are retarded about auth, i think, since they do auth, but then forget to send the event again, i will add an unapproved queue to the socket so if it happens to auth, the events get saved, anyway
i mean, seriously, jumble, coracle and nostrudel all do the same thing, send event, then realy sends closed auth-required then they auth and then... silence, and then usually they disconnect the socket in time for you to try and send again... so now, it can just save events if it gets auth
idk even what to say, do you client devs actually test this?
mleku
npub1fj…mleku
2025-05-24 16:48:44
Author Public Key
npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmlekuPublished at
2025-05-24 16:48:44Event JSON
{
"id": "c32ba5fe5854a507776f261d5422a30cc260a2439ad142664489de276ff77f17",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1748105324,
"kind": 1,
"tags": [
[
"client",
"noStrudel",
"31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546"
]
],
"content": "so, since the clients are retarded about auth, i think, since they do auth, but then forget to send the event again, i will add an unapproved queue to the socket so if it happens to auth, the events get saved, anyway\n\ni mean, seriously, jumble, coracle and nostrudel all do the same thing, send event, then realy sends closed auth-required then they auth and then... silence, and then usually they disconnect the socket in time for you to try and send again... so now, it can just save events if it gets auth\n\nidk even what to say, do you client devs actually test this?",
"sig": "e6a048b30cad00a510642bf336615a308c5a12e83cfcc502ab883e6d991445ea6ee8cecdb96ab39691a205951aa43aaba285c7eb2f4072517862a4b1bfb9a7bb"
}