For the most part, Threads content just wouldn’t appear on Lemmy at all. It’s like how you can’t see Mastodon users’ timelines on Lemmy. e.g. Jeri Ryan from Star Trek is on mastodon.world, but you can’t read her blog from Lemmy because it just doesn’t display microblog content, only stuff that’s sorted into groups (communities).

The one exception is that Jeri Ryan can track down the equivalent group on her Mastodon instance and “microblog” directly into the group. Mastodon has some hacky tweaks to do things like reading the first sentence as a heading, the second line as a URL, and the third line as the post body, so if you’re especially dedicated you can post to Lemmy from Mastodon. If Threads cares enough, they could add similar functionality to Threads to make it technically possible to post to Lemmy as long as you try hard enough, but just regular people’s blog posts on Threads won’t display on Lemmy at all.

Thanks, I appreciate it! It took a stupidly long time. :V

On some level, it’s probably not that important that people understand all this stuff, but I think the most dangerous thing is people believing that their data will be protected if Threads gets defederated. Any other confusion is basically harmless, but that’s the one thing where people have a false sense of security, because Meta has exactly the same access to your data whether or not they get defederated.

No, I don’t want to? Weird take.

Anti-Meta Fedi Pact, you fill in a web form saying you’re an instance owner with your instance admin name and at some point you should be added to list (manually).

I think it just runs on good faith, I don’t think there’s any verification that you are who you say you are.

Thanks, this is extremely thorough and easy to understand. Very well put. I can see how for anyone with sufficient distrust of Meta and its users, it makes sense to defederate anybody who might serve as a relay between them.

In the meantime, I hope kbin can catch up before Threads starts federating, so I can just interact with people from here. Currently, there’s people who I can’t see/can’t see me from kbin, not due to defederation but simple bugs in kbin’s current ActivityPub implementation. If/when mastodon.social gets defederated, there’s people I won’t have any mechanism to speak to without registering a third account somewhere in the fediverse.

This explains why it’s a good idea to defederate from Meta/Threads, but why defederate from other non-signatory instances?

Don’t sell the bots short, they can probably sell you a pill that helps you conflate things.

Thanks so much for publishing your findings re: spambot-afflicted instances. Even though I’m from kbin, this should mean lemm.ee’s actions will help improve the rest of the threadiverse, too.