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.
Awesome project and the tool looks great - nice work!
There was an existing tool which was similar: https://federation-checker.vercel.app/
Yours is definitely nicer.
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.
To be fair this is the first time I hear about Akkoma, I wasn’t even aware of its existence.
Right now the Investigator queries all instances in the awesome-lemmy-instancecs repo, which means it only queries instances running the Lemmy software. I didn’t really consider this, but evidently this also cuts off Kbin, Mastodon and so on.
To expand on this I would need a list of all fediverse / threadiverse instances, or at least the onest that federate with Lemmy. I don’t know if such a list exists out there.
Alright I don’t really care other than Lemmy anyways. Maybe kbin. IDK your tool is the best among the other ones, so well done 🙏
Thanks a lot! I’ll see if I can make any improvements on this front, but I can’t make any promises.
This tool is great! Thanks for creating it and making it public.
Also, is this the first Lemmy Hug of Death? If so, congrats, I think?
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.
Lmao lemmygrad defederated my instance 🤣 I guess Australians are too “Liberal” for them
Doesn’t support kbin :(
Yeah sorry about that, I couldn’t find a list of instances that also included kbin ones. The best I could find was the awesome-lemmy-instances repo, which as the name suggests is strictly Lemmy.
If you have a list that includes kbin I’ll be happy to add support for it.
There’s this one, but it only includes kbin instances
Thank you. Actually that list is a bit hard to interact with, but I’ve found this API and it works great. I’ll be adding kbin support in the next couple days.
Update: apparently kbin doesn’t support this kind of operation. In other words there’s no way of knowing what instances a kbin instance is federated with. I’m sorry but this really isn’t my fault. I’ll see if I can add it later on, once the kbin devs finish working on this feature.
