search

element-hq / element-meta

Shared/meta documentation and project artefacts for Element clients
74 stars 12 forks source link

Threads shouldn't count towards unread for rooms, at least optionally #2473

Open gnurbs opened 3 months ago

gnurbs commented 3 months ago

Your use case

Current behaviour

When someone else posts a new message to a thread in a room, that room gets marked unread currently.

Wanted behaviour

Either: threaded message comes in -> unread status of room is not affected (changed behaviour), but unread status of thread is updated (current behaviour)

Or (probably nicer solution): Threads I participate in plus threads I mark as notifying change unread status of room

Reasoning / background

Threads are used to structure conversations but at the same time many (most?) topics are not important / interesting to most participant in a room. This is actually a reason to use threads: to not bother everyone in a room with a specific topic

But due to the room getting unread, this is not possible: I notice that eg five of my rooms are unread. I then click through them, need to check the last message, notice that I've already read it, need to understand that it's due to a message in a thread, need to right-click the room -> mark read. Repeat four times.
So not bothering people with a topic is not achievable. And to me personally I have the feeling it would bother me less if I'd need to skim the last couple of messages to recognise a room is still about a topic I'm not participating in then the status quo. The current behaviour makes me a little anxious to be honest.

Etc

I wasn't able to find an existing issue on this, but I guess this has been reported already. If so, sorry for that, please point me to the issue.

Have you considered any alternatives?

No response

Additional context

No response

dbkr commented 3 months ago

This doesn't sound right: as it stands currently, an unread threads should either cause the thread to appear in the TAC or nothing, depending on settings. It shouldn't ever cause the room itself to be unread.

gnurbs commented 3 months ago

Looks like my server's element-web version is a tad old: 1.11.65 from april. From the changelog there were changes around TAC (Thread activity centre, right?) especially in 1.11.66, would you expect this particular behaviour to have changed from that version?