76
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Jul 2023
76 points (91.3% liked)
sdfpubnix
1330 readers
3 users here now
Fans of SDF
founded 2 years ago
MODERATORS
Edit: this comment changed my mind. In a nutshell, if we can't keep a large instance controlled by "the enemy" from destroying what we've got, then we just have to do better next time.
I have been making a related point that we should be concerned about any instance capturing too large a fraction of the space. I'm less concerned about the fact that it's Meta than I am about any one instance having a critical mass that gives them a controlling interest.
History has shown that those with a controlling interest eventually use that control for their own benefit.
That's why I joined a small collection of focused instances and try to subscribe to communities that are hosted in their "natural homes" instead of those on generic instances.
Would you say that also applies to the largest Lemmy instances currently like lemmy.world and lemmy.ml etc.?
Edit: this comment changed my mind. In a nutshell, if we can't keep a large instance controlled by "the enemy" from destroying what we've got, then we just have to do better next time.
Yes, I would. Even if they are administered by people that have the best interests everyone at heart, sheer size means that they must be taken into account as the tools and clients evolve over time.
It's not that the system itself should be unable to cope with large instances, it's that the only reason for the system itself to gain that capability is in response to the rise or introduction of large instances. Some of what I've seen discussed is the need to change the development roadmap to accommodate the seemingly unexpected rise and possible introduction of very large instances. In other words, those instances are already controlling the direction taken.