Skip to content
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

Be consistent with "Direct chat" or "People" vocabulary #1262

Open
gagarine opened this issue Oct 2, 2017 · 8 comments
Open

Be consistent with "Direct chat" or "People" vocabulary #1262

gagarine opened this issue Oct 2, 2017 · 8 comments
Labels
A-DMs O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect X-Needs-Product More input needed from the Product team z-Content

Comments

@gagarine
Copy link

gagarine commented Oct 2, 2017

Description

On the menu you can set a room to be a "direct chat". But the side bar is using "People".

Keeping the same vocabulary would make it simpler to understand.

"Peoples"
screen shot 2017-10-02 at 13 39 37

"Direct chat"
screen shot 2017-10-02 at 13 27 01

In fact "direct chat" are a "1-to-1 room" but this room is not limited to only two account as we can add bot or alternate account. This need to be clearer.

Version information

  • OS: MacOS
  • Version: Version 0.12.4 (0.12.4)
@lampholder
Copy link
Member

Consistency ftw (though I think this does require some thought before converging on a single term).

@lampholder lampholder added T-Defect S-Minor Impairs non-critical functionality or suitable workarounds exist P2 labels Oct 4, 2017
@lampholder
Copy link
Member

Back here due to @ara4n's filing of the duplicate element-hq/element-web#5782:

image

I considered this for a while, and concluded that there is no wholly nice, small fix we can do without considering the problem of direct messages more generally.

I'm not a fan of the 'move to' semantics, esp. when they won't move anywhere if they're also a favourite/low priority.

How weird would this be?

image

There's a lot still wrong with the UX, but it maintains the consistency with 'Favourite' and 'Low Priority' and dodges any potentially misleading 'Move to' ideas.

@gagarine
Copy link
Author

gagarine commented Dec 9, 2017

I think "Direct Chat" or "Direct message" is what peoples are used too for more than 20-30 years...

Perhaps, what is strange in riot is that you can mark (or move) a room a "direct chat". I'm not sure about this features for the end-user.

In Discord you can also invite someone in a DM or in slack you can have bot in a DM... but DM stay DM and room/channel stay room/channel.

@astrojuanlu
Copy link

Anecdotal data point: I came here looking for an explanation of the "Direct chat" thing because it's confusing as well, since I had a "direct chat" with three people and one bot... If you ask me, this should be automatic (i.e. if there are more than two users, it's not a "direct chat" anymore).

@t3chguy
Copy link
Member

t3chguy commented Jul 23, 2020

We still have this issue, User Info says Direct message (verb)
Room list calls them People

@turt2live
Copy link
Member

This got iterated on sometime during the rebrand: The early room list called it Direct Chats but somewhere we reverted and I'm not sure why/where.

@t3chguy
Copy link
Member

t3chguy commented Jul 23, 2020

Cool, going to throw it into the pile then

@turt2live
Copy link
Member

turt2live commented May 7, 2022

ftr, we now have:

  • People
  • Chat
  • Message
  • Direct Chat
  • Direct Message

we seem to be getting worse.

@SimonBrandner SimonBrandner added O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience and removed P2 labels May 7, 2022
@turt2live turt2live changed the title Be consistant with "Direct chat" or "People" vocabulary Be consistent with "Direct chat" or "People" vocabulary May 30, 2022
@kittykat kittykat added X-Needs-Product More input needed from the Product team and removed X-Needs-Design labels Jul 4, 2022
@t3chguy t3chguy transferred this issue from element-hq/element-web Mar 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-DMs O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect X-Needs-Product More input needed from the Product team z-Content
Projects
None yet
Development

No branches or pull requests

9 participants