New, Improved Comments with @reply
Stack Overflow didn’t always have post comments. The first comment ever was on this post by Michael Stum, and it was posted on September 6th, 2008. There have been continuous improvements to comments since they were originally rolled out:
On top of that, the limitation on comment length was relaxed from the original 300 characters to 600 characters. There have been three additional improvements to comments recently, all by popular demand.
Hopefully you’re familiar with Markdown by now; it’s the formatting language we use for posts on Stack Overflow. Well, all that learnination has paid off: now you can use a subset of Markdown in your comments for bold, italic, and code.
*italic* _italic_ **bold** __bold__ `code` *not italic* [link text](http://example.com "link title")
The support of a minimal subset of Markdown in comments isn’t new, it’s been in for several months — but I wanted to make sure everyone was aware of it.
As frequently requested, we now allow editing of your comments for a 5 minute grace period after they are posted. Just mouse over your comment and look for the “edit” link.
A comment that has been edited will have a small pencil icon indicator; the tooltip explains what it means, and also tells you how many times the comment was edited. Once that 5 minute editing grace period is over, the comment is “locked in” and cannot be edited. If you want to change it after that, it must be deleted and resubmitted as a new comment.
Comment @username Notifications
Normally, you only get notified of comments when you own the post that is being commented on. But now you will also get notified of any comments that refer to you by @username, even if you don’t own the underlying post. This implementation is inspired by the way Twitter handles @username mentions — although we have the additional rather severe restriction that in our system, user names are not guaranteed to be unique.
In the above example, Anthony Jones will get notified that Bruno Conde has replied to his comment. (writing out the entire username wasn’t entirely required, as will be explained shortly)
There are some rules, of course:
This only works when referring to other people who have already commented (or have edited the post).
Your comment must include @username that you are referring to, where “username” is a reasonable match to the user’s current display name (as seen in the comments above yours).
There must be a starts-with, case insensitive match of at least THREE characters to the displayname. So @a and @ab will never match anyone or anything.
Spaces are ignored in the match, so if the person’s display name is “Peter Smith” then just use @peter to match, or @petersmith.
Matching is performed in reverse chronological order, so if there are five people named “John” in the comments, writing “hey @john, have you considered apples?” will match the most recent John to comment.
Only one person can be replied to at a time in a comment. The first one in the string wins.
- Users who have no display name set, whose faux-displayname is derived from their OpenID URL, cannot be matched.
Question and answer owners were always notified when there were new comments on their posts, so there’s no need to address the post owner by @name when commenting. Remember, the intent of this feature is to let other users participating in the comments know that you’ve replied to them.
Now, we don’t want Stack Overflow to turn into a social networking site for chatty cathys, so there’s only so far we will go in supporting pure conversation. We may be tweaking the behavior a bit over the next day or two, but but this seems like a reasonable compromise.
Thanks for reminding me of this. Blog commenting is sure a powerful SEO tool. I sincerely hope it helps as described in your newsletter.