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).
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.
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).
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.
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.
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!
Uh yeah that is true. This was a one afternoon project, so I kinda threw the frontend together without thinking too much of it. I guess truncating the protocol instead of relying on the users doing it makes sense.
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.
It's a single line of CSS. It's very easy to fix on the Lemmy web UI (not so much on Jerboa). At one point I even considered fixing it myself and making a PR but then other stuff came up and I had to disable emojis on my instance, so it's no longer a problem of mine unfortunately.
Uhh the price tag? I just bought a new phone after 6 years of honoured service from my old one, payed the new one a whopping 300€ and it already felt like a rip off. Ain't no way I'm paying four digits for a phone.
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).