Open luixxiul opened 17 hours ago
Some people's clients are still using it, so keeping it around a while longer is preferable.
Keeping the role in the playbook is not too heavy of a burden, but still.. removing the role after a few months will probably be better, as it would prevent confusion.
The other unmaintained / deprecated components are somewhat different - they are unmaintained, but they still have their use and some (most) of them still work. We have no telemetry, so we don't know how many users each has, but I believe almost all deprecated components are still useful to at least a few people. It would be better if we can figure out which are broken and/or unused (how?), so we can remove dead-weight, but it's a difficult challenge.
As for sliding-sync, after Element X mobile apps (and various forks of them) stop using the old sliding-sync proxy and some time passes (so that people would upgrade/migrate away from these old versions of the apps), we can safely remove the role. I don't see what purpose and to who it might serve.
Playbook Configuration: irrelevant
Matrix Server: irrelevant
Ansible: irrelevant
Problem description:
https://matrix.org/blog/2024/11/15/this-week-in-matrix-2024-11-15/ says:
And the blog post (https://matrix.org/blog/2024/11/14/moving-to-native-sliding-sync/) says:
I am wondering what would be the future for Sliding Sync proxy role of this playbook. Will it be removed or kept in the same way as other unmaintained / deprecated components?
Additional context: