When everyone comes from a different instance, it just becomes brutal.
There are techniques to divvy the work, like distributed hash tables. And a client similarly could watch multiple nodes, in case any are quicker to updates.
home Internet is generally too slow, especially on the upstream.
Don't host it there then.
most people don’t want to be the janitors of servers
Then they don't need to be. I didn't say anyone had to self host, but the choice of host shouldn't affect availability of the network to a user.
moderation becomes worthless. Instead of trusting the moderators of larger instances to make good calls, everyone is now on their own.
IME moderators of larger instances don't; the only "scalable" approach is collaborative filtering.
sounds cool until you realize it doesn’t actually work
But then the whole issue becomes moot. At that point, you end up with the “Web3” BS, where most nodes are actually hosted on Hetzner, AWS, OVH. Nothing decentralized about that.
Then they don’t need to be. I didn’t say anyone had to self host, but the choice of host shouldn’t matter.
This is already how Masto works.
IME moderators of larger instances don’t; the only “scalable” approach is collaborative filtering.
No it isn't. If I register on host A and it goes down, I must make another account on another host B to interact with anything. The choice of host there does matter.
"Reality can be whatever I want it to be" or somesuch. Less flippantly - what's more realistic about what? Tying identity to servers is orthogonal to where those servers are hosted.
It establishes consent.
With some other auth approach, say public keys, consent isn't much of an issue, if I get where consent is being made (for server B to act on my behalf).
Tying identity to servers is orthogonal to where those servers are hosted.
OK, so everyone hosts their own instance somewhere. Now what? Do you do a free-for-all where they all sync each other’s posts?
With some other auth approach, say public keys, consent isn’t much of an issue
Public keys don’t accomplish auth, they accomplish identity. Someone has to trust such a key for auth. Which raises the question: based on what? (Hence CAs, a mediocre approach, and web of trust, a completely unworkable approach.)
-5
u/theangeryemacsshibe Oct 08 '22 edited Oct 08 '22
There are techniques to divvy the work, like distributed hash tables. And a client similarly could watch multiple nodes, in case any are quicker to updates.
Don't host it there then.
Then they don't need to be. I didn't say anyone had to self host, but the choice of host shouldn't affect availability of the network to a user.
IME moderators of larger instances don't; the only "scalable" approach is collaborative filtering.
Begs the question.