Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 155 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

@username auto-completion for comments was recently implemented, and is already active on MSO.

However, it only seems to auto-complete the usernames of people who have commented on the post. According to this topic, the list of users who can be explicitly notified also includes:

  • Anyone who edited the post
  • Anyone who started a bounty on the question
  • The ♦ moderator or dupehammer holder who cast a binding close vote on the question

Why not auto-complete those, as well?

share|improve this question
The post author will always be notified, so it's a waste of your one @reply to include them. – Bill the Lizard Sep 17 '11 at 14:24
@balpha bit late, but care to explain please why you declined this? – Shadow Wizard Oct 7 '15 at 12:13
@ShadowWizard Tim's answer mostly covers that. – balpha Oct 7 '15 at 12:20
up vote 10 down vote accepted

Since @notify-ing post authors is actively discouraged, and adding all editors would introduce complexity for an uncommon use case, it's unlikely that the tab completion will be expanded to include those options. Note however that the tab completion will already include the post author in the list of names in cases where that user has commented on the post, and there is at least one other comment posted by a third user.

That said, completion of the most recent editor and moderator responsible for a close vote wouldn't be too difficult to implement with something like the following, based on the minified code:

var t = o.closest("#question, .answer")
    .find(".post-signature .user-details a[href^='/users/']");
var s = l(t.last().attr('href'));

var editor = t.first();
var moderator = o.closest('#question').
    .next('.question-status').find('a:last + .mod-flair').prev('a');

o.find("a.comment-user").add(editor).add(moderator).each( // ...

(Note: the existing code takes care of the "is not me, is not post author" issues later)

Still, since these aren't very common usages of @notify-cation (and there's a bit of an edge case with finding the closing moderator), I could see why the lack of a compelling reason to add them would keep it from happening.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .