Rationale:

• The db currently tracks “has_captcha”. Cloudflare influences that regardless of whether the site is itself configured to push a CAPTCHA.
• The db currently tracks “open_registrations”. The degree of openness depends on whether a node is on Cloudflare, regardless of how the software is configured.
• Checking for Cloudflare is free. That is, no extra connections are needed. It’s simply a matter of checking for the presence of CF-RAY in the http headers on existing fetches.
• The mission purpose of fediseer is to facilitate trust assessment. The use of Cloudflare is a significant factor in that regard.

Hey peeps. Unfortunately it seems the fediverse.observer has been abandoned. This service was what the fediseer was using to detect suspicious instances, based on active users and posts. There's also fedidb but it's API doesn't export the data required. This means this feature has to be deprecated for the time being.

For now all requests to the /api/v1/instances endpoint will return an empty result so as not to break any integrations. The header will also report "Deprecated: true", to hopefully alert anyone not seeing this message.

The rest of the Fediseer functionality remains unaffected.

In this post, I mention how to grab the dataset of instance details. The censure_reasons field is null even when the web UI shows 8 censures. How can that be fetched via the API?

Hello, currently Fediseer does not handle PeerTube instances very well due to their specialized AP flavor, which is a bit of an issue. It may be worth implementing support for this in the future, there is a fairly large PeerTube userbase after all!

So, after putting in my instance name, piefed.zeromedia.vip, and my admin username, guynamedzero, what is supposed to happen? It said that I'd receive a message with an api key, or something along those lines, but I don't think I've received anything. Upon trying again, it tells me: There was an api error: You have already claimed this instance as this admin. Please use the PATCH method to reset your API key. What am I supposed to do from here?

My instance is just me, created during the reddit migration. Just found out about fediseer.

I figure if a Lemmy instance has more than 6 users it’s a notable node that isn’t necessarily running in some mom’s basement for a single user.

I’m trying to add my instance to Fediseer at https://gui.fediseer.com/auth/claim-instance so it can federate.

When I try to send the message, I get an error saying: There was an api error: API Key PM failed

I’m not really sure how to diagnose something like this, but I tried sudo docker logs [ID of nginx container] and one of the entries says "POST /inbox HTTP/1.1" 400 86 "-" "Fediseer/0.25.1" after I try sending the message.

I’m assuming this has something to do with it, but I’m not sure if that’s true or how to fix it even if it is.

Any help would be greatly appreciated.

Please take a look at the guarantee solicitations page and see if you can guarantee for some instances that you can tell are not spam

The Fediseer relies on crowdsourcing information about the fediverse, so the more of us doing this, the easier it becomes.

Hi! I was just checking in to see if fediseer is compatible with activitypub enabled wordpress. I try to add my instance, but unfortunately get the following error:

There was an api error: Error retrieving unknown site info for fusil.uk: 'software'

I have the activitypub plugin installed and was hoping to get onto fediseer so I can join a service which federates smaller instances wider in hopes to expand my reach :)

Many thanks!

The API is documented here: https://fediseer.com/api/

Expanding models :: InstanceDetails gives a useful description of the attributes and their data types, but nothing about how to fetch the whole DB. Is there a nightly ZIP or tarball, or a way to get the dump in JSON?

I tried this:

curl -o fediseer.json 'https://fediseer.com/api/v1/all_instances'

It seems hung for a long time then produces a small file with just:

<html><body><h1>504 Gateway Time-out</h1>
The server didn't respond in time.
</body></html>

update

Nevermind, it works.. Must’ve been a temporary outtage/glitch.