We don't need a NOTICE, what NIP-42 says is that the relay must answer with a CLOSED or an OK with messages prefixed by "auth-required:".
Perhaps this all needs to be clarified in the NIP. I also have had trouble implementing AUTH. It still doesn't work consistently, with some relays or clients I use, even though nostr:nprofile1qqsqvcu68pkfcyq5y9mz9n9u7sys33835rpnuglc6mtg7j4lv40c7ugpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3vamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmnyqyg8wumn8ghj7mn0wd68ytnhd9hx2erc6wa has been legit on top of things and trying to help me.
I'm not necessarily convinced that we need an extra notice. And it's been frustrating to see how slowly a relatively simple, important NIP has been propagated, and that might be due to a lack of clarity and completeness.
nostr:nprofile1qqs8qy3p9qnnhhq847d7wujl5hztcr7pg6rxhmpc63pkphztcmxp3wgpz9mhxue69uhkummnw3ezuamfdejj7qgmwaehxw309a6xsetxdaex2um59ehx7um5wgcjucm0d5hsz9nhwden5te0dehhxarjv4kxjar9wvhx7un89uqaujaz how is your AUTH implementation going?
Discussion
Okay, we'll do an in-project review of the NIP, with our relay and client devs, and maybe test it with some Gherkin. We needed to do that for Aedile, anyway.
We'll see if we can get the interop smooth, with the current state of the NIP, and submit PRs to the various client/relay repos and/or NIP repo, if we find inconsistencies.
This should be a solvable problem.
As we shift towards SDK development in Aedile, these standards are going to become way more important. I think we should host Gherkin write-ups of the NIP specs on Alexandria's relays as we determine the implementation details for our SDK.
With expected behavior precisely defined in Gherkin, we can go back-and-forth with the other devs to figure out if the Gherkin scenarios actually match the implementation and usage "in the wild," and work on updates or clarifications to the NIPs from there.
I've already written up some Gherkin for NIP-46. I think NIP-42 will need the same treatment.
nostr:npub10000000thpep7auj058803nqtymqlf3rw87lzhe6mkfeywnpxg5sjw7nql any ideas of expected nip-42 behavior for apps, relays that we can specify?
Client SHOULD authenticate with NIP-42 when they receive an AUTH as that indicates that there may be additional features available post-AUTH.
Such as prioritized responses, access to certain content (no, refusing an entire request with auth-required does not work, and neither does trying to figure out what requests want what with heuristics)
i know, that's why my relay doesn't work with the shit that NDK uses