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.

you are viewing a single comment's thread
view the rest of the comments

[–] Cryxtalix@programming.dev 2 points 1 year ago (1 children)

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.

[–] Nerd02@lemmy.basedcount.com 3 points 1 year ago

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).