Kierunkowy74

Meta’s fediverses probably also won’t be able to compete with Threads on this. Threads plan to make federation opt-in is the right thing to do from a privacy and safety perspective, but also means that people in Meta’s fediverses won’t be able to communiate with most of the people on Threads. And Meta has the option of adding communication between Threads and the billions of people on other networks like Instagram (which already shares the same infrastructure), Facebook, and WhatsApp. Longer-term, it seems to me that this is likely to be a huge challenge for Meta’s fediverses, but fediverse influencers supporting federating with Meta have various arguments why it doesn’t matter.

Is it really Meta’s fediverses, when communication between them and their alleged owner is fairly little and actively gatekept by their alleged owner?

Nostr

Change your distribution to MX Linux and use MX Package Installer there. Select Mullvad VPN from “Popular Apps” tab there and MXPI will do all these steps for you.

Authorised Fetch existed long before Instagram Threads. When it is turned on, an instance will require any other server to sign their request to fetch any post. This prevents “leaking” of posts via ActivityPub to blocked instances.

This setting is turned off by default, because some software are incompatible with it (like /kbin, Pixelfed before June 2023, maybe Lemmy too), because it makes server load higher, and it may make some replies missing (at least on microblogging side).

Another one is No Agenda Social, running on regular Mastodon.

Some Misskey instances do not report their MAU numbers. Misskey total MAU is undercounted because of this, but, looking at Misskey instance stats I suppose, that it’s 20 000 at most.
All Misskey forks (Firefish, Iceshrimp, Cherrypick, Foundkey, Meisskey, Sharkey), that are listed by FediDB make another 10 000 MAU.

It’s available on Rebased/Soapbox

Most instance admins are federating with Threads/Meta.

Not on Lemmy. Sort this Fedipact list by software and choose Lemmy to see this.

I was looking for recommendations for alternative instances… I’d appreciate anyone actually responding to my comment.

OK.

Largest Lemmy instances blocking Instagram Threads are (according to fedipact.veganism.social) lemmy.ml, lemm.ee, lemmy.ca, Hexbear, feddit.de, Beehaw, Lemmygrad, lemmy.dbzer0.com, lemmy.blahaj.zone, discuss.tchncs.de, sopuli.xyz, aussie.zone, feddit.nl, lemmy.zip, midwest.social, feddit.uk, mander.xyz, …

Mastodon since 4.2 version supports allows its users to opt into appearing into search results. Just respect this flag with Mastodon users, and you will be fine, IMHO

It’s perfectly possible to create a watertight federated network excluding both federation and scraping from Threads/Meta on Mastodon using authorized fetch and whitelisting.

Authorised Fetch is not supported yet by /kbin

Server side. Lemmy.ml has a slur filter.

I didn’t know. But perhaps it works.

Both Iceshrimp and Sharkey should have better compatibility with Mastodon clients

And if BlueSky ever finishes their own proprietary interoperability protocol (…)

ATProto is open source

List of instances, which will block Threads, listed by MAU

Lemmy is not able to disturb Mastodon as much as other microblogging instances.

Nobody on a Lemmy instance is able to follow accounts (like on Mastodon or /kbin). Thus, Lemmy will not fetch anything from Mastodon unless written specifically to a threadiverse community (and the community being CCed). Because of this, Lemmy instance are less harmful, than (potentially) any microblogging server (be it Mastodon, Pleroma, Soapbox, *key, etc.)

a lot of lemmy instances have the blocked list public

SDF is not one of them

Another example, from lemmy.ml

Gab federates no more.