Embrace, extend, extinguish. Only proven way to destroy decentralized, free, open source solutions.

First stage embrace might not even be malicious, but with corporations it will eventually lead to someone thinking: how can we monetize our position. It is just nature how business works.

https://en.m.wikipedia.org/wiki/Embrace,_extend,_and_extinguish

Please: All read this piece about how "Embrace, extend and destroy" can destroy a federated network. It happened before and they certainly will try to do it with the fediverse.

Big corpos don't want to take it over, they want it gone.

https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html

Unpopular opinion but defederating Meta is a terrible idea. What are people thinking will happen? Allow them to federate and you'll have mastodon users able to view and interact with posts from Threads without needing to be concerned about ads or tracking, without giving over any more control of privacy than they would to any other fediverse instance, and without needing to possess accounts homed within the Meta infrastructure.

Defederate them, and anyone who wants to interact with anyone on threads will most likely need to maintain a presence on both and handover more personal data to Meta than they otherwise would.

Defederating is actively hostile to fediverse users.

If Meta is running a fediverse instance, they're doing it for money. Sure, I might be able to block Meta-sourced content from reaching me, but that doesn't prevent me-sourced content from reaching Meta - where they can monetize it.

Show me how to do that, and I'm on it like white on rice.

Meta should stay away from fediverse!

Please: All read this piece about how "Embrace, extend and destroy" can destroy a federated network. It happened before and they certainly will try to do it with the fediverse.

Big corpos don't want to take it over, they want it gone.

https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html

Lemmy should defederate from threads.net

Meta jumping on the Fediverse bandwagon would kill it one day. It's an EEE strategy. We need to keep them out. Defederate from them.

I tried to sign up for this junk and it immediately suspended my account at the end of the sign up process for some reason. Now it's demanding my mobile number to appeal it.

Get fucked Zuckerberg you tosser.

I really hope the fediverse can block out the meta crap…

@downpunxx

This is Microsoft's playbook, https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish, it was use by Google to kill off XMPP - https://www.disruptivetelephony.com/2013/05/did-google-really-kill-off-all-xmppjabber-support-in-google-hangouts-it-still-seems-to-partially-work.html, now it will be used by Facebook to try to kill the Fediverse.

Why is this not more widely talked about? Please share this.

i'll join the voices saying this is bad for the fediverse, and bad for users in general. there are LOTS of normie users who are joining threads who will be shut off from learning about all the cool other servers if everyone blocks them. this will mean users who want to interact with them need to sign up on Threads, which is what we don't want.

what we want is that users on Threads see other servers, learn that they're better, and migrate over.

don't block Threads, show them how much better we are.

Has lemmy.world blocked meta?

Spontaneous idea of how to use copyright law for keeping Meta out of the Fediverse (more for fun):

Introduction: Parts of the Fediverse, including Mastodon, are software licensed under the APGL license. This license is a great choice because it forces the ones running the software to grant users access to the source code. GPL for example would allow to run proprietary services based on GPL code. The AGPL does not. Companies like Meta and Google will likely not use AGPL code because it might force them to also publish their proprietary systems behind the scenes. However, this does not help much for keeping the Fediverse save. They simply implement their own software which will not be open source.

Therefore we may need another approach. Defederating is the simplest and in my opinion currently the best. It's easy and keeps people in control.

However, there could be some 'automatic' approach using copyright law. It's a hack which allows to use existing law to regulate the way instances can federate.:

• instances would Federate only if the other side can provide a certain piece of information called X
• X is protected by copyright law, therefore by default, instances are not allowed to provide X
• However, X is released under a license which for permits to copy and distribute X under certain conditions
• The conditions allow to tune who can legally federate
• Conditions could be
  • The server software must be AGPL licensed
  • The instance must not be owned by a company with a certain amount of annual revenue

Open question is, who owns the copyright of X?

Do you really need to import a CSV just to block a single domaine? Sounds over complicated