131
Embrace, Extend, and Exploit: Meta's plan for ActivityPub, Mastodon and the fediverse
(privacy.thenexus.today)
this post was submitted on 20 Dec 2023
131 points (83.2% liked)
Fediverse
28396 readers
257 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
They might not be inherently bad, but they'll be likely bad depending on how it's done, and Facebook isn't to be trusted.
Just for the sake of example:
Note that Facebook has a long story of user-hostile decisions; as in, this crap wouldn't be below its moral standards. So, while most of the time this would be FUD, in this case it's just F, no uncertainty or doubt.
Exactly. And they've already done your second and third bullets!
What specific features do you have in mind that could be implemented in a closed-source manner that couldn't be reverse-engineered and implemented by open-source instance software too? It's not easy to come up with such a thing, and it's unclear what benefit it would serve Meta that they can't accomplish by just not joining the Fediverse in the first place.
If Threads implements asymmetric federation, I'll shrug and ignore them because I'll never see their content and it won't ever affect me.
Doesn't Threads already have a bullshit terms of service? That's my default assumption for any website, really. But even if they don't, ActivityPub is an open protocol and so of course my data is being collected by who-knows-how-many organizations already. Meta doesn't need to do anything new at all to get access to it.
Sorry for the wall of text.
The features don't need to be impossible to reverse engineer; they could be costly enough to do so, rely on other FB/Meta platforms, or demand server capabilities past what you'd expect from typical Mastodon instances. For example:
Killing a bird and a baby mammoth with a single stone, before they grow and invade your turf.
On one side you have Twitter/X; it bleeds money and Musk is an idiot, but he has enough money to throw at the problems until they go away, and he has a "vishun" about an "errything app" that would clearly compete with FB/IG/WhatsApp. On another you have the Fediverse; it's small and negligible but it has potential for unrestricted growth, and already includes things like Matrix (that competes with WhatsApp) and Friendica (that competes with FB).
From Meta's point of view, Twitter/X is by far the biggest threat. It could be addressed without federation, but by doing so would feed Mastodon, and a stronger Mastodon means a stronger Fediverse and this power would put Matrix, Friendica etc. in a better position. With federation however they can EEE one while killing another, and still advertise the whole thing as "I don't understand, why you say that we have a monopoly over online communication? We're even part of a federation? Meta plays nice with competitors. I'm so confused~".
"Some data format" is still a pretty vague handwave, IMO. What would they implement that other Fediverse users would need to care about? Some kind of proprietary image or video format? I don't see how that would gain traction.
Fediverse users can already link to FB/IG/WhatsApp content. Are you suggesting embedding it somehow? I'm not sure how that could be done in a proprietary manner that other implementations couldn't copy.
"We now allow big arse videos" is definitely not a feature that couldn't be reverse engineered. Instances can already do their own hosting, or not, depending on the resources the host wants to dedicate.
I'm sure that Meta would just love to be able to push a button that made all their competitors die. Everyone wants that button. Look around threads like this and count how many users would love to push that button themselves and wipe Meta out with it. But I'm just not seeing how Meta is going to do that by federating. As long as everyone keeps on their toes about how their resources are being used and what extensions they're adding to ActivityPub - something that they should be doing regardless of whether Meta is involved - the Fediverse seems pretty solid against attack to me.
Note: I did read your comment fully, but I'm going to address specific points, otherwise the discussion gets too long. (Sorry!)
It is vague because there are multiple ways for Threads to screw with the Fediverse through data formats. But if you want a more specific example:
Let's say that Meta creates a new image format called TREDZ. It fills the same purpose as JPG, but it's closed source. The Threads app has native support for TREDZ images, but your browser doesn't render it.
If you access a Mastodon instance through Threads, everything works well, since the Threads app has support for other image formats. However, since your browser and current Mastodon apps have no support for TREDZ, pics in this format fail to render. You get broken content as a result, and probably some Threads crowds screeching at you because you ignored their picture, saying "u uze mastadon? lmaaao its broken it doesnt even pictures lol", encouraging you to ditch your instance to join Threads instead.
And you might say "reverse engineer TREDZ, problem solved". However:
As such, on a practical level, it would be not feasible to reverse-engineer TREDZ. And even if it was, the time necessary to do so is time that Threads is still causing damage to Mastodon.
Of course, this is just an example that I made up on the spot. Meta can think on more efficient ways to do so.
Yup. As you said, everyone wants that button. But due to the difference in power, Meta is closer to get that button than Mastodon is.
The protocol might be solid, but the community isn't. Communities stronger than the Fediverse died; and the Fediverse has the mixed blessing of decentralisation - the death of a part doesn't drag the other parts to the grave, but the survival of the other parts doesn't help much the dying one either.
Actually, I'd say "let them use TREDZ and destroy themselves if they want, problem solved." In this day and age nobody wants a proprietary image format, and if Threads won't display in a browser they've just blown one of their legs off.
This is a general problem with trying to make Threads depend on proprietary formats, they can't do that and still have it work in an ordinary web browser.
Most people don't even know what's a proprietary image format. From their PoV it would be "shitty broken Mastodon doesn't show images properly". And they would still pressure Mastodon users to switch.
I'm not sure but I think that a similar strategy could work for browsers, using a web plugin.
But even if Meta decided that Threads is unavailable from browsers, it wouldn't be blowing one of Threads' legs off. There are far more mobile than desktop users nowadays; and if they want to EEE the Fediverse, they need numbers for that.
Here's five examples that they'be already done:
(Edited for formatting)