Open richvdh opened 4 years ago
I believe this is scope-creeping, as the federation tester should only test federation imho. Having a "is my hs all right" tool would definitely be helpful, but I'm not sure this is the right place to do it. Maybe we could have a matrix-client-tester
project (or some other name of the same essence) that would perform some basic diagnostic on the CS API of a HS?
I believe this is scope-creeping
well yes, hence my original comment "I'm not sure if scope-creeping ... is something we should do" :)
I guess I've got a couple of thoughts on this:
server_name
of the instance.well yes, hence my original comment "I'm not sure if scope-creeping ... is something we should do" :)
Yes, sorry I didn't make it obvious enough that I was replying to that :p
that a "check my HS is ok" tool is useful, why not build it in here, and rename the project to "matrix-server-tester"?
It's one possibility, we could probably change this project to be a broader HS tester, with tests on well-known client resolution and also some info-level stuff about e.g. available UIA flows or unstable features.
When checking the matrix/client (containing the base_url
) we can also validate the public_baseurl
? I think we are all on the same page about this additional federation test.
Validating org.matrix.msc3575.proxy
would also be handy.
I'm not sure if scope-creeping the federation tester into a general "is my server behaving sanely" tester is something we should do, but:
We could usefully check that
https://<server_name>/.well-known/matrix/client
is sensible (for instance: does them.homeserver
point to a working client-server API?)