Timeline for Why are we so uptight?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:32 | history | edited | CommunityBot |
replaced http://ux.stackexchange.com/ with https://ux.stackexchange.com/
|
|
| Mar 16, 2017 at 15:44 | history | edited | CommunityBot |
replaced http://meta.ux.stackexchange.com/ with https://ux.meta.stackexchange.com/
|
|
| Apr 16, 2013 at 15:27 | comment | added | Charles Wesley | While there is no requirement to comment after giving a down vote, in my opinion if you can't be bothered to explain why you're down voting then just flag or vote to close. Downvoting with no explanation reflects poorly on UX.SE as the answer above perfectly illustrates. Personally, I view casting a downvote as admitting that you failed to save the item in question. A helpful comment can either help fix the item in question, or educate the user so that they provide better content in the future. Skipping straight to the down vote is lazy. | |
| Apr 13, 2013 at 2:11 | comment | added | rk. | Personally, I try to provide a reason whenever I am the first one to flag/point out to the questioner if the question is off-topic or something. And I do agree that questions shouldn't be downvoted (ideally, for new comers atleast). | |
| Apr 13, 2013 at 1:26 | history | answered | Jeff | CC BY-SA 3.0 |