nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl are you aware that #jumble doesn't auth when the relay sends an auth challenge on connect?

i didn't want to have to complicate my code by handling the "challenge on arbitrary request trigger" so i just make it send the auth request if auth is required, before it even starts handling received messages.

according to NIP-42 spec this should be respected.

Reply to this note

Please Login to reply.

Discussion

i guess i'm gonna have to add one more point where it asks if it's not already authed for this problem, when i looked at my code i realised it wasn't enforcing any policy on event upload!

and then it isn't authing.

and i'm getting some weird socket error too, about the message not being valid UTF-8 when it receives the auth challenge