Page MenuHomePhabricator

conpherence makes it hard to see all active conversations
Closed, InvalidPublic

Description

From one of my users:

i tend to have a bunch of conpherence threads going at once.

on the conpherence page it lists them on the left. at first it shows only the first few (i see 5 under "Messages", not sure how "Rooms" work).

to see the rest I have to click "See More".

there's plenty of room for the whole list and it doesn't even put recent conversations at the top.

seems like it would be better to show all with a scrollbar or at least put the recently active threads on top.

Event Timeline

sshannin raised the priority of this task from to Needs Triage.
sshannin updated the task description. (Show Details)
sshannin added a project: Conpherence.
sshannin added a subscriber: sshannin.
btrahan claimed this task.
btrahan added subscribers: chad, btrahan.

This is again by design. @chad - please note this task.

it doesn't even put recent conversations at the top

There is a "rooms" section first, and then the "messages" second. Both are the ~5 most recent, with the "~" being if you are particularly heavy on interacting with either rooms or messages we don't necessarily get the full 5.

If you disagree that this is how it works, please re-open with reproduction instructions that make recent conversation not show up top.

See also T7589, which for the durable column plans to improve the recent room / messages switcher.

Thanks for the feedback.

I will report back if the ordering complaint is actually reproducible.

I've changed the initial show limit of 5 locally in my install. In case anybody else wants to do this, I just adjusted SEE_MORE_LIMIT at the top of src/applications/conpherence/view/ConpherenceThreadListView.php

Just filed T8488 which may make this better.

there's plenty of room for the whole list

What is the ballpark expectation on number of items in the whole list?

Well, for this guy I suspect it's like 20 (which is what I ended up settings ours to). Certainly for me I have more than 5 active-ish.

I think the main reason he's complaining is that there doesn't seem to be any reason to hide the other convo's behind the See More, it just keeps a big column of empty space below it.

Also, update on the ordering:
It looks like even selecting a message throws it to the top of the ordering on a refresh. Like if you click on some old convo just to read a past message there and then refresh, the old convo is now at the top of the list, even though the convo may not have had any activity for days. I think that's a bit weird/unexpected?

Can you take a step back and explain a bit more how you and your team is using Conpherence? Basically, I'm trying to understand how come there are so many active threads at once for an individual and what the nature of these threads is...?

On a page load, the active thread is at the top. As you guessed, this is to solve the corner case of looking at a conversation outside the latest N, and then its on any load to try to eke out just a little consistency. In actual usage I am aware of this works pretty well; you want to have the (old) thread you selected in that list on the left in some fashion and giving you are actively looking at it at the top of the list is not too off expectations.

T8488 still the right place to follow for changes here. I think until rooms vs messages dissolve a bit that column is as good as its going to be. I think T7589 is also likely useful for you and your team as the durable column should get better about really showing the latest N with live updates, etc.

(If its not obvious, this is under active development and even what the product is going to be is still in flux. Thanks for providing as much context as you possible can at all times on your usage of the product; much, much more useful than specific product change suggestions.)

I told my team to evaluate conpherence as a replacement for hipchat/internal xmpp. So just a generic IM system but more integrated with development process.

And yes, I'm aware it's under active development : )

It's not always clear to me when things are by design (like this) or are bugs (like T8489). Sometimes I assume wrong and am probably too terse in explaining what I think is off, so apologies for that.