onestone

Linode, DigitalOcean, OVH, Hetzner, and so on...

Stop using providers which charge a ridiculous price for bandwidth (like AWS). There are many excellent alternatives where a TB costs only a few dollars/euros.

Inoreader as well. Hands down the best of the bunch which emerged after Google Reader was closed.

Can't be sure, it's a "garbage sites" password which I've used too many times on untrusted sites. Any one of those sites could have been hacked, or had been a phishing gateway itself.

Of course what I did was bad practice. One should store passwords in a secure password manager, and use a different (preferably 30+ chars) password on each site.

It isn't the actual Gmail passwords that are leaked. One of my accounts is there, but the password is one I have used on other sites, never on the actual Gmail account.

> Is there anything specifically about GitHub which puts you off, or is it just that BitBucket works so you don't want to change?

Github has a much worse record vs. Egor Homakov than Bitbucket :)

Also, Github is Git-only, while Bitbucket supports both Git and Mercurial. I use both, but prefer Mercurial myself, despite it being less popular.

Spend it for products or services - sure. Immediately exchange all of it for a fiat currency - not so much.

I'm not sure why you disagree. Of course there are multiple factors and some of them counterbalance. And of course what I mentioned is just one of these factors.

It matters. Automatically exchanging large amounts of BTC for USD creates a downward pressure on the BTC exchange rate.

Organizations which truly support Bitcoin would choose to keep it.

These hidden fees would only apply if you choose to receive fiat settlements (which I wouldn't).

Why would you want to? You'd be caught in the same infinite loop.

Yes, their rules are a mess. However, as the OP mentions there was indeed an "AdSense for Ajax" beta several years ago, and refreshing ad slots was listed as its primary use case.

In my case, my site is structured as tabs. I refresh the ads when the user switches the active tab. A tab occupies about 95% of the page anyway.

There is actually pretty good support, but you have to use AdSense through Google DFP - https://www.google.com/dfp/. Things like creating ad slots dynamically / loading them later / refreshing them dynamically work fine when you use GPT tags in DFP.

Houdini had a slight edge against Stockfish DD, which is a few months old. The latest Stockfish version (v5, very similar to the version that competed in the TCEC Superfinal) is ~60 Elo stronger, and demolishes Houdini at all time controls. It should soon start hitting the more conservative ratinglists.

What sets Stockfish apart is its open testing framework. Many volunteers allocate CPU time to run test games, checking if a pull request actually adds Elo rating points. Also, its open development model is a big advantage compared to closed-source chess engines, which usually just have 1-2 developers. The ideas used are mostly the same in all top engines, the advantage of Stockfish comes from tuning/testing/polishing/tweaks.

An year ago Stockfish was near the top, but not quite there. Since then its development model became more open, and the open testing framework was introduced. The rate it's been adding Elo rating points since then has been amazing.

The node.js cluster module is not flexible enough to be used with engine.io / socket.io / sockjs etc. Just run several processes and put something like HAproxy in front of them. If using a cookie to ensure stickiness, you can scale to multiple load-balancers easily.

Yup. And Kay Sievers has another clone of the story, with a (quite unapologetic) comment of his own: https://plus.google.com/+KaySievers/posts/3cWXzYqB6MB

Indeed caolan/async has been a de-facto standard until recently. But for me personally it has become obsolete, with the standardization of generators and promises.

The previous submission: https://news.ycombinator.com/item?id=7203364 was a bit premature. Now that Colin Watson has voted other options before F, it's clear that D (systemd) will be the winner.

Generators and Promises play very well together.

I love Coinpunk, but don't care at all about Apple and their ecosystem. Maybe this is not the most effective way to ask for support.

After Ryan McGeehan's comment about the "million dollar bug" (cited in your writeup), I'd say your bug is worth at least $100k.

+1 for the 'hg hello' idea.

Extending a core language prototype is never necessary. And you never know which library will break when you do this (unless you review carefully the entire code of all modules you use). So it is a bad practice, despite sometimes being ok.

I admit that extending the String prototype is less dangerous than e.g. the Object or Array prototype.

It's definitely not true, at least in some countries. For example, France: http://arstechnica.com/information-technology/2009/09/big-gp...

"It's a commonly held belief that only the copyright holder of a work can enforce the license's terms—but that's not true in France. People who received software under the GNU GPL can also request compliance, since the license grants them rights from the authors."

After all, the rights of the customer (to receive the source code) are also being violated.

For the record, Node's I/O performance is better now that it's based on libuv (after libuv removed its own libev dependency) than when it was based on libev. This doesn't necessarily mean that libuv is always faster than libev, but at least for Node's use case it was.

Rackspace basically do the same. I've had a Rackspace Cloud server null routed due to a plain vanilla SYN flood DoS attack (note the single D).

The !! mentioned in the article does exactly that.

This is the dumbest article I've seen on HN in quite some time.

Impressive indeed. A post by the author in the main NodeJS group (https://groups.google.com/forum/#!forum/nodejs) would be great.