4 ms·
Another idea would be to switch from the positive incentives of karma, to a harsher negative incentive system. So if your karma is good, it is always 0. If yo
by Sakes 15y ago
Another idea would be to switch from the positive incentives of karma, to a harsher negative incentive system. So if your karma is good, it is always 0. If you make bad comments and get down voted, it begins to go negative. You can reach zero again by making better comments later, but you can't stock pile points. Zero is as high as you can go.
I still think the perceived reward of having high ranking comments has to be removed somehow.
What do you think bruce?
- mattgreenrocks 15y agoI like this a lot. Karma should be displayed to the logged in user in a vague fashion: "Karma: good." The numeric score can be maintained on the server, but never displayed to the user. Downvotes and other abilities would simply show up one day when you've passed a certain threshold, but the user should have no idea how far along they are, as we're trying to dissuade the people that want those sorts of powers (and would abuse them) from getting them. Meanwhile, negative karma could start rate-limiting you past a certain point, such as only allowing 3 posts/day. I'm still of the belief that the only way to ensure high quality discussion is to discourage commenting for it's own sake. Everybody does not need to contribute to every article, and having a numeric karma score only legitimizes posting for its own sake. To reiterate my support for a previous point: the only way to fix the karma system is to kill the ego's involvement in it.
- bruce511 15y agoI suspect any system can be gamed for some reason or other. Equally, I suspect that making ever more complicated systems, to handle ever fewer edge cases, results in the system being less useful, not more. Simple systems, like the current karma system, can certainly be gamed, but with each iteration general value is lost. Displaying comment scores (which I prefer) can be abused. So that's gone, and a data point with it. Keep them, don't keep them, I don't think I'll lose much sleep either way. But as a general rule, removing data or functionality from the many, to try and prevent the excesses of the few always invokes the ire of unit ended consequences. It's almost never an improvement.