Among 20+ microblogging clients there are only 2 that don't follow the promote centralized paradigms, soon to be 1, eventually 0.
So I don't get why you are spreading so much bullshit, it would be mu...
The problem I see is that messages aren't "evenly spread across the network" but are concentrated on a few relays, and it even happens that some replies only reach certain relays. The result is centralisation on the most popular relays.
The solution I see is the classic DHT, basically algorithmically spreading content across every node in the network, which will have storage and bandwidth quotas in its parameters. This leaves the administrator free to reject certain content or keep some in full, but fundamentally every message is split in chunks and some chunks are automatically spread across nodes. Historical examples include Usenet on one hand, as a decentralised paradigm, and eMule/KAD or ZeroNet for the distributed one.
The solution I see for further improvement is to not have "Nostr client only", but client+relay in a single package, with potential support for Tor or ZeroNet or something similar for those behind a NAT. Those with an exposed host can provide a way to punch through holes in NAT for those who don't, but basically every client is also a relay and blossom server.
I hope that's clearer now, and I don't see any bullshit or rudeness in what I'm writing. Meanwhile, as a fairly new user curious about Nostr and from the old-school *nix background, I see a tense community that's not very interested in the rest of the world, which isn't a good thing for achieving success.
The solution I see is the classic DHT, basically algorithmically spreading content across every node in the network, which will have storage and bandwidth quotas in its parameters. This leaves the administrator free to reject certain content or keep some in full, but fundamentally every message is split in chunks and some chunks are automatically spread across nodes. Historical examples include Usenet on one hand, as a decentralised paradigm, and eMule/KAD or ZeroNet for the distributed one.
The solution I see for further improvement is to not have "Nostr client only", but client+relay in a single package, with potential support for Tor or ZeroNet or something similar for those behind a NAT. Those with an exposed host can provide a way to punch through holes in NAT for those who don't, but basically every client is also a relay and blossom server.
I hope that's clearer now, and I don't see any bullshit or rudeness in what I'm writing. Meanwhile, as a fairly new user curious about Nostr and from the old-school *nix background, I see a tense community that's not very interested in the rest of the world, which isn't a good thing for achieving success.
1🤙1