Edit - Meta Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Rev

I've made a small correction to the timeline regarding the introduction of post-author notifications - they've been around longer than anything else, since comments were originally intended primarily as a way to communicate with the post author. The recent change to notifications is somewhat more subtle, but as you noted does help to explain the logic behind the redundant @ rules. See here for another overview of how messaging has changed over time.
– Shog9
Commented Jul 22, 2011 at 7:08
@Shog9, thanks, I did attempt to look up some of the oldest feature requests, but either they're not there, my search-fu is bad, or I gave up too quickly... :)
– Benjol
Commented Jul 22, 2011 at 10:39

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »