Check for MSC4143 (MatrixRTC) in .well-known

[pReya]

Any chance, you could add the check for MSC4143 (MatrixRTC in the .well-known/matrix/client) to this tool, too?

What about the other requirements for Element Call, like MSC3266, MSC4140 and MSC4222? Can these even be checked/queried remotely?

[MTRNord]

Hm interesting I can look into what can be tested. I try to avoid doing things that require login currently and also try to do clientside requests on clientside as part of https://github.com/MTRNord/matrix-connection-tester-ui (reasoning simply being that it would hopefully be a bit more realistic).

[MTRNord]

Hm, on first observation, it’s already interesting that the MSC says to use org.matrix.msc4158.rtc_foci but servers in the wild do use org.matrix.msc4143.rtc_foci instead. The "Client Discovery (.well-known/matrix/client)" section already shows it but that section currently has no mapping for the MSCs. So thats something to add.

[pReya]

Hm, on first observation, it’s already interesting that the MSC says to use org.matrix.msc4158.rtc_foci but servers in the wild do use org.matrix.msc4143.rtc_foci instead. The "Client Discovery (.well-known/matrix/client)" section already shows it but that section currently has no mapping for the MSCs. So thats something to add.

I assume that org.matrix.msc4158.rtc_foci is outdated, because the current Element Call documentation suggests to use org.matrix.msc4143.rtc_foci. But then again maybe it's the other way round?! I'm confused myself ;)

And yeah, obviously I did not suggest to check for things that require a login, because that'd open a whole other can of worms.