I didn't come to a new service just to see it get taken over by the corporate beasts who ruined the internet in general, and I am sure as hell am not going to use an instance that doesn't care about its users.

I think the admin of this instance might have been paid off to federate with Threads, it being one of the most popular.

So, I am giving y'all 24 hours to defederate and if the Lemmy.world admins don't, I'm-a bounce and close down my subs behind me

That is all

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

[+] RxBrad 44 points 1 year ago* (last edited 1 year ago) (6 children)

[deleted]

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

@RxBrad

@pinkdrunkenelephants

They arent smart, they’re reactionaries

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

I would not be surprised that after Twitter, Meta’s next target is Reddit, which is ripe for a serious commercial rival. Meta are probably working on a Reddit replacement, using activitypub and their experience with Threads. If you federate already with Threads, then it is a relatively small step to extend that to Meta’s Reddit killer. Maybe federation with Threads will automatically be extended by Meta to this new app. Give them an inch….

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago)

This is true - the bigger impact would be on Kbin instances that are both Threadiverse and Microblogverse facing.

However, if you go on Mastodon you can see Lemmy threads as posts which you can click through to the hosting instance and also boost (but not downvote). So for Lemmy if Threads.net federates, the biggest impact would be exposure of content to Threads users who then come in to Lemmy instances but not logged in or who could boost content and distort things.

For Kbin instances and also Mastodon it could mean being swamped with content from Threads.net.

Personally I do think overall the Kbin/Lemmy/Mastodon servers should probably not federate with Threads.net. The content appears to be poor and it could flood the fediverse with crap, when really it's still small and needs to grow organically. Threads.net is at 70m users already and rising rapidly, while Mastodon is at 8m (1.6m active) and the Threadiverse is more like 130k across Kbin and Lemmy. Mastodon/Kbin/Lemmy need time to establish what it means to be an independent federated social media network. They can always federate with Threads.net in the future - rather than it being Meta's choice, it should be the communities choice if and when they want to federate with a behemoth network.

[–] corroded 3 points 1 year ago (2 children)

I was a bit confused about this as well. Once Threads implements ActivityPub, what would federation with lemmy.world actually look like in practice? I understand how federation works between Lemmy instances, but how would a microblogging platform fit in? Would Threads users just be able to post to Lemmy, or would it somehow show up in a Lemmy community when a Threads user makes a post on Threads?

I'm not really understanding how two different services like Lemmy and Threads can be intercompatible.

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

Lemmy communities are "groups" in ActivityPub parlance, and groups do exist on the microblogging platforms. Using Mastodon as an example for now, a Masto user could find the group equivalent to a Lemmy community and make a post and/or comment there and it would show up on lemmy.world and anybody else who federates with that Masto instance. In reality, the groups experience is kind of terrible and a poor interface to these thread-style communities, and you lose all kinds of features like the recency/score sorting algorithm, the ability to downvote things, etc.

It would take a true masochist to post to lemmy.world from Mastodon, which is why you almost never see it. I've seen one Mastodon user in my time on the threadiverse so far. Most people who are already on the microblogging side of the fediverse have just chosen to register a separate account on a threadiverse instance so they can have an actual usable interface rather than stuffing a link aggregator through a blog-shaped hole.

Groups don't even exist on Threads currently. Maybe they will by the time they implement ActivityPub, but they may not consider that to be a core goal as a microblogging, Twitter-style platform which has no obvious use for them. This would currently make Threads an even worse interface to the threadiverse (kind of ironic) than Mastodon, which I can't stress enough is already awful. You would just have to search for individual posts by browsing somewhere like lemmy.world directly, copying and pasting the URLs into the Threads app or web site to populate the conversation in their interface in order to reply to the posts and comments there.

In short, using Lemmy via Threads is probably going to be such a nightmare that only turbo-nerds will try to do it, and turbo-nerds are more likely to realize "This is awful and I should just go join Lemmy or kbin or something," than persist with that hassle long-term. Now, kbin users have more justification to be concerned about how Threads will impact their communities, because kbin supports microblogging directly--in corporate terms, it's like if Reddit and Twitter combined into one site that you could tab between on the fly. This means kbin users will be more likely to see Threads content and vice versa.

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

Check out kbin, it supports both

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

And it will still connect to Lemmy, since we all use the ActivityPub protocol?

What is your point, exactly?

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

@RxBrad
@corroded
As you can see here I can also comment from Mostodon, the most mastodon-like app ;-) . Likewise, threads can participate in threadiverse once they federate. That's how federation works.
@pinkdrunkenelephants