Asklemmy

43376 readers

1439 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
[email protected]: a community for finding communities

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago

MODERATORS

[email protected]

Pros and cons of federating with threads? (lemmy.world)

submitted 1 year ago by [email protected] to c/[email protected]

29 comments fedilink hide all child comments

I saw in the posts recently how Metas thread grew rapidly in a span of just a day. I understand that since threads posts a privacy nightmare (no surprises there) I’m leaning towards de-federating with them.

But I am also cautiously excited about the massive amount of content if we federated instead.

So for purposes of discussion, may I know the pros and cons of federating with threads?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 12 points 1 year ago* (last edited 1 year ago) (3 children)

As I've heard Threads is not yet ActivityPub federation enabled- meta is going walled garden for the foreseeable future.

Benefits of federation would be:

Massive available content boost for Lemmy, making user retention and growth easier.
Much wider general user awareness of Lemmy and the Fediverse via federated content titles showing off instance names. May drive more natural user growth.

Cons of federation would be:

Data security. it's Meta. Any and all user information, including admin data, naturally exposed by federated services instantly gets sucked into the Zuck data vacuum to build a user profile. Right now, we're still reasonably insulated from them.
Spam. Threads is already massive by virtue of sucking in all the Instagram users. They would COMPLETELY drown any natural Lemmy content in their sheer volume of posts and votes, meaning lemmy native communities will struggle to gain any widespread traction over their Threads counterpart.
Content manipulation. Anything Meta chooses to promote via their "algorithm" will end up on the top of every federated instance, meaning they can now effectively manipulate all Lemmy content by simply bombarding federated instances with whatever they want.
Moderation. I'm not gonna sugar coat it, the average Instagram user is really dumb and it brings in all the shitty people with it too. Moderation of small instances will become impossible by sheer volume while federated with Threads.
Principle. Meta's practices of extensive monetization and monopolization goes against every principle the fediverse was founded upon (freedom, decentralization, and emphasis on the user rather than the advertiser). By federating with Threads, you are giving Meta a free license to monetize the content you are paying to host on your own independent instance, for free. That just fucking stinks.

[–] [email protected] 6 points 1 year ago (1 children)

Long story short, it’s a 1:15 pros/cons

[–] [email protected] 3 points 1 year ago

Pretty much lol. Given Lemmy's current community situation there's really very little reason to ever federate with them.

[–] [email protected] 3 points 1 year ago (1 children)

I'm wondering if they will even decide to try to federate. They're bootstrapping threads with Instagram that already had 2+billion users. That's insanely big compared to the fediverse. What do they even benefit from enabling it?

[–] [email protected] 5 points 1 year ago

They crush a potential rival in its infancy. That's literally all. It all reads to me as textbook embrace, extend, extinguish.

If the federated web were a company, they'd just buy them out if they got big enough. But it's not, so they can't, and that worries them. But they see the open part of open source as a vulnerability, so they put on a smile, pretend the game is 'if you can't beat them, join them' and then sabotage the protocol in a million ways from the inside while convincing users that your app is clearly the best way to experience the federated web.

[–] [email protected] 0 points 1 year ago

Data security. it's Meta. Any and all user information, including admin data, naturally exposed by federated services instantly gets sucked into the Zuck data vacuum to build a user profile. Right now, we're still reasonably insulated from them.

Couldn't they just run another instance and not tell us the domain name and silently steal all our data anyway? I feel like there is no way to have data security when it is decentralized. All my Lemmy data is on hundreds of other servers already.