Then you might want to read the following links: http://www.paulgraham.com/spam.html http://www.paulgraham.com/better.html

They describe how bayesian filtering works and how to use it to detect spam automatically.

I have the same desk, a Steelcase Please they work out quite nice.

http://www.daemonology.net/hn-daily/ This is probably what you want.

Just what I was looking for. Thx

I ran into a problem with a tcp connection to php-fpm just some weeks ago: The Server served requests at a rate of about 400req/s for some time without a single problem, until I ran out of useable ports. You won't have this problem with sockets.

The big difference is that on Swoopo you lose your investment if you don't win. But on 99designs you can still keep the design and get the feedback that it wasn't the right thing, and what was. Even if you don't get the job, you still get the practise and feedback. So I think there is at least some benefit.

You're not competing for the job - you're provided with the job when you enter.

You're competing for payment. There's a big difference.

I think expecting participants to be grateful for the opportunity to practice stretches credulity a little.

I always like to say that you could beat somebody with a x41 over the head and then continue working. Sometime ago a friend of mine actually had to use his X41 to defend himself. He did just that and it worked just fine for some more months until it died from an unrelated problem.

If I got it right, then point #4 is that they actually only get charged when there is a product to deliver, i.e. they get the product and you get the money.

It's directly on the about page:

What is HackerBuddy? HackerBuddy is a weekend project built using Ruby on Rails. It was built as a way to learn Rails, there is a very large chance that this site will collapse under the weight of it's own awkward code. If it does - sorry - I plan to improve it as I get better at coding in Ruby, please bear with me.

> When debugging you have to find the source of the problem in the PHP, though ideally after that you can just find the matching Pharen code and go from there.

You could always just add the S-Expression that became the php code as a comment. From there it should be trivial to find it in the Pharen code.

This reminds me of "A Mathematican's Lament" by Paul Lockhart ( http://www.maa.org/devlin/LockhartsLament.pdf ). It is a great read in any case.