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).
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.
What kinds of extensions should the typical activitypub user be worried about? I don’t care if Meta adds payments or virtual avatars or whatever–if the core functionality of the Threads app is simple microblogging, it should be perfectly interoperable with that side of the fediverse.
The more likely effect IMO (if Meta holds to their word on enabling federation on their side) is that other large social media companies (e.g. reddit, twitter) will feel pressured to federate and that will make the fediverse better, not worse.
My account is on kbin.social but I’m working on getting kbin self hosted. When I do, I’ll absolutely be federating with Threads whether or not kbin.social does.
A cool post pops up in your feed. You click it. You are met with an overlay that says “Sorry, this post isn’t compatible with your browser. Please log in to Threads.”
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.
While Threads is federated social circles and communities will have time to form. Thread users will by nature of having the support of a corporate juggernaut, be the lions share of users on the 'verse. When threads pull the plug, the Fedverse becomes a ghost town overnight and everyone not on Threads will be forced to migrate if they want to keep their social circles and communities intact.
I think few people would migrate away in that scenario. Some might create additional accounts (none of this is zero-sum). It’s not unlikely that Mastodon itself will become bigger because of it, and it’ll get hard for Meta to unilaterally pull the plug - a bit like email.
I wouldn’t underestimate them though. After all, they own some of the biggest social network platforms on the globe and have the formula to hook people up down to a t.
You’re severely underestimating the budget Meta can throw at this. Mastodon/Lemmy/etc. right now are largely volunteer-run as opposed to full-time employees.
People keep saying EEE as if that’s a point in and of itself without really explaining how in this instance
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).
Most comprehensive article on this topic I’ve seen since this Meta shenanigan started. Thanks for the read
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.
What kinds of extensions should the typical activitypub user be worried about? I don’t care if Meta adds payments or virtual avatars or whatever–if the core functionality of the Threads app is simple microblogging, it should be perfectly interoperable with that side of the fediverse.
The more likely effect IMO (if Meta holds to their word on enabling federation on their side) is that other large social media companies (e.g. reddit, twitter) will feel pressured to federate and that will make the fediverse better, not worse.
My account is on kbin.social but I’m working on getting kbin self hosted. When I do, I’ll absolutely be federating with Threads whether or not kbin.social does.
A cool post pops up in your feed. You click it. You are met with an overlay that says “Sorry, this post isn’t compatible with your browser. Please log in to Threads.”
Over half your feed are Threads posts.
Speculative example.
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.
The outcome then would be that Meta’s instance would be defederated/defederate itself - how would that be different from now?
While Threads is federated social circles and communities will have time to form. Thread users will by nature of having the support of a corporate juggernaut, be the lions share of users on the 'verse. When threads pull the plug, the Fedverse becomes a ghost town overnight and everyone not on Threads will be forced to migrate if they want to keep their social circles and communities intact.
I think few people would migrate away in that scenario. Some might create additional accounts (none of this is zero-sum). It’s not unlikely that Mastodon itself will become bigger because of it, and it’ll get hard for Meta to unilaterally pull the plug - a bit like email.
They’d probably attract more people (even people that are here right now) before doing so. Thus creating another centralized platform.
If the Threads product was so superior, and Mastodon so unable to respond that millions would leave Mastodon - sure. I doubt it though…
I wouldn’t underestimate them though. After all, they own some of the biggest social network platforms on the globe and have the formula to hook people up down to a t.
You’re severely underestimating the budget Meta can throw at this. Mastodon/Lemmy/etc. right now are largely volunteer-run as opposed to full-time employees.
That argument suggests open source products couldn’t possibly compete with a closed-source alternative.
They can compete of they have the manpower to do so. Lemmy has literally only 2 devs. How many devs can Meta pay to work on Threads and outpace it?
Threads isn’t a Lemmy competitor - it competes with Mastodon