I think it’s pretty safe to say that the majority of us are here to avoid another corporate takeover of our preferred platforms. It would seem to me to be a tad irresponsible to allow Facebook into our space with open arms, allowing them to hoover up our data. I would love to keep using Lemmy.world, but will happily change instances if need be, and I feel many share that sentiment.
Well, right now Meta is pushing, not pulling. Meaning, Threads content can be displayed on Masto, but not the other way around.
IMHO, the bigger threat is having Threads content completely dominate other activity pub clients. Other clients / communities could get dependent on it. Then Meta is basically a drug dealer with leverage.
Data collection doesn’t bother me too much. I’m not going to install their client and all of the behavior trackers that come with it, and my activity pub content is already freely available to query on the internet. If they want it, they already have access to it. Everyone does.
Since lemmy can’t pull from mastodon/threads, it seems like a complete non issue for now.
Correct. This is an issue for Masto, not Lemmy. It may never be an issue for Lemmy for all we know. Lemmy is focused on following activity pub communities not individual people.
It’ll affect Kbin.
No offense but Kbin users have a lot more to worry about than the threads issue, considering the amount of development and moderation problems that plague kbin to this day.
This thread isn’t about kbin though. We don’t need to clutch pearls about other services on fediverse when discussing what happens with Lemmy instances.
But we do need to look out for our peers.
Lemmy pull from mastodon if someone from mastodon mentions a user or community of lemmy instance
I will be able to follow and see friends’ posts and sports teams’ posts through Mastodon without needing a Meta account nor install their shitty apps.
All I posted via fediverse is public already, traveling into some obscure instances, so I don’t care if Meta uses or shares my public posts.
Honestly I like the ActivityPub idea. If ActivityPub becomes mainstream I am fleeing mainstream social media.
Or you could just create your own locked down, nerdy circlejerk instance for people like you.
How to Kill a Decentralised Network (such as the Fediverse)
This article is so misleading. XMPP died for the same reason all technology dies. No one used it. Even if Google hadn’t ever used it, it would still be dead. I know this because Google Talk and ALL Google chat apps are dead. WhatsApp killed them all.
You are more correct than they are but are still wrong*. A lot of the interest in XMPP died after they started pursuing standardization and of course after Google close off their servers. It never had a ground swell before or after that either though. XMPP however, still exists to this day. And has become integrated into internet of things, protocols for communications between devices and as well as more comprehensive communication services such as SIP. They literally just had their 2023 Google summer of code complete a month or so ago?
But yeah XMPP is not dead. Unfortunately, it was a surpassed by a number of other services that offered more. Evolving faster than XMPP could while looking to become standardized. It only lost relevance to most. Not it’s life. For what it’s worth since 2000 or 2001, there’s hardly been a day that I have not been logged in to an XMPP server. I’m logged into one right now.
In other words, Threads could help spreading the ActivityPub protocol more, not the other way around
This, the real threat is the amount of content that federates out possibly hurting others servers’ performance as their enterprise kit will scale better.
How? Because this doesn’t make an yota of sense to me.
Flipboard federated. Are you flooded with news from them?
Minds is also federated. I bet most people in this story had no idea and have never seen a single post from minds.
even if they are only “pushing”, there will still need to be profile data exchanged with Threads in order to access it, if they have http signatures enabled (i.e. authorized fetch under mastodon)
This is what happened with Google and XMPP