IMHO this is 100% the plan. If they play their cards right they stand to take out two birds with one stone (heh). They’ve already paid celebrities to be on there.

Still, this can only happen if Threads gets massive enough relative to the rest of the fediverse that the incompatibility doesn’t hurt them equally.
…that is to say, it’s all pretty likely, unless other strong competitors show up with ActivityPub support.

It’s not gonna extinguish the fediverse in the same way nobody leaving reddit joined Mastodon as a replacement. They’re technically compatible, but these are entirely different styles of sites we’re talking about. Lemmy and Kbin are gonna keep on trucking regardless of what happens to the Twitter-likes.

But they’re definitely going to try and kill Mastodon/similar through social engineering. Everybody’s favorite content creators, organizations, and brands will be on Threads, not Mastodon, and when they lock it down we’ll lose access to them and end up needing a Threads account. I don’t understand why anyone trusts this company won’t try to secure market dominance and then monopolize it. The guy says “we’ll just be right back where we are now,” but this could easily decrease the Mastodon population by pulling away anyone who doesn’t care about federation or open source and just wanted a decent Twitter alternative.

I think the people that value being on a decentralized service will stay on a decentralized server. The people that would abandon one platform to follow their favorite “high follower” poster are normies that never cared about what service they were using to begin with. Meta may absolutely take a large share of users to their platform in the future if they shut off federation and our favorite celebrities and shitposters are no longer visible. But I don’t really see how that is any different than Twitter currently having all the celebrities and high volume shitposters. We already can’t see them. The EEE argument just strikes me as sour grapes that “their” users are going somewhere else. And I’m on the fediverse (both Mastodon and kbin) so I see the value here. But I’m not going to get angry that normies don’t want to put the effort into learning this ecosystem when they have their own lives and struggles and a limited number of social causes to care about.

Now what does bother me is Meta having an outsized influence on the development of the protocol of ActivityPub. We’ve seen something similar to this with Google using Chrome to push some additions to how browsers handle HTML standards/elements, like supporting DRM.

The thing is that this can happen even without active malice.

If the product owners or engineers decide “hey, we want to add this cool feature, but it’s not supported by activity pub” the path of least resistance – bypassing the long process of changing the activity pub spec and getting everyone else on board – can be super tempting, and come from a place of wanting to make your product better.

Those ostensibly good intentions can lead to E/E/E without actively meaning to.

EEE was my first thought on seeing that threads would federate, so I felt a bit of relief when I looked at the op just now and saw that Rochko directly addressed this, then I read what he said and it doesn’t seem like he addressed it at all.

Yeah, I don’t find his answer on E/E/E comforting. However if nothing changes hopefully the niche that’s already on Mastodon and kbin/Lemmy could survive regardless of Threads as I’m fairly happy with the state it is right now.

I’ve posted this elsewhere in the thread so hopefully it doesn’t feel spammy, but this is from their privacy policy:

"Information From Third Party Services and Users: We collect information about the Third Party Services and Third Party Users who interact with Threads. If you interact with Threads through a Third Party Service (such as by following Threads users, interacting with Threads content, or by allowing Threads users to follow you or interact with your content), we collect information about your third-party account and profile (such as your username, profile picture, IP address, and the name of the Third Party Service on which you are registered), your content (such as when you allow Threads users to follow, like, reshare, or have mentions in your posts), and your interactions (such as when you follow, like, reshare, or have mentions in Threads posts).

We use the information we collect for Threads for the purposes described in the Meta Privacy Policy, including to provide, personalize, and improve Threads and other Meta Products (including seamless personalization of your experience across Threads and Instagram), to provide measurement, analytics and other business services (including ads), to promote safety, integrity and security, to communicate with you, and to research and innovate for social good."

https://help.instagram.com/515230437301944?helpref=faq_content

What should happen? That’s all public information, they can (and probably do) scrape this already. As does all and any AI project and company.

Isn’t all of that already available to Meta (and anyone else) via the web UI layer anyway? They don’t need to be federated for that.

Frankly, there are other instances out there that I’m more worried about than Threads.

They already can, everything you do on Mastadon is already public.

EEE, Embrace, Extend, Extinguish. Meta may very well be embracing federation concepts to eventually return back to their former selves.

I’m no fan of Meta or their practices, to be clear. Though I do think there are potential benefits in having the ability to communicate cross-platform, so long as some reasonable safeguards are put into place. I’m firmly in the camp that doesn’t believe that Google killed XMPP because XMPP was never a popular or widespread protocol prior to GTalk, and the users who came and went when Google did what they did were Google users, rather than XMPP users. So much like Eugen here says, it went back to how it was before they got involved.

That said, I do think that Meta in its current incarnation is an entirely different animal. I suspect that early on in a post-federated world, we’ll start seeing dark patterns intended to lure users to Threads. I’m envisioning registration gates similar to paywalls on news sites. “This content is available exclusively on Threads! Click here to register your account!” type stuff. More sinister, there’s nothing to stop Meta from appending advertisements in the body of posts created on Threads. Hell - they could go full evil genius and suppress that they’re doing it entirely on their own platform since they’ll have some other ad delivery mechanism there, which would mean the only people being served those ads would be federated users OFF of Threads who see or interact with content created on Threads.

So while I’m not a doomsayer about Threads and federation, I do think that we as a community are going to have to make some decisions about how to handle them. Having access to a community the scale that Meta will produce isn’t necessarily a bad thing. And because of how Lemmy / Mastodon / KBin / Fediverse apps work, we as users will always have the ability to control what we see in our feeds. At worst, it makes /All/ less usable, which is admittedly quite a big loss given how useful it has been to get subscribed to worthwhile content since joining Lemmy. And obviously, some instances will elect not to federate with Threads at all, which gives users choice on the type of community and content they want to interact with regularly.

With some care, likely some effort around defining usage rights for user generated content, and some new content control / filtering capabilities yet to be developed, I think that these networks can coexist in a way that is mutually beneficial to a degree, but if not - defederation is a click away.

Ima guess that Meta’s support and brand recognition dwarfs Mastodon’s, not re-assuring and rather self absorbed imo.

Yeaaah, when I read this I was just like, “Have you been outside of Mastodon lately? The brand’s not so great to those folks that have heard of it in context.” Nearly every time I’ve seen Mastodon come up outside of Mastodon, it’s to complain about it being confusing or only used by tech nerds and there’s nobody worth following there.

And I personally like Mastodon, but there’s no denying the brand’s not reputable to many folks, and it’s probably still relatively unfamiliar/unknown to a majority of folks that don’t closely follow social media stuff.

The problem is that Mastodon’s brand is absolutely nothing and Eugene has been very resistant to popular features. He’s forgetting that the ways in which Mastodon are opinionated are not very popular even among Mastodon essentialists.