I don’t understand how ActivityPub works that well and I haven’t used Threads so maybe I just doing get it.
But why would we have to worry about defederating Threads when it’s a Twitter clone? It doesn’t have communities and such so I would think it’s not compatible. We’re not federated with Mastodon instances right? This seems like something for Mastodon to worry about. How is a Lemmy instance refusing to federate with Threads relevant?
Do we even know is Threads will federate at all? I figure meta is using activitypub simply because it’s cheaper and easier than coding their own, not because they intend to federate. Zuck wants private data so he can sell us ads and propaganda. Allowing people to follow from federated servers both denies him user data and the ability to push ads.
I signed up for Threads, and there were 3 upsides of Threads on their welcome screen, one of them was that it will be part of the fediverse someday. It doesn’t mean they’ll do it, but they definitely intend to use ActivityPub as more than just an internal protocol.
Could be that Threads will use ActivityPub to feverste with other Meta platforms in the future too, assuming they want to add such capabilities to Instagram and Facebook.
It could be, but they specifically used the word “fediverse” in their marketing. It doesn’t make it sound like they want to create a new thing, that would sound like they want to integrate with the existing fediverse.
- Why bother implementing a federated protocol if the intent is not to federate?
- Don’t you think Facebook/Instagram/WhatsApp has the experience to build a social media network without implementing ActivityPub? If federation is not a goal, why constrain yourself to building something that fits into that network?
It is a ready-made software that could let them quickly launch a product, and it can deflect the allegations already made of intellectual property theft from Meta hiring former Twitter developers. Of course they could develop their own, but that would take time and added risk.
What benefit would Meta get from federating with the likes of Mastadon? They want profit, and I do not see a way Meta makes money from letting people follow Threads users from Mastodon, KBin, and Lemmy.
activitypub is less ready made software and more a set of predefined constraints and protocols
definitely more work to federate than to just have a solution that talks to a database! especially at scale
Why did google implement XMPP originally for Google Chat? They originally did federate with XMPP servers. But eventually, they decided that federating wasn’t worth it. At the time they still used XMPP, they just refused to federate.
Why wouldn’t you use ActivityPub as a protocol if it has been proven out and does 90% of what you need? Just because they use ActivityPub, I don’t see them ever Federating in any meaningful way. Essentially, I think the protocol is well designed and Meta is just using it as their starting point with no reason to share any data with the fediverse.
Was that meant to rebut the idea that Meta wants to federate with other ActivityPub services? The fact that Google did the same thing with XMPP, gained user share, then defederated once they achieved critical mass - classic EEE?
The Threads app itself clarifies that the intent is to federate down the road.
Federation would also mean that you could use your account from threads to comment or post on Lemmy. So a Threads user links to a Lemmy post, the post could blow up with users who aren’t familiar with the culture here. I think a lot of people aren’t saying it, but they’re worried about their cool, new favorite platform getting swamped with “normies.”
I don’t care about normies as much as I care about their racist uncles blowing up in the comments with lies and thinky veiled conspircies about non white people.
We are federated with mastodon instances. Beauty of the fediverse
I can follow Lemmy accounts from Mastodon, and post to their threads with reply. I did this with !startrek until it got too active.
And Kbin is so fully integrated with Mastodon the microblog section picks up Mastodon tags. I follow my kbin account from Mastodon so I can boost my kbin boosts.
Threads is an everyone problem.
