Threads users cannot subscribe or post to Lemmy communities or follow Mastodon users (yet). Threads has a sort of halfway federation situation. Mastodon users can follow Threads users without having a Threads.net account but that's it.
Also, the ability to allow Mastodon users to follow Threads accounts is opt-in, and only a small portion of users have chosen to do so.
You won't see it on Lemmy because there is no way to follow individual users on Lemmy. Here's an example of viewing a Threads user from my instance. There is no content because Kara cannot interact with Lemmy and Lemmy users can't follow her.
On Mastodon, Threads accounts (or any account) won’t federate to your instance until you (or someone on your instance) specifically requests to follow. It’s a common misunderstanding when people think that federating with Threads.net will “overwhelm” a small instance.
Also, not every Threads account has opted into federation. So there's really very little available content out there.
Threads accounts (or any account) won't federate to your instance unless you (or someone on your instance) specifically requests to follow. It's a common misunderstanding when people think that federating with Threads.net will "overwhelm" a small instance.
Threads is twitter style (like Mastodon) so it's not going to have much to do with Lemmy. Threads allows users to opt-into a sort of half-Federation where Mastodon users can follow their content. It's a unique case and not how Federation normally works.
With Mastodon, content from users on other instances is not "downloaded" unless someone on that instance specifically chooses to follow it. So it's not like every small Mastodon instance that federates with threads is going to be overwhelmed by all the millions of user feeds on Threads.
Tbh there is a lot of misunderstanding surrounding Threads federation, but in short- there is no technical way for them to "extinguish the fediverse" even if they really, really, wanted to.
"Defederating" just means two instances won't talk anymore. For example, your instance (lemm.ee) is currently defederated from three others (You can see here). It means you won't see any posts/comments from users on those instances.
Kiiiinda, Threads users can opt-in to have their content syndicated out via ActivityPub (and be followed be mastodon users). I'm not positive but I believe it's still only one-way, meaning Mastodon replies won't show up on Threads. It's basically an RSS feed.
Looks like a Nostr instance? Nostr is kinda like Mastodon but not using ActivityPub. To my knowledge Nostr is not blockchain related but it is exclusively used by cryptobros.
Generally it's been an overall positive experience.
In short, when too many cooks are in charge, it’s hard to make a good meal. Take content moderation, for example.
The take that Fediverse moderation is "not as effective" always makes me smile, because:
The moderator-to-user ratio is several orders of magnitude better on the fediverse because volunteer-run instances have zero incentive to grow beyond their ability to self-moderate. But also-
Do you really expect that paid employees (or even trained AIs) are going to be more effective at recognizing who/what is disrupting a community than existing members with a personal stake in it's quality?
Also, as aside I am very happy they said "Bluesky, if it manages to become truly federated" and not the "promises to be" or "is federated" language we usually see.
Great point, absolutely! I don't subscribe to the "dead internet theory" but my time on the Fediverse has also convinced me that all of the corporate platform's traffic numbers are almost certainly heavily inflated (probably to justify higher ad prices).
We have an entire instance dedicated to popular 1960s television show Star Trek (don't go there)
Size has not much to do with it. If a hypothetical instance allowed a "troll farm" to set up shop there, sane admins on other instances would de-federate from the one that allows trolls pretty quickly.