We currently have a pre-existing central directories of XMPP domains at https://xmpp.net/directory.php - the code powering the observatory is available (the most up-to-date code is in Jonas' repo: https://github.com/horazont/xmppoke-frontend-docker )
The upside of that project is that it's an established code base, publicly available as open source and functionally already performs a variety of checks against XMPP domains. Additionally, Jonas and the XSF iteam spent quite some time to make it run in Docker, which making it easy for anyone to run their own instance. The downside is that feature checks (and perhaps an API to be used by clients?) still need to be put in. 0.02$ On 9 January 2018 at 07:39, Daniel Gultsch <dan...@gultsch.de> wrote: > Just do it. > Some building blocks like the compliance tester and the uptime monitor > (status.conversations.im) are already here. You just need to turn the > compliance tester from a command line tool into a webservice. > Worry about things like where to host later. It's more important to > have the tools than to bikeshed about how to use them. > > cheers > Daniel > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > _______________________________________________ >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
