When a Space contains Sub-spaces, the room listing shouldn't show a flat list including all subspace-rooms.

mattdm commented 3 years ago

Your use case

Our Space has a lot of rooms -- there are probably going to be hundreds. In order to make that not overwhelming, I want to organize these via sub-spaces. However, the UI considers all rooms in sub-spaces to be rooms in the top-level space too. Observe:

(Please ignore visual styling ... this is a new server in progress!)

We don't even have all of our rooms configured yet, and the list is already basically useless. It's even worse on mobile.

I would really like one of:

Spaces and Rooms displayed as multi-level hierarchy replacing the > Rooms list.
Room list shows just rooms, but there's a second section > Spaces after > People and > Rooms which lists nested spaces.
Long flat list of rooms under > Rooms, but broken up into sections with Spaces serving as a section headers

The could also get sub-spaces out of the leftmost bar, allowing that to take up less space.

Have you considered any alternatives?

We could create multiple top-level spaces and not use nested spaces. This probably would be fine on our own server, but is less convenient for anyone coming in from a federated server since we'd have to send them a bunch of different space invites.

Additional context

This is really important to us; one of the chief reasons for moving to Matrix is for ease of use for new users, and this feels like an impediment to that.

mattdm commented 3 years ago

Note that moving the sub-space list to the second column would have another advantage. Notice how "Contributor Discussions" is truncated to "Contributor Discus..."?

mattdm commented 3 years ago

Here's a screenshot of the Rust Discord setup:

This is basically "option 3" of my suggested approaches above. It seems superior in a lot of ways:

"servers" or "spaces" column on the far left can be very narrow and not take up a lot of the screen.
There's a clear organization from top to bottom
Easy to hide the things you're not interested in right now (click the header to collapse)

This particular approach (as opposed to my "option 2") also has the advantage that you can still see everything at once and move easily between subspaces /sections.

mattdm commented 3 years ago

@SimonBrandner I notice you've thumbs-downed this suggestion. I'd love to hear the opposing viewpoint, and maybe we can come to something that fits better?

t3chguy commented 3 years ago

For me the Discord model doesn't work well with very large Guilds, I often find myself having to scroll the list loads to be able to find unreads/notifications as there isn't a way to sort by recency.

A similar issue would be the case if we split up the room list more than just People/Favs/Rooms because then each list would be recents-sorted but not the whole list. Another issue with this proposal is a room may exist in multiple subspaces and thus now then be shown multiple times in a single room list in multiple places, confusingly.

Twi1ightSparkle commented 3 years ago

@mattdm I'd love to hear the opposing viewpoint,

I see the use case for this, but personally I would not like it because I prefer to have my spaces collapsed and just use the space for the current situation (work for example) selected. Then browse the room list including all sub spaces like I did before spaces using keyboard shortcuts.

So an options in settings to choose would be best imo.

EDIT: having to constantly switch spaces, in addition to switching rooms, would slow down my workflow. Unless there is a new keyboard shortcut to change spaces. I'm very happy CTRL+ALT+(^|v) does not change to rooms in other spaces

Erethon commented 3 years ago

I would like to +1 what @mattdm is saying/proposing. Current implementation of spaces doesn't help with organizing my rooms in a logical manner, since top level (or higher level) spaces also include all the lower level channels. This become more evident if you have rooms in a higher level space that don't belong in any sub-space and the only view with these rooms gets "polluted" by all the rooms in all the lower level spaces.

As @Twi1ightSparkle said, I would be happy with a setting to choose between the two behaviours and I'm willing to try implementing this if: 1) We think it's something that's useful and might be merged 2) The maintainers think it's "easily" achievable, as my experience with this kind of work is minimal :)

mattdm commented 3 years ago

@Twi1ightSparkle Ah, I see. I think the primary difference is coming at this from being a heavy matrix user before spaces existed, vs. me coming into this and wanting spaces to provide a curated experience for our users (who might not be familiar with matrix at all).

I think, though, that these things could coexist? Public spaces could work like I'm suggesting, and then you could create your own private spaces with whatever arrangement you want.

mattdm commented 3 years ago

I want to note another weirdness that happens here: rooms are only considered a member of the top-level space if you've joined the subspace too. That leads to some serious cognitive weirdness. In my example at the top, is "Information" a member of the "Fedora" space? It depends.

t3chguy commented 3 years ago

That is a separate issue: https://github.com/vector-im/element-web/issues/17293

mattdm commented 3 years ago

That is a separate issue: vector-im/element-web#17293

Well, it could be a separate issue; or, this could be a solution to that issue.

t3chguy commented 3 years ago

No, it is a technical issue of not having access to the data via /sync - regardless of what the UI/UX looks like.

mattdm commented 3 years ago

But if you aren't trying to show rooms which are within subspaces as also members of the top-level space, it's irrelevant. That issue is only an issue because they're treated this way -- it's an example of the "weirdness" I mentioned.

mattdm commented 3 years ago

Oh! I have come across another situation related to this. We have one sub-space, Project Teams, which contains a fairly long list of sub-teams. In some cases, a team has more than one channel. I'd like to group those with a further sub-space -- say, for example, Infrastructure.

As it is, that grouping is helpful to the members of that subspace, because it makes it possible to drill down to just those channels. But it's less useful for people who aren't, because now all of those rooms are in their list in the Project Teams space -- not filtered at all.

MayeulC commented 2 years ago

I think that adding a way to "pin" a subspace to the spaces bar so that the parent space doesn't need to be extended to show the subspace would more or less solve this?

Alternatively, there could be some room state event suggesting a different presentation, but the client should be compatible.

emorrp1 commented 2 years ago

It feels to me that this discussion is simply a repeat of the Home discussion (#18093) just one level down. The solution should include the results of the experiment there and allow the user to select "Show all rooms" for the parent space. Or maybe even just inherit that setting globally since it seems to be a conceptual thing, so if someone has indicated they don't consider Home to be an Other category, then the same should apply to parent spaces.

@MayeulC that would be vector-im/element-meta#306 I think.

dkasak commented 2 years ago

I think this should ultimately be a per space setting. There are two modes at play here.

Spaces considered as (hierarchical) tags. If a room belongs to a space it is as if it was tagged by that space. Sub-spaces are like sub-tags. Selecting the space acts as a filter of the total collection of rooms to show all rooms tagged by that space.

This mode is especially useful for context switching, e.g. between Work and Personal.

Example: if room A is a member of the space Foo and room B is a member of the space Foo/Bar (a sub-space of Foo), both rooms are tagged by Foo, but only one is tagged by Foo/Bar.
Spaces considered as sets of rooms. A space is just a set of rooms (or other spaces). Selecting a space just shows all of its elements, which may be rooms or other spaces.

Example: room A is a member of space Foo, but so is space Bar. Space Bar also contains a room B. Selecting Foo only displays its immediate children, which are the room A and the space Bar.

Like @Twi1ightSparkle, I also primarily use my spaces for switching between contexts. When I switch to a context, I expect the space to filter down my total collection of rooms to those particular to that context. But when in that context, I expect for everything that is a descendant of that context to be visible at once and sorted by recency.

I think, though, that these things could coexist? Public spaces could work like I'm suggesting, and then you could create your own private spaces with whatever arrangement you want.

I think I like this suggestion, provided I could get the context-like behaviour I want by creating a private space and adding the public space as a sub-space.

Perhaps we should just differentiate between the two use cases on the UX level since these two use cases seem fundamentally different, even though both would be implemented using spaces. Something like "Contexts" and "Guilds" (to draw a parallel with Discord). There are other use cases I would like to see in the Context case, such as silencing notifications from non-member rooms when it is activated.

thoraj commented 2 years ago

Just to pitch in: We use Matrix in our solution Verji, and spaces is very important to us. "Room hierarchies" is a highly requested feature from our customers, and we believe that the introduction of Spaces is a game-changer. (So kudos to everyone involved in creating spaces)

However, for our customers, the current implementation where rooms from sub-spaces float up and show up in higher level spaces renders the solution practically useless.

Our preferred solution to this would be:

Make the behavior configurable per space (a room state event ?). So we could determine if a space only show immediate child-rooms, or the aggregation behavior we have today.
Keep the space hierarchy in the leftmost column. Or at least make it an option.

Flam3z commented 2 years ago

For me the Discord model doesn't work well with very large Guilds, I often find myself having to scroll the list loads to be able to find unreads/notifications as there isn't a way to sort by recency.

A similar issue would be the case if we split up the room list more than just People/Favs/Rooms because then each list would be recents-sorted but not the whole list. Another issue with this proposal is a room may exist in multiple subspaces and thus now then be shown multiple times in a single room list in multiple places, confusingly.

High Agree, When I used to use discord and finding huge, active servers It was very fustrating just to find one specific channel under the 5+ or so categories. Just to chime in with my own idea, having some sort of "folders" within the sections that give the freedom to the user of only wanting to be in and see a specific set of rooms within said space.

kfiven commented 2 years ago

+1 though I am already addicted to this behavior in Cinny client, but when switching to Element, I get lost in scroll when there are hundreds of rooms in subspaces and then the only option is to left is remembering room name and searching it.

t3chguy commented 2 years ago

Duplicate of https://github.com/vector-im/element-web/issues/17378

element-hq / element-web