element-hq
Should Element Clients respect room tags for lists and filters?
Your use case
What would you like to do?
Discuss: "Should Element Clients respect room tags for lists and filters"
In this message we discussed how EX treats DMs and how different it is from Web. (There's a larger issue here and we should discuss how to align DMs across platforms). For now, let's figure out how/if our clients should respect room tags EG: If a user tags a room as people, does it show up in the People list/filter in our clients regardless of how many users are in that room. Today the answer is:
- Yes on Web
- No on Android
This is confusing and makes us appear buggy to end users.
Why would you like to do it?
Aligning the platforms increases the appearance of cohesion and quality in our product suite.
How would you like to achieve it?
Personally I think the clients should listen to the user's tags and move roos between lists/filters as told. This is the correct implementation of the Spec.
We need to consider the impact of canonical DMs on this however, I still believe that while canonical DMs allows us to make smart choices on behalf of the user, if they explicitly tell us that they want a room to appear in the people list, we should allow that. I support not being able to do that from the Mobile interface (and maybe one day we'll remove it from Web) but it's still something offered on other clients.
Have you considered any alternatives?
No response
Additional context
No response
@amshakal , @manuroe , @langleyd
I'd love your thoughts on this - maybe we wait until Andreas is up and running before discussing it in detail though.
It might be worth checking with the SCT if choosing to not support non-optional parts of the spec has any issues, like would we no longer be featured on https://matrix.org/ecosystem/clients/ for example
I personally think it's weird to provide this option, and don't understand the value of it. But yes, we should be consistent across all platfroms so we should decide what we want to do.
