this post was submitted on 06 Jul 2023
4 points (100.0% liked)

Lemmy.ca's Main Community

2814 readers
2 users here now

Welcome to lemmy.ca's c/main!

Since everyone on lemmy.ca gets subscribed here, this is the place to chat about the goings on at lemmy.ca, support-type items, suggestions, etc.

Announcements can be found at https://lemmy.ca/c/meta

For support related to this instance, use https://lemmy.ca/c/lemmy_ca_support

founded 3 years ago
MODERATORS
 

I've seen that some instances have already done it preemptively.

you are viewing a single comment's thread
view the rest of the comments
[–] Omega_Jimes@lemmy.ca 1 points 1 year ago

It feels counter productive, but the reality is that the less huge corporations are involved in a federation, the safer it is.

The problem with federation with Meta is that it encourages Meta to develop and contribute to the infrastructure. Which sounds great, but the record is poor on that front.

Once a company with huge money starts working on your infrastructure, they're going to make changes, changes that maybe the community doesn't agree with, but since all the money is being funneled through one of two companies, they make the decision.

Then the company decides that they don't want to keep supporting something that doesn't make them any money. Since Meta would theoretically bring millions of users from their platforms, they could decide to suddenly cut out all non-Meta instances. Now we're the odd ones out, your friends are wondering why they can't reach you anymore, you're suddenly offline.

Embrace, extend, extinguish. It happened with XAMPP, it happened with Java, CSS, most browsers are Chrome based, 'exchange' email servers, etc.

The best thing to maintain software freedom is to never open the door to huge companies.