but how does a relay deal with this? you didn't even think about that!

no, the relay just holds the connection open, pings and pongs, and ignores all inbound messages

that's the way that minimises traffic and computation

no wait

you didn't get it all

if the CLIENT wants to auth

there is no spec in the fucking protocol you moron

infinite times

where does it say this in the spec fffs

for fucks fucking sake

no, it does not say that in the spec

it does not say the client can initiate it

mister fiatjaf

please

stop being a twat

how does a client get a resolution out of this? lol

no, it requires ...ugh... a consensus driven distributed database

something that bitcoiners have in their blindspot because shitcoiners monopolized it

you are just fucking around now

how is that even an answer to my question??

end #madeira being in WEST and put it where it belongs in GMT

it's really bizarre to be normal waking up at "7:30" and the sun still isn't risen

ok maybe different on the south side of the island but it's super weird here on the north

getting used to it... lowering my expectations to an hour later

in general i'm up around 6 by that metric and working by 7 but the clock shames me with its 8

if anything, this is the clock that europeans want to run by

used to run by

until the EUSSR showed up to institute slavery

wat is dotless domain?

psychopaths are disgusting

trust your gut on this

disgusting means it makes you want to vomit and spit

of course they aren't. they are bought and paid for, didn't anyone notice the tether gold fiasco? and then the sudden radio silence?

there is a purge going on, be careful

yeah that is retarded

nip-11 already says auth-required

i send auth

i want auth

no auth

silence

ping pong ping pong ping pong

and no REQ

that's what works in the real world, i've kept my client open most of the time in order to gather intelligence about how retarded the clients are and that's my conclusion

unless you can forward a GTFO request upstream to your reverse proxy then just entertain them with silence

lol these stupid codes

i suppose if #coracle sends them out then it sends them out

ffs how exactly did this improve over relay lists?

also, when can we migrate from the retardation of bureaucratic number lists to human readable codes? you know, bureaucracks are fucknig inhuman right?

https://github.com/nostr-protocol/nips/issues/1050

moderated mode

btw, i see your client is sending your events to my relay... haha

it's what the relay should do if the clients don't respond with auth, to conserve resources

also, what makes you think that a client sending an auth envelope with a challenge is not a requirement????

there is a fairly high cost in handshaking that's the reason why i stand by what i say - just accept the connect, drop the messages, think like a firewall, what do you do to defeat a spammer? first port of call is ignoring them

i posted an issue about client's preempting auth in the NIP repository btw, maybe you saw that?

clients don't have any capabilities signalling and as it stands, relays hardly have it either, and neither side are really dealing with this problem, it's very elementary, bitcoin has had this since very early on with version bits

yep that's the correct way to handle it

but for relays, just gonna say it, it's less work to just keep the connection open and drop the messages because otherwise the dumbass clients keep reconnecting, and that's more noisy and higher bandwidth than just holding a ping pong

of course drop the connections if your websockets count is getting out of control but i think that's a pretty high bar to reach