Oddbean new post about | logout
▲ ▼
SLCW | 21 days ago (raw) | root | parent | reply | flag 
 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?
▲ ▼
Vitor Pamplona | 21 days ago (raw) | root | parent | reply | flag +1 
 It's not better. It's your only option today.
▲ ▼
SLCW | 21 days ago (raw) | root | parent | reply | flag 
 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.
▲ ▼
Vitor Pamplona | 21 days ago (raw) | root | parent | reply | flag +1 
 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.
▲ ▼
SLCW | 21 days ago (raw) | root | parent | reply | flag +1 
 Wow. I've never been the vanguard of a movement! I better get my good boots out of the closet.
▲ ▼
the axiom | 21 days ago (raw) | root | parent | reply | flag +1 
 maybe rewrite NIP 11 to say users must contact relay owners by a phone call
▲ ▼
SLCW | 21 days ago (raw) | root | parent | reply | flag 
 Yeah, the NIP-11 query should just return the server operator's home phone number. 🤣
▲ ▼
the axiom | 21 days ago (raw) | root | parent | reply | flag +1 
 lmao but then it wouldn't be updated
how do we fix this?
▲ ▼
SLCW | 21 days ago (raw) | root | parent | reply | flag +2 
 I think calling on relay operators to keep their information up-to-date is the only thing we can do. Maybe a "Have you updated your NIP-11?" signature on all your notes would help 🤷‍♂️