Funny, I ended up with two rejections too, but they're different relays. I wonder if 500 errors end up being shown as rejections in coracle...
Discussion
i'm gonna hazard a guess that this is a technical glitch, possibly all those relays are on the same data centres. 500 errors mean misconfigured or broken web server/reverse proxy.
Right, my point was "rejection" might be the wrong way to show 500 errors in the UI.
test
test2
Never tried to debug websockets before, but at least relay.orangepill.dev looks reasonable
["OK","7604fef7067a081a2271876212df761042ea9208b91c08a38b86b2507300d299",false,"blocked: pubkey not admitted"]
Interesting I don't see this "OK" message in nip-01 but coracle understands it so it's probably specified elsewere. (Who thought "OK" was a good code for a fallible response? lol)
pubkey not admitted? doesn't this mean that something in the relay has blacklisted the key?
Could be, or the relay operates on a whitelist (more plausible imho, I haven't done anything I could imagine would warrant being blacklisted)
also, because you mentioned NIP-02 i went to look at the repo and found this: https://github.com/nostr-protocol/nips/commit/37f6cbb775126b386414220f783ca0f5f85e7614
yeah it does seem like a little more info is warranted but web devs like to quit their error handling at "something went wrong" since it's assumed all users have no idea what goes on in the background.
oh yeah, it could also be my VPN. i appear to be coming from the data centre where mleku.online is also hosted. i had problems before with alby because of my vpn service with russian owned IP addresses in bulgaria and moldova.