yackob03

I think the obvious repercussion is that business will do everything possible to avoid this threshold, whatever it may be, up to and including cannibalizing their margins. N=500, we have 499 people, do we hire one more or find a way to automate that new need or other jobs, even if it costs more than a human would?

I hope those are fake keys too:

http://vision.ucsd.edu/~blaxton/sneakey.html

I have never seen the options ending in $9, does this only show up if you're paying cash? When I pay with credit card I always get $10 and $20 options. If it is only for cash users, $19.05 is a really terrible experience for someone paying with a $20.

I'm assuming they have variable pricing based on distance traveled, and 20 EUR covers the highest fare for the system. That could just be my optimistic bias speaking though.

I can't tell if this is satire.

I tried what you said and I could definitely feel my eye moving. Is that being synthesized by my brain?

I will speak to the issues about which I am familiar.

Checksums are currently uploaded by the client and verified by the registry. Signing is on the roadmap[1]. I'm not sure what you mean by a fingerprint, would this be analogous to an SSH host key? What function would it serve if you already had a signature that only you could reproduce?

[1]: https://github.com/dotcloud/docker/issues/2700

Images may also be stored in one of the available private registries. <shameless plug> As the Co-Founder, I am partial to Quay.io [https://quay.io], which in my not so humble opinion has the best features, reliability, and support for businesses and organizations, but there are other options if for some reason Quay.io doesn't meet your needs. For those who prefer to self-host, we've also got an enterprise option, which brings all of the index and registry goodness behind your firewall. </shameless plug>

That said, we love the Docker ecosystem and way of doing things. A sibling comment mentioned how complicated Docker is, but I think when you realize that they are trying to offer DVCS like features and paradigms, you will realize that it is complicated for a reason. We all thought git was complicated at first as well.

This will get a response, not because you are trying to pay Google money, but because you are trying to use the word "google" in an ad. Had an ad for an App Engine related service blocked for a few days until a human could verify that the message containing the word "google" was appropriate.

I'm not sure how much this solves your problem of "deploying docker containers" but our service Quay.io can be used to push/pull/serve your private binary images. Couple that with something like Digital Ocean's Docker image, and you can deploy docker containers pretty simply.

Ligature symbols actually addresses this. there just aren't enough of them for my needs.

http://kudakurage.com/ligature_symbols/

I tried to leave a comment on the author's blog, but it crashed. Instead I will leave one here. We have a number of docker images that we use at DevTable to provide environments for user-hosted software (think: development servers). There was no official way to host them privately, so we built it! Quay.io (https://quay.io) lets you store your images privately, as well as having a rich access management system to allow you to delegate read, management, and administration privileges.

Correct me if I'm wrong, but as far as I know Docker actually does run a binary called /sbin/init, it's just that they've replaced it in the base images with something that is more suited for fast startup times and running of a single process. Setting the Docker start command to init will probably not accomplish what you want.

We're using Docker in production (even though it's not 1.0) and it's been great so far. We manage a large number of small images on behalf of the end goals of our users at DevTable, and managing the images themselves was becoming a pain. To address this we built Quay.io, which we're using to store our images and feed them out to our servers in production. With your large number of apps and containers, you might find it useful too. We're basically trying to be the Github of Docker images.

They will also be less likely to attract future contractors.

I can already get this experience as I walk through Little Italy, when restaurateurs try to lure me in with "specials". Unfortunately, the loudest most assertive people are the ones usually offering the worst meal for my money. Yelp's use of crowd sourcing and aggregation was the solution, not the problem.

There will have to be an algorithm that decides whose voice should be heard, in which case, maybe they can use a reputation system to make sure I'm not being gamed.

You could two-way bind this with a traditional payment form and end up with something that's useful in the traditional case (feedback about whether the data you're typing is going in the right place), and may delight users who understand what they're seeing and choose to interact with it.

I would argue that Yelp drives far more offline traffic than Foursquare. If you're going to bet on a market leader, why not them? Have the tech elite written them off for their shady business practices?