I always try to tell myself a story and keep myself entertained with my imagination as best as possible especially if it's a long one
its just lot of accidents
It's 11:00 p.m. here's a picture of my shoe
at this rate they're going to run out of null bits in the pow
not actually decentralized or censorship resistant in any way tho
would be happy to pay for using private roads
modern tech makes this aoy easier now
1. some apps publish the relays you use somyour followers can find you
2. many use nonstandard ways to do this
3. some apps allow you to specify a relay to use exclusively for the "global feed", thisnis cool and allows for specialized relays that are good at this task
4. needs to be standardized!
actually now its fine. whatever. i think the problem is the way these apps store relays
sometimes, was wack earlier. i think these clients all use their own hacked-up replaceable events to store stuff and wind up losing data when you move between them
just showed little/no feed for me today. even tho my relay list hasn't changed
#[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