How to use:
The url must be the hostname only, NO SLASHES, like this: lemmy.dbzer0.com, don’t use https://, don’t append a slash afterwards (lemmy.dbzer0.com/), only the hostname including the subdomain if it has it (in this case, lemmy).
If the instance has blocked the IP address from the server, or it is stuck and its API is not working correctly, it returns “Not a Lemmy instance” (I am too busy to fix this right now).
If the url is not formatted in a way it can process it, it will say Invalid URL. Better processing can come in the future. I won’t be updating it now.
- URL: https://federation-checker.vercel.app/
- Source code: https://github.com/lemmygod/federation-checker
In the backend, it just scrapes https://fba.ryona.agency/?domain={url} and uses the api https://{instance}/api/v3/federated_instances
PRs welcome.
Honestly it works better when deployed locally in a development environment. I think Vercel’s IP address is just blocked by cloudflare and other blacklists that stop automated stuff? Idk. Can check back in a few days.
Nope. It only tells you who dislikes it for any reason. Is sh.itjust.works a bad actor? Is lemmy.world a bad actor? If not, then why did Beehaw.org block them? According to them it was because they were open registration. Misunderstandings like these are common.
If, because I follow your advice, I join sh.itjust.works and I don’t have Beehaw content available because I am blocked, is it because I’m a bad actor? Nope, I just picked the wrong instance. Nothing wrong in looking through the list to see who isn’t blocking what you want to see and joining that.
Both these instances are temporarily blocked by beehaw as they couldn’t get trolls originating from these two instances under control otherwise.
The lack of registration screening on a federated network is at best a sign of severe mis-management and you really should not join such instances as long as this situation remains as it is.