this post was submitted on 17 Jun 2023
213 points (99.1% liked)
Technology
37804 readers
243 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Its not as bad as you describe. The issue is only present when it comes to large instances interacting with other large instances. As an instance takes on more users, it is going to have a harder time serving everyone all at once. So some restrictions will ha e to be imposed so it can offer service at scale. This will include defederating with other large instances for community maintenance.
The solution is that if you need your own set of rules than it is up to you to host your own instance. I think that is fair.
Overall, instances should in general try to federate, because that is what makes this go round. And you Alcan understand the salt users would have since they are effectively banned from a large community over something that they didn't really do. But those are the breaks, and the whole point is that if you don't like it you should host your self and maintain a good relationship with the instances that you want to participate in.