Post History
#4: Post edited
Don't downvote just because someone posted screenshot.
- I've seen comments of admitting to downvoting a post just because that poster posted screenshots.
- If someone is writing math, then they ought use MathJax, not screenshots.
But if you're quoting someone else, ESPECIALLY IF YOU ARE ALLEGING SOMEONE ELSE MADE A TYPO OR MISTAKE, then screenshots are more reliable. I want to see what that person wrote exactly, not what you transcribed that person to write.tack Exchange has too many questions when the issue is that a poster mistyped someone else's writing. If they didn't mistype, the poster wouldn't need to ask the question.
- I've seen comments of admitting to downvoting a post just because that poster posted screenshots.
- If someone is writing math, then they ought use MathJax, not screenshots.
- But if you're quoting someone else, **especially if you are alleging someone else made a typo or mistake**, then screenshots are more reliable. I want to see what that person wrote exactly, not what you transcribed that person to write.
- StackExchange has too many questions when the issue is that a poster mistyped someone else's writing. If they didn't mistype, the poster wouldn't need to ask the question.
#3: Post edited
- I've seen comments of admitting to downvoting a post just because that poster posted screenshots.
- If someone is writing math, then they ought use MathJax, not screenshots.
But if you're quoting someone else, ESPECIALLY IF YOU ARE ALLEGING SOMEONE ELSE MADE A TYPO OR MISTAKE, then screenshots are more reliable. On Stack Exchange, I've seen too many questions when the issue is that a poster mistyped someone else's writing. If they didn't mistype, the poster wouldn't need to ask the question.
- I've seen comments of admitting to downvoting a post just because that poster posted screenshots.
- If someone is writing math, then they ought use MathJax, not screenshots.
- But if you're quoting someone else, ESPECIALLY IF YOU ARE ALLEGING SOMEONE ELSE MADE A TYPO OR MISTAKE, then screenshots are more reliable. I want to see what that person wrote exactly, not what you transcribed that person to write.
- tack Exchange has too many questions when the issue is that a poster mistyped someone else's writing. If they didn't mistype, the poster wouldn't need to ask the question.
#2: Post edited
- I've seen comments of admitting to downvoting a post just because that poster posted screenshots.
- If someone is writing math, then they ought use MathJax, not screenshots.
But if you're quoting someone else, ESPECIALLY IF YOU THINK SOMEONE ELSE MADE A TYPO OR MISTAKE, then screenshots are more reliable. On Stack Exchange, I've seen too many questions when the issue is that a poster mistyped someone else's writing. If they didn't mistype, the poster wouldn't need to ask the question.
- I've seen comments of admitting to downvoting a post just because that poster posted screenshots.
- If someone is writing math, then they ought use MathJax, not screenshots.
- But if you're quoting someone else, ESPECIALLY IF YOU ARE ALLEGING SOMEONE ELSE MADE A TYPO OR MISTAKE, then screenshots are more reliable. On Stack Exchange, I've seen too many questions when the issue is that a poster mistyped someone else's writing. If they didn't mistype, the poster wouldn't need to ask the question.
#1: Initial revision
Don't downvote just because someone posted screenshot.
I've seen comments of admitting to downvoting a post just because that poster posted screenshots. If someone is writing math, then they ought use MathJax, not screenshots. But if you're quoting someone else, ESPECIALLY IF YOU THINK SOMEONE ELSE MADE A TYPO OR MISTAKE, then screenshots are more reliable. On Stack Exchange, I've seen too many questions when the issue is that a poster mistyped someone else's writing. If they didn't mistype, the poster wouldn't need to ask the question.