i just have one simple request

every client should respond to an auth challenge envelope with a request to the signing tool to sign the event to auth to the user's key

every client

a relay should be able to respond to EVERY request, as well as immediately respond upon connection with an auth envelope

sign the challenge in the content of an auth response envelope and send it back

it SAYS IT RIGHT THERE IN THE GODDAMN NIP-42 text are you people blind?

my relay at first only sent it in respons to req envelopes and got nothing happening most of the time

then i upped the ante and it was sending auth challenges immediately upon a websocket opening

still nothing, and all the clients didn't work

you are all wrong

it says very clearly in nip-42, which some of you claim to have implemented, that the client should fucking sign the challenge and send the reply back

then, my relay is happy, and it will give you whatever you deserve

and the most important thing that you motherfuckers don't get is this

why the fuck should a relay deliver a kind 4 or kind 1059/60 to you, or a 300iforget application specific data kind message, unless your fucking pubkey is in the fucking message?

why? why why why why why why FUCK YOU WHY?

cos none of your shit does, and it is something i've been complaining about for almost 2 months!

says so in the spec, none of you fucking do it, for two months, including my salty ass yelling about it

get on with it, fucking implement always respond to fucking auth challenge envelope with auth response with authed event signature it's not fucking rocket science, ok?

sweet baby jesus is crying on behalf of all you sinners

😂🤣

I have no idea what this means but it’s awesome regardless. Hope someone listens 😂

Reply to this note

Please Login to reply.

Discussion

i hope so too because it's making me want to set them all on fire

🔥