This is the correct answer. Relay selection isn't table stakes for new users. Use what your client recommends. Eventually you may want better privacy or an archive of your notes, at which pount hand-selecting specific relays or self-hosting becomes relevant. The key piece of advice for newcomers is: try to stay at 3-5 relay selections. More is not better!
Agree. I use a few specific types of relays. I think this will be the norm going forward.
True to your word with three relays 👍 Does that work with any three or do these have special powers? Aggregating from other relays etc?
Pyramid only allows cool people to write to it (this supports global, and stores my notes) hodlbod.nostr1.com is my personal relay (hosted on relay.tools, basically redundant with pyramid, but I control it, sort of) purplepag.es is an index of pubkeys to profiles and relay selections (allows me to find notes by any pubkey that has published a relay selection) It's really quite elegant
one day it will be trivial to start and run your own relay. then we'll be properly decentralized.
It's already not too hard if you have an umbrel or start9, or if you don't mind the compromises involved with something like relay.tools
Umbrel or Start9 make it super easy to setup, but people still need to use some sort of VPN or Tailacale to access their relay when outside of their home network. I have never used relay.tools, but I did use play around with relayable a bit when it first launched. It's definitely a nice solution for the average person to use.
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).
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.
@sandwich 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/
Nice! I realized talking to nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq35amnwvaz7tmwdaehgu3ww35x2umpd4jkxct59e5k7tcpz9mhxue69uhkummnw3ezuamfdejj7qgjwaehxw309ahx7um5wf6k2tnrdakj7qg6waehxw309ac8junpd45kgtnxd9shg6npvchxxmmd9uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uq3gamnwvaz7tmjv4kxz7tpvfkx2tn0wfnj7qgnwaehxw309ac82unsd3jhqct89ejhxtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsqgpxdq27pjfppharynrvhg6h8v2taeya5ssf49zkl9yyu5gxe4qg55zddau4 recently that migrating is a huge part of making outbox work. Planning to add some tools for this to coracle.
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.