Timeline for Should I downvote a question because I think it is beckoning trouble?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 12, 2020 at 13:47 | history | edited | CommunityBot |
Commonmark migration
|
|
| Mar 20, 2017 at 10:32 | history | edited | CommunityBot |
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
|
|
| Feb 7, 2017 at 8:26 | comment | added | user477799 | That's a nice theory. Too bad it isn't the case. See this, for an example: superuser.com/q/1176075/477799 | |
| Feb 7, 2017 at 8:14 | comment | added | Journeyman Geek Mod | Downvotes arn't mean. Downvotes are the clean me scratched in the dusty car of a question. Personally most questions I find bad enough to downvote, I find bad enough to closevote or at least comment so op learns. If I get one, the kindest thing one can do is comment and let me know why so I can do better. | |
| Feb 7, 2017 at 8:08 | comment | added | user477799 | First, it is not an XY problem; it is an extension of the famous "what if I press this button?" case, i.e. the OP doesn't have problem, but the thrill of doing this certain thing has taken him. Second, forget the great scheme of things; a downvote has no value whatsoever. It is never helpful. It is a mean thing that we do to each other and I want to learn the rules of it. | |
| Feb 6, 2017 at 14:09 | history | answered | Journeyman GeekMod | CC BY-SA 3.0 |