Open danxuliu opened 1 month ago
so in case a bad request is returned the federated server can know that the remote server is not Talk >= 20
We are fetching capabilities and could check for federation-v2?
In this regard, should federation-v2 be a local feature in the capabilities? https://github.com/nextcloud/spreed/blob/361a3fa2d8a6a3a172593dc6da1c20d0e64b5e0b/lib/Capabilities.php#L107
Currently it is not and when a room on 20 is added to 19, I get federation-v2 in the room capabilities.
Arg, basically all federation-v* will have to be?
I think it depends a bit on the feature. If we will ever have a feature that only the remote server needs to support (and the clients), that would also be fine to have non-local? For federation-v2
I think it should be a local one, as we need local server support for calling.
I have been thinking about this a bit. The federation-v2
capability is a bit problematic, because we need to check both sides on the clients. It needs to be checked locally, that our server supports calling, but also remotely, that the remote server supports calling. We currently don't have a way of specifying that we need to check both sides. So, should this be purely decided in the clients? Or do we need an additional REMOTE_FEATURES
array or something?
How to use GitHub
From #12604