So apparently there's a feature (undocumented or otherwise) that allows you to ping people based on the first three letters of their name. I guess I can sort of see what went through its developer's mind but it causes a problem.
My name is Oli. It's short for Oliver. In the Ask Ubuntu chat room, we've recently had three people who match the @Oli ping, me and two with longer names that start "Oli". There are hundreds of people like this in the network.
So when somebody talks to me, they get pinged too. I'm a moderator so people talk to me quite a lot. That means it's got to be pretty hellish if your nick starts with "oli". You're getting loads of pings that aren't actually for you.
In reflection (given that there's tab completion), this is a stupid feature.
It should be taken out back and shot.
This appears to have come up a couple of years ago and got a slight fix but has that since regressed? Today an Oliver was getting pings for me so the full-word-match thing advertised in the answers isn't catching any more.
And in terms of making tab-completion a viable option (not all people know about it, not all people have tab keys, eg phones), how about that if you write a possibly ambiguous @name:
- It works out who based on who's chatting, and/or
- Offers the user an option for each ambiguous @name used so only the correct people are ever pinged. Or something similar as the username is tapped in...
@Oli
. There is no difference, Oliver and Olivier will get pinged when someone auto-completes your name using <TAB> too.@Oli
because you can just Tab to his full name, so the reason the feature was there is now moot.@Oli
.@Jon
go to Jon Clements and Jonston and Jones, as well as a user named Jon. It should use the same rules as for comments: the most recently active match should be pinged (with a preference for a full match perhaps).