Defederation Investigator for Lemmy
defed.xyz
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.

  • cwagner@lemmy.cwagner.me
    English
    8·
    11 months ago

    baraza.africa is not checked despite being in the awesome lemmy list.

    It’s my defed-checker testcase, because they recently went whitelist only and defederated me that way. So the way I understand it, your tool should work there, it’s just not checking this instance for some other reason

    • Nerd02@lemmy.basedcount.comOPEnglish
      14·
      11 months ago

      Oh interesting. Now that you pointed it out I think I’m only checking instances’ blocklists, not whether they are white list only. But I should fix that, thank you for reporting it.

    • Nerd02@lemmy.basedcount.comOPEnglish
      4·
      11 months ago

      Update: I’ve written the code to do that, but I think it would require some overhaul of the UI. For instance, my instance has been blocked only by awful.systems, but by grouping together under “defederated” both those instances that have blocked me, as well as those that are on allow list only, I end up with over 70 instances in the “defederated” block.

      I think this makes for a very confusing UI, as I can’t know for sure who of these people hates my guts and who simply hasn’t heard of me. I think I’ll add an additional accordion box for the instances that haven’t included you in their whitelist.

      • cwagner@lemmy.cwagner.me
        English
        2·
        11 months ago

        Yeah, here the use cases differ ;)

        I only care about instances that won’t send me updates, I don’t care much about the reason they don’t, so I’d be perfectly fine with seeing 70 instances in the defederated block. But I guess this one is pretty simple to solve by making a new block “whitelisted, and you are not in it” ;)

          • cwagner@lemmy.cwagner.me
            English
            1·
            11 months ago

            Nice, works great!

            FYI, I needed to add @sveltejs/adapter-cloudflare to the devDependencies to get it to run locally.

            • Nerd02@lemmy.basedcount.comOPEnglish
              1·
              11 months ago

              Yeah I added it to the dependencies minutes ago. I am trying to move it from Vercel (where I just got suspended) to Cloudflare, so that’s why it’s there.