When I press "@" in a channel, I get a list of people in the order they have most recently talked. This is a pretty good default behavior.
Problems start when I type more letters after that.
I recently found myself in a channel with someone whose visible name is "Tim" and username is "@Irwing#3762", who I was trying to reply to something they had said a few screens up the scrollback buffer. I typed "@Tim blah blah" and hit enter... and produced a message that tagged @Tim#2129 and displayed as "@dudebro420". I cannot think of a use case where this is desirable. I would have to go out of my way to find out that dudebro420's username is @Tim#2129; I will pretty much never want to tag him by typing @Tim. I would type @dudebro420 (or @du, but that's another problem covered later in this post). The prioritization here should be by display name, not username.
Then come partial names. Not only for @Tim, but "Tim"(@Irwing#3762) should be the first/default autocomplete for @T and @Ti in a channel where he's the most recent person talking that matches those things. But instead @T gets me a list of a seemingly random selection of people whose usernames start with T, some of whom aren't even in the channel. The person I'm looking for isn't even on the list. @Ti gets me a couple of people in the channel, and a couple of people with display name "Tim" and a few people with username @Tim*.... but none of them are the active-in-the-channel "Tim" (@Irwing#3762) that I'm looking for.
This behavior seems like it could be greatly improved by prioritizing active people, people in the channel, and people sorted by display name instead of username.
Please sign in to leave a comment.