We will need a better way to advise users on which relays they can pick from... maybe by testing if they are suitable and saying "pick again" if nothing else. Because relays are not at all uniform anymore, and most don't work as good inboxes (for example).

Reply to this note

Please Login to reply.

Discussion

Users can't tell what is read-only, white-list-driven, or paid. Only #Nostrudel gives me any feedback.

I'm glad to hear Nostrudel is giving some information on this.

But I can't live without strudel.

Nostrudel is the ugly all powerful swiss army knife of nostr clients. ;-D

nostr:npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx and NIP-66 might provide some valuable information to give sane information here

How is migration supposed to work? The client just download the entire user history of events and rebroadcast them?

I did that kinda manually. There should be tools for that.

Just did a migration. Set it up in about 2 minutes with https://github.com/sandwichfarm/nostrawl/

Totally. If someone changes their relay list, outbox doesn't know it existed. In a perfect world, NIP-65 would also store timestamps for when a relay was added. When removing the relay, clients user events from that timestamp. Or otherwise, relays are not "removed" from NIP-65 lists, but marked inactive and marked with a timestamp indicating when the user left.

pre-coffee notes are imperfect.

post-coffee

*clients would sync events from that timestamp to other relays.

*but marked inactive with a timestamp indicating when the user left.

Not a bad idea