You can't play it on the subway, you can't play it on a plane. When are you supposed to play it then?

Except that low income job is going away to automation. So you have the same number of people competing for fewer low income jobs. If you use this inflation to make sure those low income jobs pay the same, you've evened it out.

Two cases:
Either Satoshi has his private keys from back then, or he doesn't.

If he has his private key, have him sign a message that reads "John R. Smith is Satoshi Nakamoto" with his private key.

If he doesn't, I say it doesn't matter who he is, his money isn't going anywhere.

Well... here's the thing. 99% of people just don't need more than 16 or 32 GB of RAM. I don't do any video editing, but at any given time, at work, I have several VMs open, Chrome or Firefox which tend to hog memory, a couple of development environments (usually PyCharm, VS, Android Studio or Eclipse), and several more lightweight stuff - IPython, Sublime Text and a couple more.

At max, if I set the VMs to too much RAM, this adds up to about 16 gigs of RAM. 32 gigs? No way I could get up to that. Maybe if I had an itch to keep 30 tabs open in Chrome instead of my usual ~6.

In the past with weaker computers, I used to ration my RAM. Haven't needed to do that in the last couple of years. Same goes for CPU - anything that's not really computationally expensive just doesn't take a long time to run nowadays. We've more or less reached the point where computers are good enough.

Obligatory CGP Grey

These guys really have some nerve. You'd think the least they would do is try to avoid the courtroom.

A mac would be good, if only for the zoom ability available on Safari and Chrome (might be available on Windows too). Pinch out on the trackpad to zoom a web page (really zoom, not just change text size).

http://bash.org/?14207

250,000 IOPS per second, right up there with your LCD display, PDF format, and PIN number.

I just don't get you Americans.

These visas were invented to enable highly-skilled workers to come from overseas to work in the US. That's clearly not what they're doing. Why don't those laid off sue? Or at least write your congressmen?

Not so sure about that.
We've had the internet, up alive and working for what, going on 20 years now? With no major outages? Redundancy every step of the way? I think it's OK to assume that the Internet will be around excepting armageddon or maybe a world war.

That said, any one system can be taken offline by targeting it specifically.

I've heard of this time and time again. Is there any evidence that software engineers are good teachers? I mean, the challenge in K-12 is getting control of the students, not the teaching material (which is low level and entirely uninteresting).

I currently have a D-Link DIR-685 (which works ok 80% of the time). There's a TP-Link WR941ND and a W8951ND which doubled as an ADSL modem. We've gone through a couple more which we don't have anymore. All with stock firmware.

All neighbors are older, youngest kids are in the 8-10 year old range.

Leaky microwave - it's possible.

Directional antenna - tinfoil style? Or does it require a purchase?

Where do I perform hashing (smartphone/web client or server)?
You hash twice, with different salts - once on the client side and once again (i.e., hash the hash) on the server side. The doubly-salted, doubly-hashed password is the one you store.

What hash algorithm should I use?
You said it yourself - bcrypt. bcrypt allows you to set a cost, which increases password brute-forcing difficulty but also increases computational cost on every verification. Set the cost to be the maximum you can handle - if you have a stronger computer and fewer users, you can set a higher cost.

How do I store the hashes?
Chrome uses encrypted SQLite for browser saved passwords. Which encryption depends on the platform - Windows has CryptProtectData, KDE and Gnome have keyrings. The basic idea for all of these is to use some symmetric encryption algorithm (e.g. AES) with the key derived from some set of hashes on machine-specific data, like hardware serial numbers. If you want to go hardcore, use a hardware encryption dongle (HSM).
Note that it is important to encrypt the file on disk, but it is also important to make sure that decrypted hashes stay in server memory for as little as possible.

How can clients recover forgotten passwords?
They can't recover forgotten passwords - you're only storing hashes, remember? What they can do is reset their password. Two factor authentication is best (a verified email account and phone number, if you can send SMSes or automated calls), but at least email and a security question seems to be the standard.