[guardian-dev] jitsi-monitor to track basic data about all known public instances
Hans-Christoph Steiner
hans at guardianproject.info
Mon Apr 6 06:56:23 EDT 2020
I forgot to add two things:
* This scrapes other sources for the list of instances. If you want it
advertised, then I think you should add it to:
https://github.com/jitsi/jitsi-meet/wiki/Jitsi-Meet-Instances I think
you can just edit that page with a GitHub account. Otherwise, the
README lists the places that are scraped, where you can add them:
https://gitlab.com/guardianproject/jitsi-monitor#source-lists
* This can be run locally to get results based on the local network. So
far, this has only been tested on Debian/buster. I recommend running
this on a throwaway setup, like in Docker or a VM. If you have FireJail
installed, this will run the JavaScript inside of a jail.
.hc
Hans-Christoph Steiner:
>
> With everyone needing video conferencing these days, there has been an
> explosion of public Jitsi Meet instances, which is great to see. In
> order to help people choose which one works for them, I have set up
> "jitsi-monitor", it runs once a day on all known public Jitsi Meet
> instances and gathers some basic data on them:
>
> * configuration including STUN servers, analytics, etc.
> * TLS settings and connection timing
> * TCP traceroute
> * what else?
>
> This script should also work for people to run on their own network to
> choose the closest instance. The source code is here:
> https://gitlab.com/guardianproject/jitsi-monitor
>
> The results from our runs on GitLab CI are here in very basic HTML
> format. I'd love to see this used by someone who makes nice Javascript
> UIs. There is a full JSON report available there too:
> https://guardianproject.gitlab.io/jitsi-monitor/
>
> .hc
>
--
PGP fingerprint: EE66 20C7 136B 0D2C 456C 0A4D E9E2 8DEA 00AA 5556
https://pgp.mit.edu/pks/lookup?op=vindex&search=0xE9E28DEA00AA5556
More information about the guardian-dev
mailing list