Oddbean new post about login | logout Both auth.nostr1.com and inbox.nostr.wine were made for nip-17. :) But most relays accept it.
I agree they should support NIP-17, but last I checked, they do not.
I don't understand what you are saying. I have used them daily for over 9 months now. They fully support it.
If you click on the relays in the Amethyst relay list, it shows which NIPs the relay supports. Neither show NIP-17 as one of the NIPs they support. The NIP-11 info document for those relays also do not indicate support for NIP-17.
That's just old info from their relays... No relay operator ever changes that information.
Isn't the NIP-11 document automatically generated based on the specific configuration of the relay server?
No. It should be manually adjusted by each operator. And no one changes that.
So what's the point? How are we supposed to know which NIPs a server supports if nobody bothers to maintain their NIP-11?
Nip-11 is irrelevant. You shouldn't do anything based on it at this point. Just talk to your relay operator. They will tell you if they support or not.
That's a pretty inefficient system. We're abandoning NIP-11, which automatically reports server compatibility, in favor of manually contacting all your relay operators to ask them which NIPs their server supports? Why is that better?
It's not better. It's your only option today.
Ok, but is there some push to reestablish the accuracy of NIP-11 reporting in relay servers? For the time being, it's not a problem to contact relay operators to ask them what their server supports, but that's not sustainable longterm.
Not that I know of. Users don't seem to care if their relays are writing accurate NIP-11s or not. You can start the movement.
maybe rewrite NIP 11 to say users must contact relay owners by a phone call
Yeah, the NIP-11 query should just return the server operator's home phone number. 🤣
lmao but then it wouldn't be updated how do we fix this?