@jan how do I know if Threads has blocked my instance? I've tried to connect to various threads.net accounts but it's not working. My instance is not blocking threads.
@thomas@jan Any luck in connecting with Threads‽ That is weird as I do not see why you would be blocked. Have you tried reaching out to Meta about this‽
@thomas@jan I would contact them as they usually respond (or at least react). I remember complaining about search items being censored (including the country Niger 🇳🇪 which had experienced a coup at the time) & they quickly responded by unblocking it.
You should be able to contact them via the help page within the Threads app.
Not just that, it is actually “just another instance”.
People have been blocking instances for the most ridiculous reasons, years before the “Twitter Migration” and Threads announcement. This Threads/Meta thing just got overblown because, “Meta/Facebook/Zuck”.
Instances, be it xyz, abc, mno, threads, tumblr, wordpress, whoever, can freely block whichever instance they want, for whatever reason they want. Their instance, their decision. It has always been that way since instance-blocking first appeared in fediverse software (which was years before Mastodon came into existence, AFAIK).
@johnclint Maybe, maybe not. Sometimes a server and/or the software/platform your instance is using, have issues finding certain instances even if they haven't blocked each other.
There have been cases I had to communicate with different instances to fix their interoperability with each other, and often than not, it was because one or both instances have a server-backend-related configuration causing it, and has nothing to do with “blocks”.
@thomas@jan Hmm…yeah, I just realized it is hard to contact Meta via email or phone call, as they insist on people creating an account (unless you are contacting their legal department for obvious reasons).
What happens when you try to follow an account like @potus or @whitehouse (those accounts are federating)‽