Replying to Avatar ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ

so, i finally understand why NIP-42 is not working for most clients

- most clients are nearly impossible to configure to test on one relay

- most relays don't support NIP-42

- only replicatr and khatru support NIP-42

so for the time being, us CLI bound relay devs are in a bind, and thankfully, we have people who get what is going on and are going to fund clients that work with our relays... or, mine, in particular

because without auth

there is no private business use case

and without relays with auth

there is no clients with auth

and there is no private business use case

and you all cry about adoption and you are not nagging your relay and client devs to actually FUCKING IMPLEMENT NIP-42 i don't know how fucking many times i have to repeat myself with this

IMPLEMENT

NIP

FORTY TWO
Avatar
nQuiz 1y ago

NIP-42 convenience link: https://github.com/nostr-protocol/nips/blob/master/42.md

Reply to this note

Please Login to reply.

Discussion

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

it's a really simple protocol

any reason, relay sends "["AUTH","challengesdring"]"

any time client receives this message, it signs a message:

tag with ["relay","wss://relayaddress"]

tag with ["challenge","challenge"]

and sign it like a normal FUCKIXNG EVENT

GITRDONE guys, seriously, just fucking finish this shit because we can't make money running relays without you cunts implementing it properly nor the relay devs, why does everyone still fucking praise strfry when the project is DED?