Closed kittykat closed 10 months ago
t3chguy
commented
10 months ago This setting would need to be set to the same default across all clients to not make a really confusing experience where one client says its off (unset) but another says its on (unset) - why not just change it on their deployment via config.json or in their rooms via state events?
daniellekirkwood
commented
10 months ago Agreed, for this season we probably wouldn't want to change this default (as to needing to do that cross-platform and knowing the larger impact longer-term is currently unknown). But if there's a config switch as @t3chguy suggests, that feels like it covers this case well enough
t3chguy
commented
10 months ago https://web-docs.element.dev/Element%20Web/config.html#default-settings
Closing in favour of configuration
Your use case
What would you like to do?
As a user in busy public rooms with 100s or 1000s of people joining over 2 days, I don't want to see join and leave messages in the timeline
Why would you like to do it?
Having a timeline that looks like this is not ideal (note that while we're not in conference season, those messages are spread over a few days):
How would you like to achieve it?
In settings, make "Show join/leave messages (invites/kicks/bans unaffected)" to off by default.
Have you considered any alternatives?
We can patch the FOSDEM app downstream