LessWrong anti-kibitzer (hides comment authors and vote counts)

Related to Information Cascades

Information Cascades has implied that people's votes are being biased by the number of votes already cast.  Similarly, some commenters express a perception that higher status posters are being upvoted too much.

If, like me, you suspect that you might be prone to these biases, you can correct for them by installing LessWrong anti-kibitzer which I hacked together yesterday morning.  You will need Firefox with the greasemonkey extention installed.  Once you have greasemonkey installed, clicking on the link to the script will pop up a dialog box asking if you want to enable the script.  Once you enable it, a button which you can use to toggle the visibility of author and point count information should appear in the upper right corner of any page on LessWrong.  (On any page you load, the authors and pointcounts are automatically hidden until you show them.)  Let me know if it doesn't work for any of you.

Already, I've had some interesting experiences.  There were a few comments that I thought were written by Eliezer that turned out not to be (though perhaps people are copying his writing style.)  There were also comments that I thought contained good arguments which were written by people I was apparently too quick to dismiss as trolls.  What are your experiences?

53 comments, sorted by
magical algorithm
Highlighting new comments since Today at 5:00 PM
Select new highlight date
Moderation Guidelinesexpand_more

If the main Less Wrong codebase offered an option to hide the names of contributors and non-negative karma point totals (because negatives you may want to let your eyes just skip over), not revealing them until voted on (including a neutral vote)...

...then what would you think of only giving half a karma point for any votes made without obscuring the name and current total? (Likewise any votes changed after the reveal.) Fair? Or just annoying?

The half-point idea is an interesting one. I find it hard to think of genuinely good reasons for wanting to know how positive a score is before deciding whether to vote up or not, and I haven't heard any good explanations from anybody else yet either. That's to be contrasted with the multitude of bad reasons for wanting to know the score beforehand, which exploit common cognitive biases that we are all at least partially subject to. I do find the idea a bit heavy-handed, but I think it would make the community slightly less herd-like and a bit more rational.

Of course, you'd also have to change the code base so that once an initial blind vote has been made, any further changes would only register at the lower value.

As to whether it's unfair, you could explain it as getting an EXTRA half point for your willingness to make a small sacrifice for the betterment of the community at large. You could even make it 1 point versus 1.5 points.

that's brilliant and hilarious. We should implement more de-biasing programs by exploiting biases.

Though I'd say by this scheme it should be 1 point versus 2, just to preserve the punchline.

Maybe have endorcements for the program by respected members? Pictures of attractive women marvelling at Bayes on little adverts? Make it opt-out?

IMHO, unfair. But it would be interesting to have an option to see such a total, or to see how much karma is from info-obscured vs info-revealed votes.

Just annoying.

Though I frequently change my votes as I reflect on them, so even reading anonymously I'd probably end up with all devalued votes. And this process of reflection would eliminate any debiasing effect of reading anonymously.

Of course, I put a lot of stock in character, so I don't see the problem with occasionally voting up comments by better people.

Simply annoying from a usability point of view. It requires you to know too surely which posts you will want to vote on and which authors you'll want to know; if you care about the value of your karmic vote you'll wind up interfering with your enjoyment of the posts to preserve its value; etc.

The latest version of the Anti-Kibitzer Script (click "View the original post" above this comment to lean more about it)

  • is integrated directly within LessWrong (no more Greasemonkey)
  • is controlled by a section in the user Preferences called Kibitz Options
  • hides names and scores from sidebars, and hides your own karma score

To activate, simply navigate to Preferences and check "Enable anti-kibitzer" - this will add a button to the upper right allowing you (without refreshing the page) to temporarily display names and scores again.

When the feature is active (respectively inactive), the button says "Turn Kibitzing Off" (respectively "Turn Kibitzing On"). Shouldn't it say turn "Turn Anti-Kibitzing Off" (resp. &c.)? Kibitz, to gossip, so removing the names is "anti-gossip," right?

I don't seem to have that preference. Is it still supposed to be there?

Not released yet, as I alluded to elsewhere. I jumped the gun in updating the above comment to describe what's coming.

Version 0.44 is here, still packaged as a Greasemonkey script.

I think one of the useful things about being able to identify people by name is that you frequently end up entertaining a contrary opinion you would have otherwise dismissed because it's held by someone you respect. Such events are probably more significant to personal development than discovering a gem in the rough you would have otherwise overlooked. Hiding karma probably has more utility than hiding names.

How hard would it be to make a modified program that tracked the up-votes and down-votes one makes with and without it (storing the comment author, the number of points the comment previously had, and one's own vote) and then printed that data in some Excel/Octave/etc.-readable format? It would be nice to know the details of my own biases.

This program is great, though. Thanks, Marcello.

Actually, I find I have the exact opposite problem. I almost never vote. Partly that's because I read Less Wrong through an RSS feed that doesn't even show the vote totals. I only ever vote if, like now, I've gone to the actual site in order to comment.

Even then, I find that I am comparing the quality of Less Wrong posts and comments against the entire corpus of what I read on a daily basis, some of which is great, and some of which is dreck.

So, I tend to only vote when the quality of what is written is extremely good -- enough so that I want to 'reward' it -- or extremely bad, so that I want to punish. The vast majority is in the middle and so I don't bother to vote.

I think the latter experience is telling. my experience of trolls tells me that they get labeled as trolls because they say things that make people uncomfortable because they suspect they might be true. If the so called troll was just saying completely wacky things it would be simple to dismiss them. Someone coming into a forum and shouting white power or some such nonsense is not the same as a troll.

This is really great. Thanks for making it available.

My only suggestion is to hide the "Turn kibitzing On/Off" icon after a few seconds and only show it when the user hovers over that area.

The reason I make this suggestion is that while I slowly scroll down the page while reading, the icon jumps all over the place in the upper right corner as it repositions itself 10 times a second.

Even if it didn't jump around, I'd still rather have it hidden except when needed. IMHO, it stands out against the dark background and mars the otherwise very nice LW aesthetic.

That's a bug of sorts in the script, and easily fixable. In fact, I've already done so; have an updated version.

I'd still prefer it be hidden altogether after a few seconds until I hover in that area, but this is a big improvement. Thanks.

Your version is now the official version 0.3. However, the one thing you changed (possibly unintentionally) was to make Kibitzing default to on. I changed it back to defaulting to off, because it's easy to click the button if you're curious, but impossible to un-see who wrote all the comments, if you didn't want to look.

I'm significantly torn on whether to enable this. I understand the downsides of seeing authors (and am confident that I'm engaging in at least some of them), but I have one issue with it. Knowing authors can improve my ability to rapidly and effectively process posts. There's at least one author who makes very good points, but sometimes glosses over issues that turn out to be either quite complicated or openings to criticism of the post. I've found these omissions both important and quite hard to find - at the moment, its worth it to me to leave author names active just to be aware that I need to read these posts with a different style of criticism than I normally engage in.

In short, there are sometimes positive outcomes of knowing authors, if only for general efficiency increases.

I have my anti-kibitzer on, I've had it on for two days. I too, read certain posters more carefully than others, but now, rather than deciding who to read carefully by status, I decide who to read carefully by over-viewing the contents of their posts. Of course, you want to give more resources and time to a great master of the art, than to a moderate master. But deciding who is who by status, or letting status weight in as much as it does in humans, is almost as bad as not having any time management at all. It's like time managing, where you also falsely think that some independent variable has something to do with the content.

It appears as though activating anti-kibitzer causes the lesswrong, Singularity Institute, and Future of Humanity logos appear in the wrong places in the header.

I believe this is specifically anti-kibitzer and Firefox 4 in combination; I've had AK on for a while, and only noticed the problem when I upgrade from FF3. Other breakages include block quotation in comments and vote link bolding.

When I see a lesswrong post in my RSS reader, it still shows the author of the post. Is there a way I can avoid this? Does anyone else experience the same problem?

The anti-kibitzer script is designed with Web browsing in mind rather than RSS feeds.

The RSS feed doesn't seem to show posts or comments' karma scores anyway, and doesn't allow voting as far as I know, so the anti-kibitz feature may not be relevant for people who consume LessWrong that way.

I could be wrong about this, of course - tell me more if I am?

On a rationallity website that knows about biases like the halo effect, displaying the author of a post before the content is just silly.

The identity of the author influences my interpretation of the post before I've even read it, so it would be better if the author of the post didn't appear right at the top of the RSS item. This could be avoided by, for instance, creating a parallel RSS feed without info about the author. This would be a lot of effort to go to just for me, which is why I asked if other people had the same problem.

The only problem is, part of the meaning of the post is its context, and sometimes the author's identity provides context. Like when multiple people are having a discussion and someone says, "As I wrote above..." or something. They could just link everything, but it'd be best if the anti-kibitzer assigned random names or numbers to each commenter in a given thread - or something like that. That way you'd at least be able to follow a discussion. Or does it already do that?

Yes please. Gensymming authors by thread would fix most of the problems on both side of the kibitz button.

The author should probably be in manual control of which comments visibly share authorship.

I didn't think I needed this until the current kerfuffle over gender bias came up. Still unsure if it's the most effective approach to avoiding my own biases (i.e. judging argument and author together), but it's an awesome experiment.

A couple notes: I still see names in "Recent Comments", and I still see names in comment permalink pages. Still, good stuff!

Edit: Also, it hides my name and my scores, which seems rather useless from an objectivity perspective...

Just installed it, works like a charm -- I'll keep it this way. If only it could hide the sidebar as well.

Also, thanks to this post, I'm now aware of the fact that there are posts other than those listed on the homepage! I have no prior experience with Reddit, so I assumed that the front page is completely community-driven, but it turns out that it is for 'PROMOTED' posts only!

I spotted the word 'anti-kibitzer' in the sidebar, but was unable to find the post on the front page -- that's how I discovered the 'NEW' and 'POPULAR' links under the site banner.

I've upgraded the LW anti-kibitzer so that it hides the taglines in the recent comments sidebar as well. (Which is imperfect, because it also hides which post the comment was about, but better will have to wait until the server starts enclosing all the kibitzing pieces of information in nice tags.) No such hack was possible for the recent posts sidebar.

Well, to kibitz the anti-kibitzing, it looks to me like:

by Marcello

would match pretty easily against something that looked for

by (.+)

and deleted it, similarly on the Recent Posts but without the , checking for the identity of the two matched strings is optional (I forget how to do this offhand with REs).

That particular hack looks like a bad idea. What if somebody actually put a bold-face link into a post or comment? However, your original suggestion wan't as bad. All non-relative links to user pages get blocked by the anti-kibitzer. (Links in "Top contributors" and stuff in comments seem to be turned into relative links if they point inside LW.) It's gross, but it works.

Version 0.2 is now up. It hides everything except the point-counts on the recent posts (there was no tag around those.) (Incidentally, I don't have regular expressions because by the time my script gets its hands on the data, it's not a string at all, but a DOM-tree. So, you'd have to specify it in XPath.)

I think trying to do any more at this point would be pointless. Most of the effort involved in getting something like this to be perfect would be gruesome reverse engineering, which would all break the minute the site maintainers change something. The right thing to do(TM) would be to get the people at Tricycle to implement the feature (I hereby put the code I wrote into the public domain, yada yada.) Then we don't have to worry about having to detect which part of the page something belongs to because the server actually knows.

I hereby put the code I wrote into the public domain, yada yada.

A great way to put your code into the public domain would be to put it up somewhere like (ideally exactly like, because they're very awesome) http://github.com/.

If anyone else wants to modify your code the git (and GitHub) workflow is very good - anyone can fork your repository, and if you want to accept their changes that's easy for you to do.

See the GitHub Guides if you're interested.

by (.+)

by <a href="http://lesswrong.com/user/([^"]+)"><strong>([^<]+)</strong></a> would be better (you could also make your .+ non-greedy with .+?), but us (Trike) providing more classes and ids is better still. We're looking into it.

Uh, now it's on the homepage. I'm completely confused. What determines if (and when) a post makes it to the homepage -- human intervention or some kind of algorithm?

Editors include Robin Hanson and Eliezer Yudkowsky; they promote articles to the "Promoted" page.

Thanks for making this available. Plus, thanks for the opportunity to learn about Greasemonkey :).

Thank you. Trying it now and it's working perfectly. It's like a dream come true.

Looks great to me! Unfortunately I know via Recent Comments and Recent Posts the identity of the author of the above comment... ;)

The "Only works in Firefox" note in the preferences is incorrect; it's working fine for me in Chrome.

Anyone else using Anti-Kibitzer, the new version that's activated from Preferences?

The AK script is currently broken on article pages, due to some funky interaction between its CSS and the AddThis bookmark at the bottom of the page. (Since this is outside the LW codebase I have no reliable way to check if this is a recent change or if it has been broken for a while and I only just noticed. I'm pretty sure it's a recent change.)

I'll push a fix in the next few days.

Is anyone still using the old (Greasemonkey powered) version?

Fix committed and pushed. Though I'm getting the impression this is mostly for my own benefit?

I may take another look. I used it for a while... must be a year ago now. I hacked it around a little too, to add a couple of features I desired.

Turning off the 'new messages' notification and blocking comments based on user. I also had it so it would selectively block comments by a user only when they were replying to me.

I had been using the anti-kibitzer, but since yesterday if I pushed the button to turn it off I would get:

http://i157.photobucket.com/albums/t43/Macbi/lesswrongscreenshot.png

And if I pushed it again the page would be pure white (not even an anti-kibitz button). (Latest version of Firefox being used on Windows 7)

Yep, I've been seeing just the same thing. It's the defect I've corrected, and it will go away as soon as Tricycle push it to production. That sometimes takes a few day or more.

The specific defect in the code might make an interesting anecdote in that "programming as a rationalist skill" post I've been planning for ages. My thesis is that every single "bug" in software is the result of a map-territory mismatch.

In this particular case, I'd been assuming that once a Web page was loaded, its CSS stylesheets could be accessed by a Javascript program through an array whose ordering wouldn't change. This assumption turned out to be wrong: the "AddThis" widget at the bottom of a post inserts a stylesheet right at the top of the array, shifting the main stylesheet one place forward, so that it is on that stylesheet that the AK script stomps.