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
It’s worth pointing out that the wiki article lists several examples of Microsoft using this approach but I wouldn’t class many of them as successful.
Not only was it not very successful, it’s an old outdated Microsoft playbook from the 90s/early 00s and was targeted at closed source competitors and freeware, not open source software where you can just fork out a separate version.
By all means block Meta instances if you want, but they have 3 billion users, they definitely don’t give a shit about a “competitor” with a few hundred thousand users. If simply the presence of a corporation in the Fediverse is enough to destroy it, then it wasn’t going to last long anyways. It’s embarassing that “embrace, extend, extinguish” caught on around here just because it’s a catchy alliteration.
Let me offer a rebuttal. The fact that this playbook even exists and is well-known is a cause for concern. Yes, Microsoft’s campaign wasn’t very successful, but that doesn’t mean Meta won’t try or learn from Microsoft’s mistakes. I ask: is the probability of this happening non-zero, and if so, is it lower than you’re comfortable with? For me, and many others here, that answer is no.
Moreover, this is a greater problem: Meta is well-known and has practically infinite marketing budget. They can spin their app as the de facto, causing many people to lose control of their data. By association, some people will blame the Fediverse and not Meta. Defederating signals that we are not willing to participate with them and tells potential Fediverse users that they will not be able to engage with us—and whatever they decide, we cannot impact more.
The crux of my argument is risk management. Defederated is a conservative measure to prevent possible issues in the future.
By all means block Meta instances if you want, but they have 3 billion users, they definitely don’t give a shit about a “competitor” with a few hundred thousand users.
If they don’t give a shit then why do they add federation feature at all? It doesn’t make sense.
Exactly. Which is why I believe that all this fearmongering is because of Meta’s reputation (rightfully so) rather than because Meta actually has a plan to destroy the fediverse. And it’s not the like the fediverse can be actually destroyed, people can always start new instances at any time.
Not only was it not very successful, it’s an old outdated Microsoft playbook from the 90s/early 00s and was targeted at closed source competitors and freeware, not open source software where you can just fork out a separate version.
In Microsoft’s case I agree. However Google successfully used EEE to essentially kill of XMPP where they initially added XMPP support to Google Talk, then extended it with their own features which weren’t up to spec, and then later killed off XMPP support.
If they don’t give a shit about the fediverse why do they want to join it? Only Facebook can win from this.
Google successfully did this to XMPP.
https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html
Thank you for this article. It shows exactly what’s Facebook’s plan. They will join in, make their own implementation that doesn’t work well, pass the blame to the other platforms that use the protocol*, which in turn pressures them to debug and slow down themselves around Facebook’s stuff, and then they cut them off entirely.
The correct attitude is to extinguish Facebook now. They’re not welcome.
*And yes, this would work. Users are absolutely gullible about this shit, even without ever being told anything directly. Look at Apple users and their blue/green speech bubble thing. Every single flaw with the system is Apple’s fault - but the dumbass cultminded users see the green speechbubble and blame the other users for the flaws, not Apple. They literally just did the stupid tribalism comic and it worked.
XMPP still exists. Google dropped support for it, that’s definitely not killing it. Google drops support for projects all the time by the way, it’s kind of their thing.
That’s partly because of actions taken by various governments. Who knows what tech would look like today if Microsoft from the 90s forced us all into Internet Explorer.
Also, more successful examples would be Google. They have done this very thing several times but then keep messing it up lol
It looks like articles today are saying that Meta is delaying integrating ActivityPub at launch.
That said, I’m not seeing how we get to the last E, extinguish. By its very nature, ActivityPub is decentralized to avoid total control. So even if Meta embraces the technology and wants to monetize it (because capitalism, of course), extending ActivityPub would (hypothetically) be open source - or they would fork it, diverging and making their version closed, and otherwise not function in full with other ActivityPub instances (like with kbin, Lemmy, and Mastodon). Without buying the platform from the developers in full, I don’t see how ActivityPub or the greater Fediverse dies. And I could just be missing something obvious, so if you can explain how we get there, I would really like to hear and understand.
I guess the only way I could see it is if Threads got so popular that people literally stopped using the other apps - but I also don’t see that happening, because anyone already using stuff like Mastodon are using it because Twitter, Facebook, etc, suck ass and they’ve moved away from sites like that.
EDIT: Thanks to the one person that actually replied, I saw I was on the right track at the end, but failed to see the obvious (as I assumed).
It’s hard to predict but the extinguish part would come from bigger non-Threads instances implementing compatibility with Thread-only extensions (in the interest of their users, or for money) and fragmenting the community. Threads then becomes the defacto ActivityPub standard. Maybe some instances stay true to the standard but with extremely reduced communities because now they can’t see what other instances are publishing. So now you have to decide between your ideals and your social network. At best, you’re back to square 0.
It happens in the extend part.
Large corporation will have much more resources, they will implement features and refactoring, which small open source teams do not have capability to implement. They will start pulling users because they support features that other do not.
This also means that they will start getting control.
And then finally they just cut the communication, and split the community. All the way they can claim to be working “for the community”
i.e.: The IE approach. Take an open standard (HTML), then fill in the gaps it’s missing with proprietary components (ActiveX), wait until your solutions become entrenched, then start doing evil stuff (implementing HTML slightly wrong so that developers have to do extra work to support compliant browsers).
I doubt that is the plan. The Fediverse is tiny, even after the recent growth. Prior to June it was basically just Mastodon, and I doubt Meta is agile enough to start this from scratch in response to the June growth. This is a lot of effort to take down a competitor that’s widely considered to be rough around the edges, and is only just now hitting 2m active monthly users.
Realistically Threads has been in the works for a while as a way to eat Twitter’s market share while Twitter destroys itself. I suspect they see value in the ActivityPub protocol in the same way Yahoo saw value in email in the 90s. Regardless of whether EEE is their intention or not, Meta’s presence in the Fediverse is going to have major implications for its long term stability.
EDIT: on further reflection, I suspect the value they see is pressuring other would-be competitors to also implement ActivityPub. I suspect they do genuinely want to grow the Fediverse… because doing so would increase the amount of data they could collect and sell from it.
On embrace phase the intention is not malicious, they probably want things to grow. Corporations just in long run will eventually lead to someone asking “how can we capitalize this” and this lead the FOSS part of things to be cut out, and destroying the protocol at that point.
Fediverse should defederate every corporation and just grow naturally.
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
Same reason I am highly critical of Jack Dorsey’s BlueSky and its attempt at rolling out a separate protocol. The last thing we need is for the Fediverse to be fragmented into a dozen protocols that do things ever-so-slightly differently and prevent network convergence.
Another reason to avoid it is that Jack Dorsey supports known anti-vaxxer and general conspiracy kook Robert F Kennedy Jr. Not the kind of people I’d want to run my social network.
That’s bonkers, I don’t even see what there is about the man to support. He’s just an amalgam of nonsense conspiracies.
It is very easy to argue that network convergence is NOT a good thing. That’s the whole point of the “embrace, extended, destroy” point you responded to.
The point being is that inventing a new protocol is either a case of Not-Invented-Here syndrome or an attempt to fragment the ecosystem - hence jumping straight into the extinguish phase. It does not paint BlueSky as a good actor in this race - especially as there are no substantial improvements over ActivityPub as far as I can tell.
i steal your formatted post, to post it again. I want visibility for this.
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.
The idea is that at first threads.net will seem “normal”, like all the other fediverses
Then they start adding features that either break against other servers, or straight up aren’t supported, making threads.net seem more enticing just because all the neat features aren’t on the other sites.
Think how Internet Explorer killed Netscape with all the Page Load errors caused by ActiveX, yet everyone wanted ActiveX sites.
Once they’ve walked through the path of least resistance and grabbed the bulk of the traffic, they just defederate from everyone.
Couldn’t any instance or app do this already? Like #peertube does videos in a way that isn’t necessarily fully federated with #mastodon. We get partial functionality everywhere and some places will have some extra things. If it is popular enough, then add it to the standard and let everyone who wants it add the functionality.
People are concerned about Facebook/Meta trying to Embrace, Extend, Extinguish ActivityPub - if I’ve understood correctly.
People keep saying EEE as if that’s a point in and of itself without really explaining how in this instance
If they become so ubiquitous that all you see are Threads messages, all they have to do is start adding their own extensions to ActivityPub and degrade the experience of everyone who is not using their app.
Embrace, they join the fediverse seemingly in good faith. Bringing their larger userbase to massively increase the size of the fediverse.
Extend, they add some features that are convenient when interacting with their base across the fediverse. But these conveniences require proprietary software integration.
Extinguish, once enough users and platforms are tied into the conveniences of extend, they use that to force compliance. Stricter and stricter rules on their proprietary software. Comply or die.
The fediverse won’t be gone afterwards, but if it EEE works then we will end up very stifled.
Here is an example of a corpo dealing a blow to an open source project. The article covers an example of Microsoft and Google killing a competing open source project(s).
You’re acting like there’s only two situations: The entire Fediverse defederates with them, or the entire Fediverse federates with them. That’s not the case.
I, personally, do not want to interact with anyone using Threads, because Meta has a proven history of poor moderation and of manipulating the narrative for political gain on Facebook and I see no reason to think they won’t do the same here. I am not the only one who holds this opinion. Those of us who feel this way can use instances that defederate with them, and have our way.
If you want to interact with them, you can maintain an account on an instance that does federate with them. You do not need to have a Threads account, nor does anyone else.
meta is not here to promote open networks. They will do more harm than good. If you want to learn more about how google achieved it with the XMPP you can read the story here https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html written by one of the core developers.
This is an interesting article, but I don’t think it’s fair to blame Google for the death of XMPP. Google were the largest consumers of XMPP at one point, sure, but Google was in no way (and never has been) the market leader in communications applications. Google talk came and went, Hangouts came and went and so on. The argument of “When google pulled the plug, XMPP users had to use something else to keep in touch with friends” is equally true of Google messenger users as well. I don’t know anyone that ever exclusively used a Google messenger app, now or then.
Google isn’t entirely innocent here, they definitely didn’t treat the protocol with the respect it deserved, but the development of XMPP was/is fraught with its own problems. I remember setting up an XMPP network for use in a small office as an internal chat tool, it was a nightmare of an experience. Different XMPP Clients had different levels of compatibility with different XMPP servers, many of the clients were just poor overall and the user-experience left a lot to be desired. All we wanted was a simple instant messenger for work, in the days before Slack and Teams. We ended up using OpenFire because it was developed in tandem with Spark, it was basic but worked well for our needs but any time I tried to adopt a different messenger, half the features didn’t work.
I don’t want to interact with anyone on Threads. It is new and it is Facebook.
Was about to say just that. I’ll love to reject people that only follows big corpos.
Meta joining the fediverse is like Raytheon joining anti-war protests. They are not there for sincere participation.
No worries once threads becomes big enough they will defederate from fediverse /s That sure will be hostile to fediverse users.
When Thread finally enable federation, just unleash the Lemmy meme community there. We’ll see how fast they roll back the federation feature on their own after their feeds are getting flooded with beans.
They have also already declared that if you federate with them, your instance has to abide by their code of conduct, so they already throwing their weight around.
Lots of naivety here. Big corps only act in their own interest. They view the world in terms of opportunities and threats. Eating Twitter’s lunch is an opportunity. The Fediverse is too small to be worth much today, but someday it might grow up and challenge the status quo. That makes it a threat.
Threads is new - unless you meet someone who for some reason only has a threads account, just talk to them elsewhere.
Otherwise, why is it the Fediverse user who has to get the threads account? Tell your people to make an account elsewhere. If you are conscientiously avoiding threads, you’re probably the only one in the relationship with a principle boundary to cross in this situation.
I’m all for federating with them. But give the user the ability to defederate their posts/comments based off their settings. I would rather my information not be supplied to any company owned by Facebook, that’s just me.
The information they could get is already public. That’s how Activity Pub works.
That’s completely fine, but just because a knob can be lockpick doesn’t mean you leave it unlocked.
Granted I have very little experience with activity pub, but I would expect that it should be very possible to have something similar to how defederating Works where if you don’t allow it to be sent to a specific Community it just won’t communicate.
edit: Looking back at it though, it wouldn’t stop them from just opening a secondary instance nobody knows about, having it set to private and then just running it as an info collector I don’t think.
I agree with you.
Instances can defederate from meta at any point they choose, should it become necessary in the future. Until then, it is a huge boon to the more decentralized parts of the fediverse to get content from where all the “normies” are, as well as giving more visibility to non-meta instances and giving said normies a road to the less data-hungry parts of the network.
Reading material: https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html
honestly, i think only half-accepting them would be beneficial. it gives meta users a taste of the fediverse but locks them out of a whole bunch of cool stuff that they could have, if they just make an account on one of the instances that they already know because it’s in the half that does federate. we just need to ensure we never repeat xmpp’s mistake: meta users should never be a majority.
i’ll have to discuss this with our admin team, but my initial plan is to defederate meta if usage by them hits 25%. if a critical mass of the fediverse does that, in the worst case we’ll split off from them before taking damage, and in the best case we’ll actively siphon away their user base. (and if any other tech giant enters the fray, we’ll just have to include them in the 25% quota as well.)
update: we discussed the topic and went for an immediate defederation
it is a huge boon to the more decentralized parts of the fediverse to get content from where all the “normies” are
This is something I can’t understand. There’s obviously no profit motive to push fediverse to everyone, and most content is dogshit.
Can you explain why you find either to be preferable?
Plus, the more entwined threads is with the rest of the fediverse, the harder it’ll be for them to break off. Users will be following Mastodon accounts and posting in Lemmy communities and if Meta does something to break that, they’re the ones that’ll get the backlash, not the fediverse. We’ll just continue along as normal.
While I think I agree we shouldn 't just defederate them. This is for a user to block them. And if you tell users how they can block them, it will maybe take a bit of pressure away from admins to do it.
During the first wave of Twitter refugees , there was a lot of explaining about ignoring and blocking users. Which can never hurt IMHO. Certainly because it can decrease the load on the volunteers that run an instance
I’m with you. What’s the hate with Threads? It’s going to basically just be like another Mastodon instance anyway, right? Just keep using whichever instance you want and Threads will end up adding more content to the fediverse. I don’t really see the downside.
In case you’re wondering why all the down votes, it’s because of this concept:
https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html
Edit: Heres a summary I had in another post.
Summary:
-
The Fediverse is a decentralized network of servers communicating through the ActivityPub protocol.
-
Large corporations like Google and Microsoft have a history of either trying to control or make decentralized networks irrelevant.
-
Google joined the XMPP federation initially but implemented their own closed version, causing compatibility issues and slowing down the development of XMPP.
-
Eventually, Google stopped federating with other XMPP servers, leading to a decline in XMPP’s popularity and growth.
-
Microsoft used similar tactics to hinder competing projects, such as the Samba network file system and open source office suites like OpenOffice and LibreOffice.
-
The strategy involves extending protocols or developing new ones to deny entry to open source projects.
-
Proprietary formats and complicated specifications are used to maintain dominance in markets.
-
Meta’s potential entry into the Fediverse raises concerns as it could lead to fragmentation and a loss of freedom.
-
The Fediverse should focus on its values of freedom, ethics, and non-commercialism to avoid being co-opted by large corporations.
How a new federated decentralized platform can avoid this fate:
-
Stay true to the principles: The platform should prioritize and uphold the values of freedom, openness, and decentralization.
-
Develop open and robust protocols: Use open standards and ensure the protocol’s specifications are transparent, well-documented, and not controlled by a single entity.
-
Foster a strong community: Encourage collaboration, participation, and diversity within the community to avoid reliance on any single company or organization.
-
Emphasize user control: Give users control over their data and privacy, allowing them to choose which servers and communities to join and ensuring their content is not subject to corporate surveillance.
-
Focus on user experience: Create a user-friendly interface and provide features that attract and retain users, making it easy for them to engage and connect with others.
-
Avoid centralization of power: Design the platform in a way that distributes authority and influence across the network, preventing any single entity from gaining too much control.
-
Promote interoperability: Support compatibility with other decentralized platforms and protocols to encourage communication and collaboration across different networks.
-
Educate and raise awareness: Educate users about the benefits of decentralized platforms, the risks of centralized control, and the importance of supporting independent, community-driven initiatives.
By following these principles, a new federated decentralized platform can strive to maintain its integrity, preserve user freedom, and resist the influence of large corporations seeking to control or make it irrelevant.
My reading of that isn’t that Google killed XMPP, it’s that they thought XMPP would be useful for the userbase they brought in, they realised it wasn’t, and they ditched it. There’s no indication that XMPP had the userbase and lost it to Google, or even that XMPP had features that were stolen by Google
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.
@Nougat It doesn’t prevent them now, as they can just easily crawl all of your posts on here because you are posting on a *public instance*. Defederating from them does nothing to make your public content private.
@ninboy No, it doesn’t make my public content private, but it would display my content alongside everything else that a threads user would see, which would make Meta’s product more attractive to threads users. Increased threads userbase means increased ad revenue. Speaking of which, I’m now thinking about how content I created, not on a Meta-operated site, would be (as federation by default intends) displayed next to Meta advertising on their instance. My ability to prevent me-sourced content from reaching Meta’s instance prevents me-sourced content from displaying next to advertisement I don’t want it to be displayed next to.
@Nougat that makes sense, thanks for elaborating on your points. I guess as soon as we put any content out there we can’t prevent screenshots going viral on any context.
Neat, but it still means nothing. You’re still posting in a public forum. You can copyright or watermark your work, but fair use is a two way street.
I printed it out and put it on the front door of my house. The castle doctrine means that this is enforced against all internet companies I use in my house.
How is this legally binding? I still remember when people posted similar stuff all over Facebook. It means nothing.
This is exactly my concern, I don’t want my online activity to become another revenue stream for meta. If they can put ads next to our posts then we’re back to working for free for the billionaires.
If I understand correctly, the concern is not for the users on Meta’s “Threads”. It’s the fact that the content you create on Mastodon or whatever fediverse part with which Meta federated would eventually reach users on Threads, and thus “you” (on the fediverse corner outside of Meta) are indirectly monetized.
Meta should stay away from fediverse!
Yeah, not a fan of the ominous shadow threads™️ casts. I don’t trust them not to flood the fediverse with assorted toxic garbage to push people back towards their walled garden platforms.
The fediverse offers something radical - a new shot at genuine self determination and a socialised, self-governing internet. That shit spells B-A-D N-E-W-S for incumbent platforms (imo) and they’re bad actors in general; they wouldn’t think twice about smothering anything that threatens their short/long term profits. Who’se going to stop them?
Might be a little bit overly risk concious but goddamn. If I were them, I’d be trying to kill alternative ecosystems before they grew - especially if mine (metas) is both trash to use, and be used by.
Even worse, the Threads app is a privacy nightmare
I bet meta really wants to keep track of people in fediverse
What does “Other Data” even cover? Could be literally anything Meta wants
ActivityPub is no more radical than NNTP. Lemmy is almost an exact reimplementation of newsgroups