All of wmoore's Comments + Replies
Great to hear you're interested in contributing Chris. The LW codebase takes a bit to get your head around so I'd certainly suggest starting with smaller bugs or small features before diving into big new features. You should definitely get in touch with us (TrikeApps) and Luke to discuss what you want to work on to make sure it's the best use of your time and your approach considers all angles.
For reference, Accepted issues are generally bugs. The Accepted status indicates they have been reviewed and acknowledged as a bug. Approved is used to indicate tick...
SiteMeter in the sidebar was the cause of this. It has been removed.
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.
Ok, it has been reverted.
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.
Given that people are already coming up with crude hacks for extracting some of that information, it would be nice if the percentage tooltip displayed the raw array as well.
You're correct, John deliberately changed this as he thought it was a bug. I'll chat to some people to work out what the desired behaviour is.
I've just deployed a fix that will apply to all new poll votes. Thanks jimrandomh for passing on the bug report and initial patch.
Your fix for the incorrect median calculation has been deployed.
Fix for this and issue 327 has been deployed.
Test in Chrome
2 karma points are now required to start a new discussion. We'll see how this goes at reducing the spam.
yo again
yo
Morendil your latest patch has been applied and deployed. We took the liberty of inverting the preference for two reasons: Firstly it made more sense for the checkbox to be checked when the kibitzer was enabled and secondly we added a note that full compatibility requires Firefox for now, the text of which was hard to phrase with the uncheck to enable behaviour.
Hi ciphergoth, I've made some changes this morning that make the Less Wrong code base compatible with PostgreSQL 8.3, which is available in the karmic repositories. The change is on the 'postgres-8.3' branch in git. I have run through and revised the Hacking on Less Wrong wiki page this morning on an Ubuntu 9.10 install and have confirmed that it works. It would be great if you could have another go at getting the code up and running and let me know how you go.
It's unclear -- do you mean that the number of points received for posts gets multiplied by 10, both for positive and negative votes?
Yes an up vote on a post is worth 10 karma points to the contributor, a down vote -10 points.
With regard to discussion, I just implemented what I was instructed to do.
Some changes to karma have been deployed today. Posts will now show scores less than zero, previously scores below zero were shown as zero. Votes on posts are now worth 10 points up or down to the contributor. Also the threshold to be able to post is now 50, up from 20.
Markdown test
Does anyone know if these accounts are being managed or is there the possibility as you say for a siege at a later date?
The missing comment's have been scraped off the old OB site and should all now be present,
We did our best to try to link up OB names with Less Wrong user names. However as there were many hundreds of names this had be done automatically. For a match to be made the name on OB and username on LW had to match, as did the email address on both sides.
If you supplied an email address on OB then that will have been imported and you can claim the account by following the forgotten password process for the account. Assuming it has your email address you will be sent an email and be able to reset the password.
This should be fixed now.
Yes, we're working on this. The missing comments were omitted from the Type Pad export. It has been raised with TypePad.
'Top' now defaults to 'All time', instead of 'Today'
The behaviour was all inherited from the initial Reddit codebase. It just isn't feasible to rip out and re-implement all the javascript dependant parts of the site that are already there and working.
There's no reason I can think of why you wouldn't be able to edit your comments. What exactly is happening?
No there isn't a way to check vote counts at the moment.
The main driver for the limit was to prevent someone registering one or more accounts and being free to vote everything down.
I've verified the numbers, thomblake has posted 2538 down votes. 93t is 11801 in base 36. Adding 436 articles drop the percentage slightly to 20.7%.
Due to some users being unexpectedly limited from down voting by the prior change. The threshold is now four times your karma.
Quick fix deployed. I did some analysis of user's down vote count and karma. This change allows everyone to down vote that doesn't have a massively skewed down vote to karma ratio (Like 21 to 2 or 548 to 137). Obviously this still leaves thomblake roughly 500 short.
It was mistakenly assumed that most people's down vote count would not be approaching their karma, particularly for high karma users. I'll do some more research and discuss it with Eliezer.
Initial quick fix: downvote limit = 4x karma.
The anchor was removed when the article content was removed from comment permalinks as the comment should be visible on an average sized screen without jumping down. The content above the comment is also relevant to the permalink now more so than before so this was another reason why it was removed.
Thinking about this more I decided to make a start on an FAQ/user guide on the wiki.
Feel free to add anything that you feel is useful.
There is lots of content that is managed with styles to allow the dynamic aspects of the site. CSS is a required browser feature of the site.
What are you seeing? Why would you need to exceed Eliezer's karma? The limit on down votes is based on your karma, so you should be able to cast more than 500 down votes at the moment.
Javascript is a required browser feature of the site. Its needed for most interaction (as opposed to just clicking around and reading) and to load the side bar.
An FAQ/user guide for the site is needed. In its absence the Reddit help is mostly applicable.
You are notified when you reach the limit by a message stating how many down votes you've made and what your current karma is. Until then I imagine you should not let this limit influence you:
Note: It is possible to see this message and the down vote count be greater than the karma due its dynamic nature.
We've deployed a fix for the Top Contributors that should see all 10 users listed. Although it may not be immediately visible due to client and server side caching. You may need to give it up to an hour before it shows up.
Up votes aren't capped but your point about lurkers is interesting. The primary motivation for the change is to stop it being easy to just register an account then down vote everything you can find.
You have banned comments.
We've just deployed another related change: Now you can only cast as many down votes as your karma value.
I would still like to see a list of recent edits and/or active pages in the Less Wrong blog sidebar, and a list of recent blog posts and recent comments in the Wiki sidebar.
If the recent edits were available as a feed (which they are after a quick look at MediaWiki) then this is very easy to implement. In fact it would be entirely Javascript. This is exactly how the "New on Overcoming Bias" section in the side bar works.
Ahh that's why there are people missing. When the site first went live and before it was announced someone found it, created an account with a questionable username and posted an article of little relevance. A hasty fix was put in place to exclude anyone from the Top Contributors list that had a banned article. Now that the community is much bigger this fix can probably be reversed, which would see the missing people re-appear.
We'll keep an eye on this. We won't be chasing fixes for developer releases but if the problem persists it will be fixed.
The inbox is a feature that came for free with the Reddit codebase but it was "lost" when the site was restyled. You will notice that the formatting of inbox page is totally messed up, this is also because it wasn't included in redesign. Notification of replies is on the list of things to implement but there's some higher priority work going on at the moment. Since it is a small change and many people seem to be requesting it I hope that we will get to it soon.
Unfortunately article submission requires Firefox 1.5 or newer. I was able to reproduce the problem you described in 1.0.7. However I was able to successfully submit an article using 1.5.0.7. This is due to the javascript based WYSIWYG editor TinyMCE being required, which would explain why Lynx didn't work either.
I have raised an issue to either make it work or make the behaviour more friendly.
Please note that as of late last year the official development environment is now built with Vagrant. The primary repo contains a Vagrantfile and all the chef recipes (derived from our production recipes where possible) necessary to configure a base Ubuntu box for LW development.
The instructions for using this are at: Development-VM-Image.