I can remove this reason, but currently this reason does not effect user reputation and only effects the placement of the content from the source the vote was placed from. If someone was to down vote the content because they don't understand it and therefore don't want to see it on the front page, they would simply choose another reason to do so, which would then have an effect on member reputation. It's a tough call, what do you think? We are always wiling to make adjustments to our approach if the ideas behind it are sensible.
My issue is with the mixed signals this sends. We have a culture of not downvoting because we don't like or we disagree. And people listen to that.
We downvote on spam and hate and things that ought not to be on snapzu.
And then you tell people to downvote things if they aren't in English. And once again people listen. If it's part of the menu then it's what I ought to do, right? It moves us towards a casual downvote culture like reddit's.
Ideally we'd have a "hide" option to mask things we don't want to see without downvoting but even without it I think we'd be better off removing the option from the menu.
As mentioned above, would it be difficult to implement a temporary solution to have a checkbox which says "Don't post to front page?" and filter those posts from the fp of all users? That way the snap only shows up in the tribes it was posted to and doesn't run into people on the front page downvoting it for language reasons.
Another option would be to just include Front Page as a default tribe new snaps are posted to, and give the ability to remove it. Make it a free tribe posting which doesn't affect the current default of 3 tribes.
The solution we are working towards needs to be easy enough to quickly implement but at the same time needs to be intuitive, users need to understand right away what the functionality is for without having to go read a manual to understand its context. Again, we are going to discuss this at length and work on creating a low impact intuitive solution to allowing members to post multiple language content without the worry of filling the front page with content from every language imaginable.
Can you at a minimum remove not being in English as a reason to downvote?
I can remove this reason, but currently this reason does not effect user reputation and only effects the placement of the content from the source the vote was placed from. If someone was to down vote the content because they don't understand it and therefore don't want to see it on the front page, they would simply choose another reason to do so, which would then have an effect on member reputation. It's a tough call, what do you think? We are always wiling to make adjustments to our approach if the ideas behind it are sensible.
My issue is with the mixed signals this sends. We have a culture of not downvoting because we don't like or we disagree. And people listen to that.
We downvote on spam and hate and things that ought not to be on snapzu.
And then you tell people to downvote things if they aren't in English. And once again people listen. If it's part of the menu then it's what I ought to do, right? It moves us towards a casual downvote culture like reddit's.
Ideally we'd have a "hide" option to mask things we don't want to see without downvoting but even without it I think we'd be better off removing the option from the menu.
As mentioned above, would it be difficult to implement a temporary solution to have a checkbox which says "Don't post to front page?" and filter those posts from the fp of all users? That way the snap only shows up in the tribes it was posted to and doesn't run into people on the front page downvoting it for language reasons.
Another option would be to just include Front Page as a default tribe new snaps are posted to, and give the ability to remove it. Make it a free tribe posting which doesn't affect the current default of 3 tribes.
The solution we are working towards needs to be easy enough to quickly implement but at the same time needs to be intuitive, users need to understand right away what the functionality is for without having to go read a manual to understand its context. Again, we are going to discuss this at length and work on creating a low impact intuitive solution to allowing members to post multiple language content without the worry of filling the front page with content from every language imaginable.