[–] [S] 1 point 5 days ago

Thanks! Codeberg.org gives my browser problems, but I was able to shallow clone that over Tor using git.

My first hack was to add a --socks4a parameter to all the curl calls to force it over Tor.

It did not work out of the box. I could see that it sources config.sh. The example file shows API keys. The instances_list.json file shows {"error":{"message":"Invalid Authorization header."}}, which implies that I need an API key. If I simply run this:

curl --socks4a 127.0.0.1:9050 -o "${filename}" 'https://fediseer.com/api/v1/all_instances'

there is no problem. I suppose you have hard-coded an API key to do operations that submit data, which is then used for getting data as well. Anyway, the script works for checking a single instance.

I wrote a script that uses Cloudflare’s ASNs to grab all its IP ranges. Then the script checks without even connecting to the target just by resolving the IP and checking if it matches CF’s range. It’s still just a messy workaround. It’s really something that should be in the fediseer dataset.

  • source
  • parent
  • context
  • [–] [S] 1 point 1 week ago* (2 children)

    It’s still down for me. Just times out. So I have no idea what you propose.

    Anyway, I don’t imagine how a workaround would be possible. The dataset is missing the data. If I have to scrape for the data myself, it defeats the point of a public dataset. I could write in my code a Cloudflare check, but that doesn’t help anyone else using the fediseer dataset.

  • source
  • parent
  • context
  • [–] 3 points 8 months ago

    PieFed doesn't accept PMs from brand new accounts and since fediseer's bot sends a PM out of the blue, PF thinks it's new. I've just coded an exception for fediseer that lets those PMs though.

  • source
  • [–] 3 points 1 year ago (1 child)

    You should have received a pm. If you have not, then something went wrong in the communicationffrom fediseer with piefed. Iirc piefed has some problems receiving lemmy PMs. Pm me with your admin account and I'll reset it and give it to you

  • source
  • [–] [S] 2 points 1 year ago* (last edited 1 year ago)

    There are 4 interesting attributes (which makes Fediseer quite useful because no other dataset captures this level of detail):

    • open_registrations
    • approval_required
    • email_verify
    • has_captcha

    When running select open_registrations,approval_required,email_verify,has_captcha from FSnodeTbl where open_registrations = 0 | sort -u`, we get all varieties of combinations:

    0|||
    0||0|
    0|0||
    0|0||0
    0|0|0|0
    0|0|0|1
    0|0||1
    0|0|1|0
    0|0|1|1
    0||1|
    0|1||
    0|1||0
    0|1|0|0
    0|1|0|1
    0|1||1
    0|1|1|0
    0|1|1|1
    

    AFAICT, the value of open_registrations is not implied by the other variables. It seems to be an independent variable that should mean just what it describes on the face of it.

    And if we consider just cases where open_registrations is true, there are fewer combinations, strangely, but still it’s independent of approval_required (2nd column):

    1|||
    1|0||
    1|0||1
    1|1||
    1|1||1
    
  • source
  • parent
  • context
  • [–] 2 points 1 year ago (1 child)

    Isn't that just a different definition of open?

    One seems to be open but with admin approval, while the other one only counts them as open when there is no such review?

  • source
  • [–] 3 points 1 year ago* (3 children)

    After verifying that the user is admin, will you continue to send PM code when logging in? If so, then software without a message receiving mechanism will still not be able to use Fediseer.

    I suggest you consider the way I did it in Lemmy Federate. I create a private/public key pair and ask admins to add the public key as a TXT record. If the private key entered while logging in matches the public key in DNS, admin can log in.

    This way it is not necessary to query the user with webfinger and send a message. You also avoid the hassle of distinguishing between different messaging structures in the Fediverse.

  • source
  • view more: next ›