I was wondering if anyone knows how to figure out which instances are blocking this one? I know beehaw is as it was quite public, but now we are blocked by 2 and I am just curious which instance is the second one. I have looked on the awesome-lemmy-instances page and also tried Federation Observer, The Federation Info and FediDB but none of them seem to have this information.
Edit: Lemmymap seems like the easiest option, as you can’t specifically search for an instance. It seems like https://news.cosocial.ca/instances is the other instance that has blocked us! Thank you bdonvr for mentioning this.
Edit2: It should be noted that this is a very small instance as mentioned by PriorProject, and is nothing to be worried about.
It should be noted that cosocial has 10 registered users according to their front-page. Small instances frequently make idiosyncratic federation decisions and exactly because they’re small they have little impact on the overall health of the network.
Beehaw’s defederation as a “load-bearing” instance in the lemmyverse that is already entangled via cross-instance subscriptions is much more damaging and degrades service for like an aggregate 50% of the lemmyverse.
I wouldn’t sweat this cosocial thing, it will probably never impact you in a perceivable way.
I am not worried about it! I was more so curious if a larger instance had blocked us, since then it has some utility to know when commenting in communities on other instances. E.g. if someone from beehaw comments on !privacyguides@lemmy.one I know not to reply to them considering they won’t see my comment (unless my understanding of federation is incorrect)
But someone else might see it.
news.cosocial (remember, that they have a Mastodon instance too) works on allow list anyways