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.
Idk what’s hard about it.
It’s a pretty simple thought process.
Another level of complexity is, for example, knowing that lemm.ee bans nsfw content and you can’t post it. What if you want nsfw? You check the tool again, find lemmy.zip which doesn’t have nsfw blocked and has not blocked or been blocked by SJW and Beehaw and many others, you sign up, and you have all you want. What’s so hard or bad about that?
This kind of “what’s best for me alone in the short term” thinking is absolutely destructive to a federated network and is really only a small notch above intentional ban evasion.