Update: This has now been pushed to the live site. For now, on Desktop, strong upvotes require click-and-hold. Mobile users just tap multiple times. This is most likely a temporary solution as we get some feedback about how the respective modes work under realistic conditions.
Over on our dev-site, lessestwrong.com, we have a fairly major feature-branch: Recalibrated voting power, and Strong Upvotes/Downvotes.
tl;dr – Normal votes on the test server range in power from 1 to 3 (depending on your karma). You have the option of holding down the up/downvote button for a strong vote, which ranges in power from 1 to 15.
We're looking for feedback on the UI, and some implementation details.
Flow vs Stock
This post by Jameson Quinn notes that there's two common reasons to upvote or downvote things. This is similar to my own schema:
- Conversational Flow – When you like (or dislike) the effect a comment has on a conversation, and you want to give the author a metaphorical smile of appreciation, or awkward silence/stare.
- "Ah, good point" (+)
- "Hmm, this gives me something to think about" (+)
- "This comment cited sources, which is rare. I want to reward that." (+)
- "This was clever/funny." (+)
- "I think this post contains an error." (–)
- "This comment is technically fine but annoying to read" (–)
- "I don't think the author is being very charitable here" (–)
- Some combination of the above (upvote or downvote, depending)
- Signifying Importance – When you think other people should go out of their way to read something (or, definitely should not). Ideally, posts and comments that contribute to the longterm stock of value that LessWrong is accumulating.
- "I learned something new and useful" (++)
- "The argumentation or thought process illustrated by this post helped me learn to think better." (++)
- "This post contains many factual errors" (––)
- "This comment is literal spam" (––)
- "The reasoning here is deeply bad." (––)
People instinctively use upvoting to cover both Flow and Importance, and this often results in people upvoting things because they were a good thing to say in a conversation. But then later, if you want to find the most useful comments in a discussion, you end up sifting through a bunch not-actually-useful stuff.
People also often unreflectively upvote things they like, without paying much attention to whether the arguments are good, or whether it's good for the longterm health of the site. This means people who think hard about their upvotes get counted just as much as people casually clicking.
So the idea here is that by default, clicking results in a Normal Upvote. But, if you hold the button down for a couple seconds, you'll get a Strong Upvote. (And same for downvotes).
Can you technically Strong Upvote everything? Well, we can't stop you. But we're hoping a combination of mostly-good-faith + trivial inconveniences will result in people using Strong Upvotes when they feel it's actually important.
I have some more thoughts on "what good effects precisely are we aiming for here", which I'll flesh out in the comments and/or the final blogpost when we actually deploy this change to production.
Vote-Power by Karma
Quick overview of the actual numbers here (vote-power/karma)
- 3 – 25,000 karma
- 2 – 1,000 karma
- 1 – 0 karma
- 16 – 500,000 (i.e. Thousand year old vampire - the level above Eliezer)
- 15 – 250,000
- 14 – 175,000
- 13 – 100,000
- 12 – 75,000
- 11 – 50,000
- 10 – 25,000
- 9 – 10,000
- 8 – 5,000
- 7 – 2,500
- 6 – 1,000
- 5 – 500
- 4 – 250
- 3 – 100
- 2 – 10
- 1 – 0
(We considered using another log scale, but log5 didn't quite give us the granularity we wanted, and smaller log scales produced weird numbers that just didn't really correspond to the effect we wanted. So we just picked some numbers that felt right.)
We're still hashing out the exact UI here – in particular, the UI for helping users discover the feature. (Posts basically have little-to-know discoverability, comments have a little hover-over message).
Check out lessestwrong.com and note your feedback here. (If you created your user account recently, you may need to create an alternate account on the lessestwrong development database)