#[0] nip-02 says the content should be ignored, but all major clients (iris, amethyst, others?) use it to serialize the set of preferred relays.  indeed, publishing a contact list with no data can break some clients. should we document that use case and add it to nip-02?  or deprecate it and refer people to nip-65 (which is inadequate, and is likely why clients are using nip-02) my suggestion is to:  - document it  - update nip-64 to include the additional relay flags besides read/write that people are using (as well as documenting extensibility) that way people can stop accidentally wiping out their relay sets by trying other clients

iris has been busted recently, moved to coracle.   not sure what's up.

i still can't get over how ridiculous ibm's "tomatoes on the blockchain" was it's a summary of what's wrong with big tech these days

it would be cool if my client suggested relays to me based on who I follow like if 10% of my followers you some relay that I don't have I'd like to know about it I get that clients might do this kind of thing automatically and in the background but it would be nicer if it was explicit