195
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 23 Jun 2023
195 points (100.0% liked)
Technology
37742 readers
463 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
Yes, and if it becomes really big, then every federated instance would find itself coping with large amounts of traffic passed to and from the big instances, and it will become difficult to run a small operation cheaply. At that point, only the big players with big money will be able to run sites in the Fediverse and it could end up mirroring what has happened to the rest of the internet.
On balance I think it's best if existing Fediverse instances don't federate with the big corporations. But there are still other ways the corporations could sabotage this place, so the developers and the site admins need to be ready.
I think that' where the biggest threat lies. How is a small operator going to keep up with the demands of a corporate server cluster with millions of users. A small operator would have to defederate. That puts us back to the crux of original question, should corpos be allowed on the Fediverse. Why not save everyone the circle jerk and blacklist them from the start.
A secondary threat is corporate sabotage of the ActivityPub protocol. They already have a track record of doing that to free and open standards.