Discover who has defederated your Lemmy instance with the Defederation Investigator.
EDIT 3:
All good now, the DNS has done its thing and defed.xyz is fully operational! Once again, thank you all for having checked out my tool, it means a lot to me.
Deploy problems, read more
EDIT 2:
I've managed to fix it as well as add some optimization measures. Now it shouldn't ramp up bandwith nearly as fast. The DNS records are still propagating for https://defed.xyz so that might not work, in the meantime you can use the free Netlify domain of https://sunny-quokka-c7bc18.netlify.app
EDIT 1:
You guys played too much with my site and ended up consuming this entire month's 100GB limit of free quota, so the site is currently blocked.
This is probably my most succesful project ever, thank you all for checking it out. It will take me some time to find another suitable host and move the project there.
ORIGINAL POST:
I couldn't find any tools to check this, so I built one myself.
This is a little site I built: the Defederation Investigator defed.xyz. With it, you can get a comprehensive view of which instances have blocked yours, as well as which ones you are federated with.
The tool is open source and available on GitHub. Hopefully someone will find it useful, enjoy.
Oh didn't know about that. It doesn't look too accurate though. My instance was defederated by some guy and it isn't showing. Anyway thank you, glad you like it!
Does defed.xyz checking other softwares like Akkoma? For my instance, defed.xyz shows only dubvee.org is defederated, which is correct.
But in the other hand, federation-checker shows only matrix.rocks defederated, which is a Akkoma instance. I'm not sure is it correct since IDK where is Akkoma's defederated list but both sites showing different sites.
Not sure if it's the first but it's definitely a first for me. In retrospect I could have written it way better, the logic was a bit rushed, but it should be fixed now.
I love the amount of support I've been getting from this and other threads, thank you for using my site.
In my experience, the data on there is significantly outdated/incorrect. The easy way to check is the domain reverse lookup- pick any instance (e.g. sopuli.xyz) and enter it into the reverse lookup. Then compare that to the official published list at sopuli.xyz/instances.
As of right now, FBA lists 9, while the official list is 15. The lists are significantly different as well, with each having multiple entries that are not on the other.
It was originally developed by Kiwi Farms when they were running their own Mastodon instance.
They built this tool because they were being massively defederated (for obvious reasons) but eventually gave up and closed their Mastodon instance.
Since then, other instances apparently not related to Kiwi Farms (but usually still that kind of "free speech" ones) have reinstantiated the service.
It also has a slur immediately on the page you linked
Good to know. Feel free to use that if you prefer it, the only reason why I made this was because I wasn't aware of the existence any other similar tool.
What does returning errors mean? I had a main account that I tried migrating away from lemmy.world, only to have it return errors from lemmy.world. I can't see two thirds of the comments I can from this programming.dev account.
For some reason when I query programming.dev, as well as a couple other instances from my Vercel deployement I get 403s "Forbidden" errors. Not really sure why, it works when I run it from localhost? Maybe them or their provider have somehow blocked request from Vercel because they are afraid of bots? It's anyone's guess really.
This site is built on top of the lemmy-js-client, which is maintained by the Lemmy developers, unfortunately there isn't any API documentation to look at, so for those times when the JS client doesn't work it's very hard for me to debug it and troubleshoot it.
BTW you can look at these errors yourself in your browser's "network" tab, all errors return 500s. In the request body you can see the queried URL, in the response you can see the error message. Sometimes it's "Forbidden", some other time it's a timeout (possibly due to the instance being offline or severely overloaded).
Sure, I could do that. The only reason why I didn't was because that info is just one click away, it's really easy to see that from an instance's web page (while it isn't so easy to see the rest of the data I am displaying).