I don't think I saw the issue you're referring to

Reply to this note

Please Login to reply.

Discussion

This has been discussed infinite times. If the relay wants clients to authenticate the relays can send an AUTH message immediately upon connection.

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

no wait

you didn't get it all

if the CLIENT wants to auth

there is no spec in the fucking protocol you moron

no spec in the protocol

no spec in the protocol

it does not say anything in the protocol about clients initiating auth

shut the fuck up, it needs to be in the protocol

put it in the protocol

or prepare for continuing harassment about your shitty go code

no i lied, i'm gonna rag you about your broken concurrency until kingdom come

you can't call yourself a go programmer if you fling around channels and goroutines like they are nothing

you are a noob, get over it, learn, become better

OK, I accept it, I am a noob. Can you tell me what is wrong with my concurrency code so I can get better? Give me an example.

what is that? Having many parallel threads running concurrently?

Why would the client want to authenticate to a relay that is not expecting that or prepared to handle that AUTH message? Or are you saying that the relay is prepared for it?