-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
only show spaces sidebar if more than one space is used by user #24714
Comments
Duplicate of #18898 |
@t3chguy i think this is not a duplicate as #18898 aims to allow users to close the spaces bar if they so choose, but i'm suggesting to completely disable it (and also the Home view) as long as a user has no access to more than one space. please reopen it or give a different (or more detailed :) ) justification. im a newbie, thanks for the patience 0:) |
@dukepeet #18898 tracks all variations of "Not everyone needs a space panel" - even if you have 1 space, + Home, you need a way to change between them.
This isn't the case, Home (with all rooms not enabled) will sow rooms which are not in that 1 space you are in. I suggest adding your opinion to the meta issue which will be used by product & design to derive a solution from. |
@t3chguy thanks, it's not clear from the description that
so i'd suggest then changing that or phrasing it differently (especially the title! i like yours much better, you could create a meta-issue with that title and reference the current open one, if you don't want to override that) or only tracking comments that are relevant to that bug and not changing the scope midway through the discussion, as this only occurred to me by reading through dozens of comments. fwiw
is fair but that does not warrant the need for a sidebar. however,
would be a different use case to what i suggested; mine is about cases when only a single space is used without any rooms that'd belong to a different space. hence my argument that in this case, even the home view is unnecessary. all in all i think i still consider my argument on this not being a duplicate valid :) thanks for the quick and useful feedback though, i appreciate that a lot! :) |
I suggest opening an issue in https://github.com/vector-im/element-meta/ if you feel like this is a case that should get special support by Element |
@t3chguy why is that a more suitable place? :) |
Because whether the Element clients give special treatment to users in exactly 1 space with 0 orphaned rooms should be considered cross-platform |
thanks, opened element-hq/element-meta#1098 |
Your use case
What would you like to do?
i'd like to not see the spaces sidebar and the Home "space" if i'm only using a single space. (if i start a private chat with someone from a different space, without joining the space itself, which i heard is possible, that would count as using multiple spaces already, in this context.)
Why would you like to do it?
it makes no difference to have a Home "space" in addition to the space itself, if multiple spaces are not in use.
it gives rise to possible confusion when people click a notification and it takes them through the levels of element/home > space > room [> thread], and when they want to quit, they feel like they have to quit the same space twice. i guess similar issues are possible which are only relevant in this context.
altogether, the Home "space" is practically useless in this case, which in turn should render the spaces sidebar useless as well. (the "add space" and "browse spaces" options could be available through the profile menu or something similar.)
How would you like to achieve it?
i'd like to automatically disable the spaces sidebar and the Home space until i start using multiple spaces.
Have you considered any alternatives?
i've considered Slack as an alternative :D as they do it roughly the way i described, and my use case seems to be no different across the two apps. now my mind is too narrowed to be able to think of other ways or use cases, sorry :)
Additional context
No response
The text was updated successfully, but these errors were encountered: