Yes. Great stuff.
And in nostr when you change relays in your relay list, and move your data, you have done a similar thing. That is, USERS can move whenever they want, to evade censorship, etc. But RELAYS cannot. With pubkey in a sense, the RELAY is the USER.
But in nostr you can have one set of relays for sending things to the world (outbox) another set for receiving messages (inbox). In pubky you just have one, right? So on the data side it is less redundant? I could be wrong on that.
If I run my own Outbox, how can I tell the whole world about it if they 10 relays every one reads from censor me by decree from USG under the threat of unpersoning the relays owners aka sanctions?
If people only read from 10 relays under USG control, nostr won't survive that. I have 3,881 relays in my gossip client relay list. Granted most of those are junk. But there are far more than 10 relays. When I advertise my relay list I generally hit about 100-200 relays with it. For sure some of those are in China, Russia, Iran, etc. So this situation isn't close or likely.
This might be fine if nostr stays small for pocket/private networks, but for social media, marketplaces, etc... nope.
Good to hear, but this sounds like an adhoc gossip network. We don't need to reinvent overlay networks, we know that DHTs scale, gossip doesn't. Gossip only work when you are already cursed with the need to replicate a dataset in full.. for everything else, sharding aka DHTs are the optimal solution.
The 200 relays you reach, are not likely to be the ones I read from, and if it is likely, then it means these relays are under too much stress and they will churn or drop your data soon.
Nostr is good enough for sure, but physics is physics, and the Web needs a DHT or ICANN... these are the choices.
I agree DHTs are the superior solution. The odds that the 200 relays I used do not overlap at all with the ones you search are vanishingly low when we are inspired to use the most popular of relays. Is that a centralizing force? Yes, but a modest one, and what is popular changes ovrer time. Nonetheless it is clearly inferior to the DHT. Which is just one of the (many) reasons I'm working on Mosaic.
I honestly cant follow this degree of equivocation.
It just sounds like nothing means anything and everything is the same even though all of it is totally different...
Pubky currently supports modular optional indexer(s) and homeserver(s).
Indexer can pull from one or many homeservers, or anywhere really.
Apps can rely on indexer(s) or not.
I'm sorry that it sounds like meaningless equivocation to you. Maybe you don't understand enough about how nostr works.
In nostr, to find somebody you look for their kind-10002 relay list. The spec says to spread that thing as far as you can. Relays are all supposed to host it if they support NIP-65. Just one per pubkey, a newer one replaces the older one. Inside that signed document you specify which relays you are using. At any time, you can change those relays and publish a new relay list document.
If you are using 5 relays (3 for outbox, 2 for inbox), then one of those outboxes decides to start charging, you go find a new provider, copy your data from the bad relay (or better yet one of your other trusted outbox relays) to the new provider, and update your relay list.
Instead of registering an endpoint in the DHT, and updating that whenever you like, you publish multiple endpoints in a relay list and update that.
Outboxes are where people come to read your posts. Inboxes is where people drop messages to you. Because I don't follow everybody who replies to me, I can't expect to see their replies on their outboxes, so they have to copy me on my inbox.
So in nostr you specify MULTIPLE relays. I'm not sure but with pkarr you specify one homeserver? Maybe you can specify many, I don't know.
BTW having multiple relays has problems. People go off and setup hundreds and then our clients get overwhelmed. I think the spec should say "only first 3 count".
