vaguerant

There are literally, not exaggerating, over one billion Instagram accounts in existence. It’s self-evidently not the case that they have just silently registered everybody a Threads account and are counting those numbers.

Defederation and the Dutch

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.

The other problem here is that I don’t think a lot of people actually know how defederation works. There’s lots of takes like “I don’t want Meta to get my data, so we have to defederate.” But defederating stops you from receiving their content, not the other way around. Once Threads actually is federating, defederating it will stop people seeing posts from Threads users. That has its own merits, but it doesn’t protect your data in any way. If you don’t want corporate entities to access your online posts, either send them via some private end-to-end encrypted system where only you and the direct recipients can see them, or don’t post them online at all. The Internet is on the Internet.

Now, a bit more of an explanation on what defederation is: while the decentralized nature complicates things (since different servers will have different defederation lists), defederation is closer to a Reddit shadow-ban than whatever it is people are imagining. If literally everybody defederated Meta/Threads, they would still see our content, but from their (Threads users’) perspective, it would just seem like we’re all giving them the silent treatment, because we never respond to their posts or comments.

“Maybe the worst bluff I’ve ever seen.” - Michael Bluth

Yeah, the front page is working just fine, what’s not as good is going to a specific community for a subject you’re interested in which currently has 1-3 posts and zero replies.

I believe they’re talking about a situation where somebody is like …

Wow, everybody check out this amazing thread! https://someother.instan.ce/post/1194109

Anybody who sees that link and is not already from someother.instan.ce now has to track down that post on their home instance in order to interact with it, which is a bad experience. It’s not the absolute worst thing in the world, like the home URL for the discussion we’re in right now is https://lemmy.world/post/1194109 and if you paste that URL into your local domain’s search it should find you the relevant discussion locally, but it still kinda sucks. In theory this would be sort of solve-able on the server end by having it search for any instance links behind the scenes and re-write other people’s links to point to the equivalent page on your own instance, but right now there’s no “nice” way to handle that situation.

The linked page specifically tracks Lemmy, although it’s not clear to me whether it’s tracking posts by users from Lemmy instances or posts to Lemmy instances, which is a medium-sized distinction (the latter would include kbin, Mastodon and other Fediverse users who are posting to Lemmy from their home instance, while the former would obviously include only Lemmy users).

Time for somebody to make an EU-exclusive Mastodon instance called realthreads.legit and put it up on app stores. The real way to grow the fediverse in a hurry is to trick people into it. /s