Yeah, false is correct since I hadn't AUTHed yet, but false as a string crashes my testing client which cannot deserialize the json.
Ah, so maybe my false response is malformed then? I will re-read the nip again..
I am basically hand crafting these responses according to the nip examples
see my response, i wrote all this stuff, i know it works, it auths on nostrudel and coracle, just the damn resource bug it's at https://github.com/Hubmakerlabs/replicatr in cmd/ingestr for client side, anyway, just check my other note here: nostr:nevent1qvzqqqqqqypzqnyqqft6tz9g9pyaqjvp0s4a4tvcfvj6gkke7mddvmj86w68uwe0qqszeyrlj2mcvggjzp2y9np52eyq4yjxu09wzzyret7zvqxskflcthsv9prp8
I will need to fire up mitmproxy to see the traffic on the wire. As far as i can tell, the code is supposed to be sending false like this falseString := fmt.Sprintf(`["OK","%s","false","auth-required: you must auth"]`, event.ID)
Of course, my own client doesn't send an event pre auth, so I would need one that does and inspect it's traffic. 😂 also nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug said he may have found a problem in amethyst where it wasn't retrying the event when it received a pre-auth "false". So... I still will try your tool at your leisure man, thanks for the halp! 💎
https://github.com/Hubmakerlabs/replicatr this should build for you now, i pulled in all those dependencies and made it a monorepo was pretty funny running it again... had all the configurations and a database already sitting on my disk and just fires right up anyhow, please reply if you get any errors with it now, i'm pretty sure i didn't exclude anything in the allowlist .gitignore but i buggered up the precomps in my revised embed version elsewhere (yeah, this whole mess happened because i kept getting git bugs and gave up self hosting after i had mleku.net/reponame as i wanted using legit but gd fkn git buggerization, haven't heard from the legit dev yet about a fix on it i filed an issue)
Ohhhh dude, I get what you mean now.. the relay tester wants a Boolean and I am sending a string 🤦♂️🤦♂️🤦♂️ big whoops, I forgot json had boolean. Ok I will fix this.
Hey Mike, ya the relay tester was right. I deployed a fix to change the string to bool and the auth test proceeded. Whew, relay tester ftw!! 💎
did you verify that it is a "CLOSED" envelope its supposed to send first then "AUTH" with challenge after? (and expect an AUTH with signed event containing challenge... in the content field??? i think? no, i think in the tag after "challenge")
https://github.com/nostr-protocol/nips/blob/master/42.md#protocol-flow yeah, that's the info there anyhow
Did you run my https://github.com/mikedilger/relay-tester or are you referring to me as your "relay tester"? 😂
Yes I ran it lmao!!! 😂😎👨💻