One of the oddities of the EA forum is people voting disagree on posts like this… I can understand downvoting if you thought it was a bad change (though this seems a bit mean-spirited to me), but it seems hard to imagine thinking that the core point of the post is false!
When announced, the function of the agree/disagree axis was somewhat generically stated as “whether you agree with the contents of the comment.” That’s broader than just the truth value of the explicitly stated propositions.
For a post that announces an organizational decision, using the axis to communicate agreement/disagreement with the decision being communicated strikes me as an appropriate use. Such posts uinclude an implied claim that on net, this is a good decision. Otherwise, the axis has no value for a post like this.
(I have no votes of any sort on the top-level post.)
I think it’s better to try to keep the upvote/downvote and agree/disagree axis more distinct—to express normative vs positive evaluation. So in this case I would think that downvoting would be the natural way to express disapproval.
I think a downvote-as-disapproval wouldn’t work in this case, I would want to use upvote+disagree to express “this is an important change that the community should know about, but I disagree with the decision”. A downvote de facto communicates “I don’t want people to read this post”.
i upvoted the post and disagreed based on @Jason’s reasoning below. I agree with @Larks that’s not technically correct but still feel ok about doing the opposite of what he suggested.
The post is great so it feels wrong to karma downvote it that’s for sure.
Thanks for the update Aaron!
One of the oddities of the EA forum is people voting disagree on posts like this… I can understand downvoting if you thought it was a bad change (though this seems a bit mean-spirited to me), but it seems hard to imagine thinking that the core point of the post is false!
When announced, the function of the agree/disagree axis was somewhat generically stated as “whether you agree with the contents of the comment.” That’s broader than just the truth value of the explicitly stated propositions.
For a post that announces an organizational decision, using the axis to communicate agreement/disagreement with the decision being communicated strikes me as an appropriate use. Such posts uinclude an implied claim that on net, this is a good decision. Otherwise, the axis has no value for a post like this.
(I have no votes of any sort on the top-level post.)
I think it’s better to try to keep the upvote/downvote and agree/disagree axis more distinct—to express normative vs positive evaluation. So in this case I would think that downvoting would be the natural way to express disapproval.
I think a downvote-as-disapproval wouldn’t work in this case, I would want to use upvote+disagree to express “this is an important change that the community should know about, but I disagree with the decision”. A downvote de facto communicates “I don’t want people to read this post”.
i upvoted the post and disagreed based on @Jason’s reasoning below. I agree with @Larks that’s not technically correct but still feel ok about doing the opposite of what he suggested.
The post is great so it feels wrong to karma downvote it that’s for sure.
The core point of the post is, in fact, true! (And all the other points, to the best of my knowledge.)
I always appreciate you pointing this out.
I don’t point this out very often, so it seems pretty plausible that you might always appreciate it, so I will agree-vote your comment!