I was told that NIP-42 is “very easy” so why has nearly nobody implemented it in 3 months? Private relays are one of the most demanded feature on nostr.
We’ve had our relay running NIP-42 for nearly a month. Kollider’s subscription relay is basically unusable because nobody supports the AUTH standard.
nostr:note1zydl0pxnt33mdlg8d0p39gs3fym6gjpyee3hfn528mnxyu4hf88s8mmkuw
because users demand a lot from client devs, it’s hard to keep up
Just want to be clear I’m not blaming client devs I think the spec has a lot of unanswered questions on how you should implement it and I suspect that is part of the collective feet dragging.
plz don’t burn out jb55
Lol don’t put that on me, I’m offering a bounty publicly for any contributor to add it. Not trying to give Will more work…
I find this very interesting too. I felt a lot of pressure to add AUTH, did so, and realized no one else really supports it. So people are paying for private relays but unable to use them?
Yes, unknowingly too.
FYI: coracle upon connection instantly sends two REQ's:
["REQ", "REQ-82764758", {kinds: [1], since: 1681967605}]
and
["REQ", "REQ-81775670", {kinds: [1], since: 1681946005, until: 1681967605, limit: 20}]
To which an NIP-42 AUTH requiring server sends back 2 NOTICE's of failure (even though the server sent an AUTH challenge upon connect)
It responds to the AUTH challenge properly though.
The client should probably first use NIP-11 to get the supported NIPs - see that it supports 42, and then expect an AUTH challenge?
Nostr not having formal client initiated connect/auth makes this a little awkward.
