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.

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.

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

Isn’t all of that already available to Meta (and anyone else) via the web UI anyway? They don’t need to be federated for that, they can just use a web crawler. And I assume they are.

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.

I’m admittedly unfamiliar with Eugene, so was using the title listed in the blog post.

Actually the copyright option might be the best one. Theoretically speaking the instance would need to state that all work is licensed only and that every comment and post has the copyright retained to creator/OP.

It’s just a simple tweak of the terms of service, but that would be enough to do it. Getting them to respect it is another ball game, because as we’ve seen with Midjourney and other photo apps, they have clearly scraped photos with watermarks that they didn’t have access to, and have used them to both train their models, and in the final output. This is why there was discussion of a class action lawsuit, although I didn’t hear where that ended up going.

The Mas.to admin claims to have “blocked Meta’s domains” already. Maybe that could prevent the scraping? Maybe not.

deleted by creator

Removed by mod

What does spam/abusive use have to do with Threads specifically.

Also, can you justify your concerns? You just stated a few words without saying why it is a concern. This article did a pretty good job of not only stating the same concern words you used, but why the fears are a bit overblown.

I don’t know the others you mentioned, but how is libs of tik tok a ‘harassment’ account?

Seems reasonable to exercise caution. Plus, unless you have the means, it’d be a tough spot to deal with resource scaling without knowing what the volume of new traffic will look like.

As a small instance, defederating from Threads could do more harm than good. Denying users access to a potentially large amount of content could cause them to move on.

If you’re concerned about them slurping your content, don’t be. They can just easily set up an instance at billjoejimbob.com and slurp it indirectly. They very likely already are.

I don’t know about everyone else here, but my social media use involves me actively trying to avoid The Algorithm™. I subscribe specifically to what I want to see, and actively avoid everything else. You can’t do this in the Threads app. So this is why I’ll be using Trunks or Megalodon over the Threads client.

Every social media platform, UseNet, BBS, and forum – and the planet Earth itself – has had it’s clique of garbage idiots, off in a corner, doing garbage idiot things. They’re inevitable. They’re even here on the Fediverse – in our own precious instances – already. If you don’t engage them – don’t follow that person you hate the most, or sub to the community that stands for everything you hate – things are actually pretty nice. All of this defederation talk feels extremely short-sighted, and is just going to torpedo the Mastodon platform we’ve started to come to enjoy.

If anything, the public declarations of political & social allegiances via choice of instance could just torpedo it all, and attract the trolling idiots like flies. But, we’ve already opened up that can of worms.

And half of the feed is people talking about how addicted they already are.

Umm…read the article.

You’ve completely missed the point. It’s not that Facebook (and by extension, their users) will connect to Mastodon, it’s that they will take over Mastodon, seizing all control for themselves, and coopting the existing userbase.

Right now it’s a separate product. Just like people know that Twitter is not Mastodon, Threads isn’t either. If you want to reach Twitter users, you get a Twitter account. If you want to reach Mastodon users, you get a Mastodon account. Facebook is planning to market themselves as the best way to enter the Mastodon ecosystem. Before long, they will be the absolute dominant server. Then they will have control, because defederation is a weapon they can wield and not vice-versa.

This is not theoretical, either. Google did the EXACT same thing back with Google Talk and the XMPP protocol. And we know how Facebook operates, so we know that this will eventually happen. The only way to stop it is before it starts - Facebook users need to be unhappy (at Facebook) that they can’t reach Mastodon users, so that defederation remains their own problem.

(Separately, I agree with you that Lemmy needs to become more accessible to the common user. But simply handing it all over to someone as awful as Zuck is not the way)

Ignoring everything else, they absolutely intend to collect and sell your data regardless of whether you use or interact with anybody from their service:

"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

It does either way. As you said defederating threads makes an instance not viable for you. Many people might think that way. This defacto lessens decentralization and increases vulnerability to an eventual takeover.

And defederating threads has the issues you mentioned. Both comes with problems and in the end it might split the fediverse.

Or am I missing something?

Its not a little cabin. Remember that scene from UP, where his house was surrounded by urban development.

That is this.

if they do, you can just folow them for here right? Or does lemmy.world have less features than kbin.social?

They might dip their toes in at first. But then you’ll have 9 out of 10 big communities/users on Threads (or probably 99 out of 100 if we’re realistic). And at that point if Meta defederates nobody of those users will care. Threads will become Twitter 2.0 and be its own thing, while Mastodon will be crushed with a tiny user base in comparison (which will get even smaller because most content is on Meta servers, so users switch over to Threads).

There’s a 90% probability that Threads takes over from the failing Twitter. Nothing will change. No one will learn anything. More of everyone’s data will be stollen.

They had 10 million signups within 7 hours of launch.