IMHO regarding coverage: clients don't need to find a minimum set with maximum coverage. Clients can just connect to 500 relays to follow 500 people. It still works. But of course it is more efficient to do otherwise, and especially if some relays are down, to find the set that is up and covers everyone.
I think (as you describe in (8) that real world considerations probably far outweigh theoretical algorithm choices. But that doesn't mean we shouldn't bother to get the algorithms right.
Yeah, I got cobwebs in my brain still about nostr.
Clearly relays need to filter nasty things.
But if the option Leo suggests (asking the relay to filter by WoT) were filtered at the relay (rejecting events outside of the WoT when they arrive, instead of when they are downloaded) then that relay could only really serve as a personal inbox relay for the one person.
Sorry I keep thinking about write relays not inbox relays. Just ignore my wanderings here. I need another coffee.
Like I say, I'm not sure what the performance impact is without trying it. It saves some, it costs some. Should be explored. In any case if I follow 500 people, which relays am I asking this of? My presumption is that I still find those 500 people's write relays and go ask them, which means I wouldn't be "subscribed" to many of these relays, or I'd have to sign up to a lot of relays, or else relays also have to shuttle from other relays.
In general I agree with both of you. Filtering can be done either side. Personally I prefer client-side filtering and dumb relays because it puts me in control. I don't get to choose the relay that has the right censorship policies. The people I follow choose the relays, not me. But that only affects their posts and it makes some sense too.
Asking relays to compute WoT so you don't have to upload long lists of pubkeys has performance consequences and I'm not sure if it is better or worse.
I have to admit to feeling jealousy. I wish my government was shut down.
Node Package Manager. Where most people get their javascript libraries.
FYI there is a massive cyberattack on NPM right now, package developers being attacked, nasty commits being added and published, tokens being stolen and used to corrupt more packages. The ecosystem is currently widely corrupted. We just got an advisory from the NZ government about it.
My mind has been wiped clean of the memory of everybody who did not make it. Who? Jacinda? Lemme ask around....
.... nobody by that name is up here.
I'll ask next time. If there is a next time. There shouldn't be a next time.
Where do you have your bird's eye chillies?
Um... we don't carry bird's eye chillies.
Ok, how about kaffir lime leaves?
Sorry, we don't carry those either.
Ok fine. Just point me to your coconuts.
We don't carry coconuts either.
What?! What kind of store is this?
This is a stationary store. We carry office products.

I agree this data is suspicious. How do they get at the root cause? I dunno. My uncle died last year from not eating enough bananas? 🤨
It is not just human breeding that makes fruits sweeter and less fibrous. The plant itself is under pressure to do that, to spread it's seed more effectively.
It is hard to find any fruit that hasn't been cultivated at least a little bit by humans over the last million years, even mangos and mangosteens. But some fruit has changed more than others.
Apples were created by Rome from crab apples, which are barely edible, it is not an ancient naturally-evolved fruit.
But fruits on plants where the apes live are more palatable than crab apples. Mostly figs, mangosteens, lychees, and they are not highly cultivated and bred.
I think it is a miscomprehension that fruit 10k years ago was far less sweet and far more fibrous... rather, I think our modern dietary excesses make sugar into a villian and we project that status onto all our knowledge. Yes, sugar is a villain if you are overeating, but it is nothing of the sort if you are not.
Therefore I think angiosperms made sweet palatable fruits for mammals to spread their seeds with. Also bees make ridiculously sweet honey, and we didn't breed them to do that. And hunter gatherer tribes eat large amounts of honey. Another data point against the "sugar is modern and evil" idea.
I should also say that open timestamps are well solved by blockchain. So that's 3 things: money, timestamps, and universally unique usernames.

At least in nostr with the outbox model, there is no routing, and nodes don't control which other nodes they communicate with. I imagined the thing just like browsers connecting to websites. But a completely different architecture could be routed, where a node connects to certain known and trusted neighbors only, and data is routed node-to-node. Such protocols are slower and less reliable, having so many middle-men, but of course if you use Tor under nostr you are pretty much doing that same thing.
I lean towards clients connecting to untrusted nodes. And clients being considered very difficult to develop because they must be security hardened. In the same way that browsers must be. In a similar way that computer hardware has to be bug-free before they tape out. Making nostr "simple" proliferates insecure half-assed software. I lean towards complexity as a way of weeding out developers who can't be trusted to make hardened software.
But this is just a current leaning. I'm interested in exploring architectures where clients don't have to talk to nodes they don't trust... I just don't see the big picture right now of how this could work without so many downsides.

If you have a reference I'd appreciate it. I believe Paxos is the first solution invented way back in 1989 but published in 1998. And Raft is technically equivalent to Paxos. I'm sure he's proud that such a solution is now widespread in bitcoin, but bitcoin blockchain isn't the first and only solution.
But these are solutions to the problem of consensus among bad actors. Do we need consensus in social media applications? The only reasonable place we might want consensus is usernames, not that we need them, but that users seem to want to declare and own a globally unique one and you would need a consensus system to give users what they want. But I'm not sure the juice is worth the squeeze, and petnames avoid all the trouble.
If you are going to bother building a network of peers, a consensus algorithm, and an ever growing blockchain, you'd better be solving a problem that is worth all that trouble. Bitcoin clearly was. Usernames in a social media protocol don't seem to be worthy of such a heavyweight solution. I shouldn't have said "ugly", I should have said "heavyweight."
Solutions to the Byzantine generals problem such as Paxos or Raft are more general than blockchain. And other solutions to distributed computing problems exist like conflict-free replicated data types. My problem with blockchain is that it is an infinitely-growing public ledger, and that while bitcoin needed it, not much else needs precisely that. Many things may benefit from something *like* blockchain, but not actually blockchain. And for a decade people have been running around with a beautiful hammer (blockchain) looking for nails to hit, and not finding any interesting nails (problems) so they started creating nails so that they would have a use for their beautiful hammer.
Take git for example. It is both distributed and it has a blockchain. But it's not a bitcoin-like blockchain requiring some network of nodes and Raft to operate. Most problems can be solved more like git and less like bitcoin. Bitcoin is the only real problem I can think of that actually needs what bitcoin did.
In what respect? I'm a fan of his work.
Peer-to-peer means not having a 3rd node sitting in the middle of the communication in some data center. E.g. rather than client->server->client it is just peer->peer.
But I've run across people who think a client-server protocol necessarily isn't peer to peer. I'm just trying to argue that the p2p protocols are still client-server protocols. Nostr could be written as a p2p application without changing any of the NIPs, just by making every client also a relay.
Your point is the part I didn't discuss because it wasn't in my head at the time --- the middleman. You want direct communication over anything with no middleman. Fair enough. And I think that should be achievable, even if the communicating pieces are a client and a server.
I agree. Half of the nipple should be covered, the other half slipping out "accidentally"
You have censored her nipples.
you forgot sex

p2p.
People want it mainly because they don't want to rely on data centers. But let's walk through an example.
Perhaps you have a node in your home network, and I have a node in my home network. For these to communicate, one of them has to contact the other one first. So let's say my node contacts your node. Ok. Then my node is acting like a client, and your node is acting like a server. So in fact p2p IS actually client-server. It is just a special case of client-server, where the clients and servers are forced to be glued togther into a node.
Therefore IMHO, client-server architectures cover all p2p architectures and more. And gluing the client and server together is a completely unnecessary requirement.
In fact, I want clients on transient machines, laptops that I turn off. But I don't want servers offline, I want them on hardware that stays on. So the p2p node idea falls apart. Clients and servers should be separate.
But of course this isn't all that people are talking about when they talk about p2p. They are talking about hole-punching.
So all I'm trying to argue here is that client-server is not some worse alternative to the superior peer-to-peer, but rather that client-server is the superior architecture.
And it makes more sense to me to suggest that there should be ways to make servers acccessible to the Internet even if they run on home networks, perhaps with hole-punching rendezvous services. Running a server at home is an excellent idea. But nothing else about p2p seems like a good idea to me.
I've already said more than I know myself. You go figure that one out.
What people want is, I believe, the following things:
Privacy: data protection, metadata protection, and IP privacy.
Censorship Resistance: decentralization purports to assist in this goal, but I don't think "decentralization" is the goal.. the goal is censorship resistance.
Control and Independence: people don't want to be locked-in to one provider that could in the future disappoint them.
The following hot ideas are not so hot in my book:
federation - if you are still locked in, this just changes the scale of centralized lock-in.
blockchain - an ugly solution to a problem that nobody has.
p2p - an artificial binding of clients to servers (I will explain in a sister thread).
Lots of people are looking to build on a decentralized censorship-resistant platform that offers privacy, that is mesh, that is p2p, or uses blockchain, or is federated, or <pick your buzzword>.
Nostr clearly is in this space. But this thread is more general.
Signal is in this space and Moxie Marlinspike argued (5 years ago) in favor of centralization here:
https://www.youtube.com/watch?v=DdM-XTRyC9cI'm not going to argue against all his points, many of them are clearly constructed and wrong and not worth my time. But that video is what inspired this post.
I want to talk about high level ideas in this space, and clear up what I believe are common misconceptions. Since I'm going to write about lots of separate things I'll make sub-posts for each point.
I just want to see replies from strangers, without letting them use the relay to send material that would get me in trouble. Maybe I never 'release' their notes. How bad would it be? All of their followers will still see their reply (posted to their outbox as well as my inbox). Only my followers would not see it. Unless of course I wanted to reply to it, in which case I would release it and reply.
You are right it is a problem. I've always felt bad about this aspect, that I was breaking other people's experience. But I can't think of another way to be sure that I'm not going to get in trouble.
We need more thinking on this area.

There are multiple ways you connect with people on nostr. By far the most common is that you find an event from a key you haven't seen before. And so that case must have a good solution. The case where you know the person and scan their business card or go to their personal URI is the easy case.
I don't like the NIP-65 solution of "spray it everywhere". It requires people to just-so-happen to look for relay lists in the same places, which drives it to be a centralized thing. I really do like the DHT solution.
But the bittorrent/mainline/Kademlia DHT handles only ed25519-signed data blobs.
I'm starting to think standing up a new DHT using all the security learnings we have at this time from published academic papers (most of them from early 10s when everybody was into it) might be where we are headed. And I would strongly suggest that such a mechanism not be tied to just one cryptosystem, but to support multiple including PQ signature schemes. It is not just the nostr social graph I want to save, it is the flexibility of signature scheme. Sure you can wave your hands and claim quantum computing will never work. I did that about AI and I was wrong.
What I decided to do with chorus is that the inbox events are visible only to the people that the relay serves, which in my case is only 3 people, and the event's author.... until I actively approve them for public view. This prevents illegal content from being disseminated from my relay (even if it might arrive and get stored). The downside is that some people watching the conversation don't see the conversation in real time (if they however follow the stranger, they will see it from the stranger's relay). Sometimes I may go many days without moderating events on the relay, I've been pretty lax about it.