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.
How to Edit
- 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
How to Format
-
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>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. stack-overflow), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
@postowner
words that are now present on our network. That's a lot of pointless noise. Also note that in the latter example Jason used above, no@usernames
were required at all to get notifications as we detect when only two people are talking and auto-reply. Bottom line, unless someone explicitly indicates otherwise, comments are always directed at the post owner. That's the intent, and has always been from day one.@postowner
. There's a large number of counters to that on this page. But you continue not to address several points. 1. Even if you were right, it's wrong to push such a silly little thing in the face of this feedback. 2. That's not the only purpose of them. 3. The change is pointless, people just put@ postowner
andpostowner:
, both of which are just as noisy, but which actively mislead new users for when they do need to use@
to direct their comment. I'm sure there are more. #1 is esp. big.@user:
syntax is appropriate, except in this one case of answerer + one commenter, where the commenter can't add the "@user:" syntax but the answerer can. How is a new user, who may be familiar with Twitter and Facebook and other social media where@user
is the norm for addressing someone else, regardless of whether it has any automated effect, supposed to understand these rules?@user
syntax more than once in the comment even though I was using it in its literal and non-automatic form. You guys REALLY need to take your best shot at a simple, easy-to-understand webpage, and if you really feel the need to deny people posting a particular syntax, include a link to that webpage on the popup box so someone can actually understand what it is they're not supposed to do.