This is relevant: the LW code is a little bit gnarly to set up, having this in a pre-packaged VM can help.

These days Vagrant is being superseded by Docker, I might have a go at turning the VagrantFile into a Dockerfile if anyone is interested.

Fair enough, and I see the link for sorting by stars is here.

Should I literally just be going down the list top to bottom? Or limit myself to things that are accepted / authorized?

Did they add auto-playing video ads to the LessWrong frontpage, or do I have malware?

I received a lot of errors over the weekend relating to a performance regression introduced in the last set of changes. Eugine, you were one of the people affected by these errors. I released a fix for this yesterday and have not seen those errors since. Work is also underway to migrate to a new database server.

Previous behavior was chosen intentionally, see this thread for the discussion. I think the change should be reverted.

Awesome! That was one of the most asked-for feature!

And it is implemented on comments too, as a title text: Mousover the karma score of a post or comment and a little popup will give you the percentage of positive votes!

(a side effect of this is that if we see a comment at 0, we can't immediatly differentiate 1 upvote and 1 downvote from 50 upvotes and 50 downvotes, but that's pretty minor)

Many thanks to the trike apps people, and whatever volunteers helped implement, test and deploy this!

Edit: This specific fix appears to be thanks to Wesley Moore.

This is actually a bug, not a feature. Some major changes to how karma is stored and passed around the application were made in order to implement the percentage tooltips. Scores are now passed around as an array containing the number of up votes and down votes, where previously it was the difference of the two. It appears the this array is being incorrectly rendered in the side bar, instead of the calculated score.

It appears to me that 30 day karma has switched back to votes received in the past 30 days from votes on material posted in the past 30 days. Why? The original switch was very soon after the introduction of the feature.

I noticed this because people who haven't posted in months have 30 day karma. I then tested it by voting on an old comment.

Confirmed. The issue is in an interaction between the polling code and Reddit's custom ORM which causes vote-totals to be cached, but not persisted to the database correctly. I have a fix, which I'm testing now. All polls created before the fix is applied will be affected; it'll be possible to restore them, but it'd take some work which isn't a priority for me.

Thanks for spotting this! I looked into it, and it seems to be double-counting the most recent result when computing the median. It's an order-of-initialization issue; it thinks it's getting all the results except the new one, adding it, then taking the median, but it's actually getting a list of all the results. The fix is straightforward; I'll email the admins to apply it.