Oddbean new post about | logout
▲ ▼
mleku | 9 months ago (raw) | root | parent | reply | flag 
 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
▲ ▼
PABLOF7z | 9 months ago (raw) | root | parent | reply | flag 
 I don't think I saw the issue you're referring to
▲ ▼
mleku | 9 months ago (raw) | root | parent | reply | flag 
 https://github.com/nostr-protocol/nips/issues/1050
▲ ▼
fiatjaf | 9 months ago (raw) | root | parent | reply | flag 
 This has been discussed infinite times. If the relay wants clients to authenticate the relays can send an AUTH message immediately upon connection.
▲ ▼
mleku | 9 months ago (raw) | root | parent | reply | flag 
 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
▲ ▼
mleku | 9 months ago (raw) | root | parent | reply | flag 
 no wait

you didn't get it all

if the CLIENT wants to auth

there is no spec in the fucking protocol you moron
▲ ▼
fiatjaf | 9 months ago (raw) | root | parent | reply | flag 
 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?