- I would move to absolutely close to work as possible, even if that means renting a closet from someone on craigslist.

- Consider the day job a sidejob (but of course, be professional). Always look for a better gig.

- Be frank, say you need a vacation right now/nearly immediately because you're unable to keep working at this pace. If they make up flimsy excuses, stay firm and say something like "I feel like I'm not performing at my top level because I'm headed in the direction of burning out. I would like you to help me be recharge my productivity and engagement by finding a way to get some time off very soon because this will save you from having to fire me and hire somebody else and me from having to quit because I really want your help to allow me to get back to firing on all cylinders so we can get X done."

- Build a paper clock

- Visit a massage/sauna/spa place

- Do some random hobby meetups or local community center activities

- Volunteer at church/nonprofit to help the needy

- Donate blood

This is brilliant because the main cost of running gear is power draw (PDUs / electrical circuits). Having OEM/ODM blade ARM setup a-la sgi cloudrack/supermicro is the way to drive costs to the floor, in a Backblaze/Google way. Unfortunately, it's a "Dell/Walmart model" hypercommodity where such a business has to maintain massive customer subscriptions to stay cash positive and still just trickles in $.

It's an interesting space, but if I were launching a cloud IaaS/VPS, I would probably optimize for the other extreme of "Apple model" premium/full-service expensive hosting that has fantastic uptime, gear and sales/support for enterprise/startup and IT/web operations... There's some more money in that and less headaches. (The most money seems to be in the upper-middle pricepoint area.)

> I would probably optimize for the other extreme of "Apple model" premium/full-service expensive hosting that has fantastic uptime, gear and sales/support for enterprise/startup and IT/web operations... There's some more money in that and less headaches. (The most money seems to be in the upper-middle pricepoint area.)

A few weeks ago, I'd say "You mean AWS", but after this morning, and a few other incidents over the last few weeks, I don't think anyone can do fantastic uptime in a virtualized/cloud environment.

There's the rub, isn't it? Companies want to compete on quality, but if you're supposed to architect your application(s) for failure, uptime becomes a lot less important. You then only have price to compete on.

I know Twilio runs in both AWS and Rackspace, depending on various KPIs for shifting load. Seems to be the way the world is headed. I'm curious if containerization like Docker predicts CDNs running your containers for you at the edge...

I have fantastic uptime on linode. Averages probably 9 months?

Is that just uptime as reported by the OS, or actual time between outages? The server can be happily churning away even if its network connection goes down.

I've been on Linode for a while, and have also had a decent experience. However, I wouldn't use uptime as my only metric.

I will vouch for Linode. Also if you've never heard of Ramnode, they are my go-to VPS provider. I build actively monitored infrastructure with downtime notifications on the order of 5 minutes or less, so my story isn't just anecdote. I have bought hundreds of VPS over the years from a huge number of providers, and Ramnode is hands down absolutely the best provider. Excellent uptime and the VPS always feel snappy and responsive. It never feels oversubscribed like every other provider out there. Linode is also very good, too, IME.

Actual time between outages.

I've had a similar experience on Linode as well. In fact, in the few months that I have been using Digital Ocean for a personal server they have had more outages than the past ~2 years on Linode.

DO has really gone downhill. For some time they were top-of-the-heap for me with Ramnode and Linode, but lately (the last two years or so), they have really gone downhill with respect to overall quality.

This is important because "silence gives consent" to hate and violence directed at unprotected minorities. Revoking business dealings is one of the main levers to encourage countries/groups/companies to play nice. Tyranny of the majority (or to a lesser-degree, minority beyond a sensible point) are incompatible with civility.

Top-down configuration (as opposed to discovery like UDDI) via something like zookeeper or dns solves this problem. And APIs shouldn't do WSDL either, the code and docs should document the API. It's possible to add so many over-engineered layers of YAGNI flexibility that almost no one can understand what the heck is going on or how to hack on it, e.g., Eclipse plugins.

Keep it really simple, until it breaks too often.

Really good suggestion for the API doc. I admit that writing documentation is much harder than code;)

Hopefully, they'll do rpc adapters for zmq and rabbitmq.

There's a naive zmq RPC adapter here: https://github.com/lsm/micromono/blob/master/lib/rpc/zmq.js

Very buggy especially when clients disconnect/reconnect. But, it's good starting point if you are interested.

Any idea how this is done at scale, on C cancer cell lines x W compounds?

one way is 3D colony formation assay, 96 or more WxC combinations at a time depending on format and replication requirements

If Snowden or IS uses this service, it's still possible for governments to take you to court Lavabit-style (minus SSL private key) (or Mega or PirateBay) and get a court order to shut you down unless you have colo/VPS hosting in Iceland, Sweden or similar jurisdiction and private DNS registration with a registrar independent from most corporate/diplomatic pressures (definitely not name.com, maybe what piratebay uses: https://www.binero.se or similar with less inflammatory/infamous clients).

Privacy as a service/app cannot be sustainably delivered without being distributed, like TahoeLAFS or i2p. Company-run, centralized service/apps are SPOFs because they're at massive risk of being shutdown or blocked by friendly/unfriendly governments, at their whims, by whomever happens to be in power. The instant email option is partly distributed but the bigger risk is being in the US means US courts, FBI, local police, etc. can grab your provider's servers. name.com is also subject to both Irish and American laws.

Unfortunately, most founders of privacy apps are business naïve and unable to manage their attack surface, making them easy prey to non-technical but more business-savvy folks. This resistance is further compounded by the sunk costs-bias, because what's done is seen as an immovable foundation which can never be torn down and, therefore, it must be worthwhile in the face of overwhelming contradictory evidence (e.g., 1950's lifestyle worship leads to cognitive dissonance with climate change). In reality, a venture should be a viewed as a never-ending collection experiments, where the assumptions may be turn out to be terrible to excellent (hopefully nearer to this) and trends/disruptions may move out from under it all.

Good luck and I hope it makes a lot of money before it gets shutdown by Hillary or the Great Firewall of China.

Forget even government attackers. The entire point of the product is to avoid trusting them. Except... you still utterly and totally trust them, as there's no way to verify what the form is actually doing.

I had a long chat to a taxi driver medallioned in Chico, Sacramento and SF the other day.# It seems Uber is doing good to bring the fight to the pay-to-play bureaucracy, but it doesn't seem to be showing enough demonstrative acts that their drivers are making more/have better conditions than non-Uber drivers.

# This summer, it seemed there were only 1-2 Uber X drivers in Chico which didn't work weekends. If they did, I had a credit to use which would've meant a free ride. Also, the rules in Chico is that a Paradise (a nearby town) company can't pickup in Chico and vice-versa.

Many carriers already MITM port 80/tcp (blindly sending SYN ACKs). Symptom: try connecting to a random domain without a webserver (like http://cse.ucdavis.edu/ ) and it will seem to have a website but just hang.