Yeah, a UI like that will definitel make sense as the number of instances grows. That'll require a server to run it. This is a quick and dirty GitLab-CI thing with static files on GitLab Pages. But this code should be useful for setting up a compliance checker.
.hc Abel Luck: > Nice work Hans! > > Reminds me of the XMPP compliance tester.. which serves a sligthly > different purpose: list XMPP servers and the XEPs they support and > suggest ones with secure settings. > > https://compliance.conversations.im/ > > Still, could be a nice UI inspiration. They used to have a list of all > servers at once, but they removed that, I guess to reduce spam? > > ~abel > > Hans-Christoph Steiner: >> >> 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 >>> >> > _______________________________________________ > List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev > To unsubscribe, email: [email protected] > -- PGP fingerprint: EE66 20C7 136B 0D2C 456C 0A4D E9E2 8DEA 00AA 5556 https://pgp.mit.edu/pks/lookup?op=vindex&search=0xE9E28DEA00AA5556 _______________________________________________ List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev To unsubscribe, email: [email protected]
