Apparently, these are the statuses of the accounts they are scraping:
406425 "completed" 1533427 "pending" 53541 "read"
Here's a 7MB gzip'd JSON file that indicates the current status of the *instances*. The account metadata is too big to attach. Anyway, this is their view of fedi: instances-p.json.gz
This is their view of fsebugoutzone.org. There's a lot of interesting information in there. They've got, for example, `"processing_status": "completed"`, but they never launched any successful requests as far as I can tell. (I will have to look through the logs again.) They have `"connections": "33435"`, and this appears to be the peer count. They are using instances.social for the `thumbnail_proxy`, maybe that's where they got the list of instances. They have 16,795 on the list, and all of them have `"processing_status": "completed"`, so the queue is probably stored somewhere else.
{ "_id": { "$oid": "673f10ac2aa5fd2484163e28" }, "id": "6628f572b42b8088be06b2fb", "name": "fsebugoutzone.org", "added_at": "2024-04-24T12:05:06.281Z", "updated_at": "2024-11-21T10:02:14.842Z", "checked_at": "2024-11-21T10:02:14.842Z", "uptime": { "$numberInt": "1" }, "up": true, "dead": false, "version": null, "ipv6": false, "https_score": { "$numberInt": "10" }, "https_rank": "E ", "obs_score": { "$numberInt": "70" }, "obs_rank": "B ", "users": "1733", "statuses": "2072037", "connections": "33435", "open_registrations": false, "info": { "short_description": null, "full_description": "FSE temporary bugout zone until the new code is ready, but mostly a development instance, so it will not run like regular FSE: closed registrations (but if you had an account, your old username/password will work), I will shoot anything that annoys me while I am hacking (and if you are hoping for a warning shot, please do not annoy me until ammo prices drop), etc. Lots of things will be broken periodically because this is a development instance. Direct complaints to your friendly local anarchist @p, or if you are a total dick, just #fediblock us based on rumors/assumptions without trying to reach out, just like you did with FSE! Full explanation here: https://blog.freespeechextremist.com/blog/update-and-roadmap.html", "topic": "Free Speech Extremist", "languages": [], "other_languages_accepted": true, "federates_with": "all", "prohibited_content": [], "categories": [] }, "thumbnail": "/instance/thumbnail.jpeg", "thumbnail_proxy": "https://camo.instances.social/6079b328d69223bfa89de4e89dbfa2a691fbefdc/2f696e7374616e63652f7468756d626e61696c2e6a706567", "active_users": null, "email": "fedi@freespeechextremist.com", "admin": null, "loadtime": { "$date": { "$numberLong": "1732161080203" } }, "processing_status": "completed" },
@ricci @eeide@scholar.social Jacobus (Kobus) Van der Merwe (no fedi account, interesting background, https://users.cs.utah.edu/~kobus/ ) Jason Wiese (link goes to a department page)
From that same page:
> CloudLab is part of the National Science Foundation's NSFCloud program.
You may remember that @drand got caught using address space allocated to him specifically, and later that he was part of the teams presenting to the NSF on how to remove misinformation from the internet and get away with censorship. externalizing_the_difficult_responsibility_of_censorship.png
@p@ricci@c92a979036ccbbe62736de83ec9258fe2fc5608f5d51b2185bf2611210523e28@Drand Our timelines return 401 for all of their requests from that address space so if they got anything to/about poast it wasn't directly from us. There was only two instances in that JSON you posted and both of them are tied to us being in the bio of @silverpill as his backup account