Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
why should anyone downvote a community proposal, like this post? Because they think it's a flawed proposal. That really should have been obvious. In the particular case you cite, note that you go...
Answer
#3: Post edited
by
Olin Lathrop
·
2020-08-31T19:31:51Z (over 3 years ago)
- <blockquote> why should anyone downvote a community proposal, like this post?</blockquote>
- Because they think it's a flawed proposal. That really should have been obvious.
- In the particular case you cite, note that you got many responses disagreeing with lumping physics and math together. I didn't vote at all, but if I really cared about a math or physics site, I probably would have downvoted too.
- Part of it may also have been frustration with your attitude. When people disagree, you basically repeat the same arguments. While there is nothing wrong with sticking to your original opinion, you seem unable to recognize that others disagree without being stupid. Your post here is another example of that.
- <blockquote>why should anyone downvote a bug report, like this post?</blockquote>
- That is less clear. I also didn't vote on that post. The downvote may be because someone thinks the issue is poorly described, or that you haven't been very helpful in responding to the devs and helping them track down the problem. Perhaps people are using votes on bug reports to give them a relative sense of priority.
- It would probably be helpful if there was site-wide guidance of how voting on bug reports should be used.
- <hr>
- <blockquote>In my opinion, people should only upvote site proposals they want to contribute to</blockquote>
- Yes, it is clear that is your opinion. My opinion, and apparently those of some others differ. Personally I think a combined math and physics site is a bad idea because it would get in the way of real math and physics sites. I'd rather there not be a math+physics site, even if it takes longer to get both math and physics sites.
Now that I to write this down (the rubber duck effect), I'm realizing I really should downvote the math+physics proposal. I'll go to that now.
- <blockquote> why should anyone downvote a community proposal, like this post?</blockquote>
- Because they think it's a flawed proposal. That really should have been obvious.
- In the particular case you cite, note that you got many responses disagreeing with lumping physics and math together. I didn't vote at all, but if I really cared about a math or physics site, I probably would have downvoted too.
- Part of it may also have been frustration with your attitude. When people disagree, you basically repeat the same arguments. While there is nothing wrong with sticking to your original opinion, you seem unable to recognize that others disagree without being stupid. Your post here is another example of that.
- <blockquote>why should anyone downvote a bug report, like this post?</blockquote>
- That is less clear. I also didn't vote on that post. The downvote may be because someone thinks the issue is poorly described, or that you haven't been very helpful in responding to the devs and helping them track down the problem. Perhaps people are using votes on bug reports to give them a relative sense of priority.
- It would probably be helpful if there was site-wide guidance of how voting on bug reports should be used.
- <hr>
- <blockquote>In my opinion, people should only upvote site proposals they want to contribute to</blockquote>
- Yes, it is clear that is your opinion. My opinion, and apparently those of some others differ. Personally I think a combined math and physics site is a bad idea because it would get in the way of real math and physics sites. I'd rather there not be a math+physics site, even if it takes longer to get both math and physics sites.
- Now that I to wrote this down (the rubber duck effect), I'm realizing I really should downvote the math+physics proposal. I'll go do that now.
#2: Post edited
by
Olin Lathrop
·
2020-08-31T19:23:59Z (over 3 years ago)
- <blockquote> why should anyone downvote a community proposal, like this post?</blockquote>
- Because they think it's a flawed proposal. That really should have been obvious.
- In the particular case you cite, note that you got many responses disagreeing with lumping physics and math together. I didn't vote at all, but if I really cared about a math or physics site, I probably would have downvoted too.
- Part of it may also have been frustration with your attitude. When people disagree, you basically repeat the same arguments. While there is nothing wrong with sticking to your original opinion, you seem unable to recognize that others disagree without being stupid. Your post here is another example of that.
- <blockquote>why should anyone downvote a bug report, like this post?</blockquote>
- That is less clear. I also didn't vote on that post. The downvote may be because someone thinks the issue is poorly described, or that you haven't been very helpful in responding to the devs and helping them track down the problem. Perhaps people are using votes on bug reports to give them a relative sense of priority.
It would probably be helpful if there was site-wide guidance of how voting on bug reports should be used.
- <blockquote> why should anyone downvote a community proposal, like this post?</blockquote>
- Because they think it's a flawed proposal. That really should have been obvious.
- In the particular case you cite, note that you got many responses disagreeing with lumping physics and math together. I didn't vote at all, but if I really cared about a math or physics site, I probably would have downvoted too.
- Part of it may also have been frustration with your attitude. When people disagree, you basically repeat the same arguments. While there is nothing wrong with sticking to your original opinion, you seem unable to recognize that others disagree without being stupid. Your post here is another example of that.
- <blockquote>why should anyone downvote a bug report, like this post?</blockquote>
- That is less clear. I also didn't vote on that post. The downvote may be because someone thinks the issue is poorly described, or that you haven't been very helpful in responding to the devs and helping them track down the problem. Perhaps people are using votes on bug reports to give them a relative sense of priority.
- It would probably be helpful if there was site-wide guidance of how voting on bug reports should be used.
- <hr>
- <blockquote>In my opinion, people should only upvote site proposals they want to contribute to</blockquote>
- Yes, it is clear that is your opinion. My opinion, and apparently those of some others differ. Personally I think a combined math and physics site is a bad idea because it would get in the way of real math and physics sites. I'd rather there not be a math+physics site, even if it takes longer to get both math and physics sites.
- Now that I to write this down (the rubber duck effect), I'm realizing I really should downvote the math+physics proposal. I'll go to that now.
#1: Initial revision
by
Olin Lathrop
·
2020-08-31T13:17:47Z (over 3 years ago)
<blockquote> why should anyone downvote a community proposal, like this post?</blockquote> Because they think it's a flawed proposal. That really should have been obvious. In the particular case you cite, note that you got many responses disagreeing with lumping physics and math together. I didn't vote at all, but if I really cared about a math or physics site, I probably would have downvoted too. Part of it may also have been frustration with your attitude. When people disagree, you basically repeat the same arguments. While there is nothing wrong with sticking to your original opinion, you seem unable to recognize that others disagree without being stupid. Your post here is another example of that. <blockquote>why should anyone downvote a bug report, like this post?</blockquote> That is less clear. I also didn't vote on that post. The downvote may be because someone thinks the issue is poorly described, or that you haven't been very helpful in responding to the devs and helping them track down the problem. Perhaps people are using votes on bug reports to give them a relative sense of priority. It would probably be helpful if there was site-wide guidance of how voting on bug reports should be used.