Used to generate stats for arewereadyyet.com
  • JavaScript 58.1%
  • HTML 37.3%
  • Shell 2.8%
  • Dockerfile 1.8%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2019-05-22 16:46:24 +01:00
.gitignore ignore data 2019-03-12 17:24:52 +00:00
Dockerfile Make awry scraper have a docker file 2019-05-22 15:29:24 +01:00
history.txt include a newline... 2019-03-08 16:56:01 +00:00
homeservers.sql insert user count 2019-03-20 15:19:51 +00:00
index-template.html Make awry scraper have a docker file 2019-05-22 15:29:24 +01:00
output-html.js update template to include second (users) dial 2019-05-22 11:20:41 +01:00
package-lock.json init 2019-02-21 13:35:30 +00:00
package.json init 2019-02-21 13:35:30 +00:00
parse.js update to match fed tester output 2019-03-27 21:40:35 +00:00
README.md Make awry scraper have a docker file 2019-05-22 15:29:24 +01:00
remote-import.js Make awry scraper have a docker file 2019-05-22 15:29:24 +01:00
run.sh Make awry scraper have a docker file 2019-05-22 15:29:24 +01:00
test-homeservers.js Make awry scraper have a docker file 2019-05-22 15:29:24 +01:00

homeserver-status

From a list of visible homeservers, and a list of phone-home servers, hit them each with the federation tester, then parse the result.

There are separate scripts for each step:

  1. homeservers.sql is used to create a new SQLite DB called visible.db with a single table.
  2. remote-import.js connects to juventas and inserts all visible homeservers from 2019-01-01.
  3. test-homeservers.js looks at each hostname in turn, and tests each one against https://matrix.org/federationtester/api/report. It writes the response to the db. It does not parse the response. This script sorts by lasttested, so that if interrupted you can just run it again.
  4. parse.js takes each response per homeserver and parses it, storing the results in the db.
  5. output-html.js takes two arguments, a template file and an output file. It will generate a single page to be deployed.