If drivers come to expect surge pricing to be in effect on a given night, "It usually surges on Saturday night," then they will hit the road on that night.

Drivers are not dumb, they can predict when they will make more money, and will work more when there's more profit to be made.

The doggy day care I bring my mutt to won't take her unless she is up to date on all her shots.

But a people day care does not have this same rule?

That's just crazy.

The article mentions using facial recognition, so I assumed they had something working.

As for IDs, I just mean spotting fakes by checking the tell-tales. These days, when a bouncer gets an ID he's not familiar with, he has to pull out a book and look it up.

Buzz Aldrin needs to punch you in the face.

And bouncers. Facial recognition automatically identifies banned patrons. Video record proves they checked ID. Video camera verifies IDs from out of state / country.

Thank you for giving it a spin and reporting back, glad your tests worked. :-) Our policy is to not execute JS at all on older browsers like IE6 and IE7 (for security and maintenance reasons), which has the side effect of keeping us honest in ensuring all core features work without JavaScript.

Hey gl4ss, these are fair points, but I stand by my original estimate, including overhead & travel. A couple of things to keep in mind: 1) Although WMF is based in the SF Bay Area, it is a non-profit, there are no bonuses or stock options, and base comp is good but not as high as you can get elsewhere. We also hire internationally and our teams often include remote folks in regions with different pay scales. For positions like community liaisons, we often hire younger folks who don't get quite as high an hourly rate as an experienced engineer would. 2) Yes, managers need to get involved, there are meeeetings, etc., but our engineering managers tend to be responsible for pretty large groups (20+ folks) since teams working on user-facing features have their own dedicated Product Managers and most of the day-to-day decision making exists at the team level. This reduces the risk of micromanagement and keeps managers focused on supporting teams rather than getting in their way. 3) The delta in compensation between engineering managers and engineers is not as high as you might think.

Hi TuringTest, thanks for your comment! Contrary to your past tense, Flow continues to be in active development, and continues to be deployed to new use cases, most recently a new user help forum on French Wikipedia, and a technical support forum on Catalan Wikipedia. Since the only way to roll out a system like this is to replace existing use of wiki pages, we're proceeding conservatively to test it out in social spaces where people want to try a new approach, and improving it in partnership with real users in those venues.

It's true that talk pages, being ordinary wiki pages, support "making your own workflow". I love the Douglas Engelbart reference, though I doubt Engelbart would have remained content with talk pages for very long. The lack of a discrete identity for separate comments makes it impossible to selectively monitor conversations you're participating in (you literally have to use diffs to know what's going on), or to show comments outside of the context of the page they were added to. This is a pretty tough set of constraints to work with. At the same time, you're absolutely right that a modern system can't simply emulate patterns used by web forums or commenting systems like this one.

Like wiki pages, Flow posts have their own revision history. Flow-enabled pages have a wiki-style header. Each thread has a summary which can be community-edited. Threads can be collapsed and un-collapsed by anyone. All actions are logged. In short, wiki-style principles and ideas are implemented throughout the system. At the same time, we believe that as we add modern capabilities like tagging, we can replace some of the convoluted workflows that are necessary in wikitext. Already, Flow adds capabilities missing from talk pages -- notifications for individual replies, watching specific threads (rather than a whole page), in-place responses, etc. More to come.

Hello metasonix! First, congratulations on the successful article submission. In answer to your question, I was referring to LQT development. LQT was put into maintenance mode in early 2011, so of your "10 plus year project", about 7 years elapsed with a little bit of paid effort dedicated to the development of LQT. $150K max spent (not all of it by WMF) on LQT is really a high estimate -- Andrew Garrett, the only dedicated developer, also worked on other projects during that time, including the widely used AbuseFilter extension.

Flow development kicked off in summer 2013, about 18-19 months of development effort so far by a team that's fluctuated in size but currently comprises three full-time engineers, about half a person's time for UX design and research, a product manager and a community liaison. During that entire timeframe, I would estimate money spent on the project so far at less than $1M. Even if you combine both efforts, "millions of dollars spent" is pure hyperbole, and adding up elapsed time to exaggerate scale and scope of these efforts is equally misleading.

The article summary speaks of "millions of dollars spent" on a new discussion system for Wikipedia. The article actually tells a very different story -- the LiquidThreads extension started out as a Google Summer of Code project, was funded for a while by an interested third party, and then received a little attention from the Wikimedia Foundation (one designer, one developer) before development was put into maintenance mode. I would ballpark the total money spent around $100-$150K max. Elapsed time does not equate money spent. LQT continues to be in use on a number of projects, but its architecture and UX needed to be fundamentally overhauled.

Flow, the designated successor to LQT, continues to be in development by a small team, and is gradually being deployed to appropriate use cases. It is now running on designated pages in a couple of Wikipedia languages, and old LiquidThreads pages are being converted over using a conversion script developed by the Flow team. Contrary to the article's claim, WikiEducator upgraded to a recent version of LQT, and will be able to migrate to Flow in future using the conversion script.

You can give Flow a try in the sandbox on mediawiki.org and see for yourself whether the article's claims are hyperbole or not. Disclaimer: I am the person referenced in the headline of the Wikipediocracy article, so take my view with a grain of salt, as well. ;-)

The one HUGE advantage your iPhone has is that it is with you, in your pocket. You can't take a picture with a camera you didn't bring with you.

I hear arguments like this a lot, in general, but they forget that the S&P 500 (or whatever) is a selection of stocks which is continuously changed, and if you "held" the S&P 500, you'd have to sell the companies that drop out of it or go bankrupt, and buy into the companies that enter it. And suddenly, the amazing returns of whatever basket of stocks disappears. It doesn't take many lemons in the mix to ruin the supposed gain.

From the summary: "The battles in Battle of the Five Armies are deadly boring, bereft of suspense, excessively padded, and predictable to the point of being contemptuous of the audience."

That pretty much describes all 3 movies to a Tee.

Emacs user here. The only one in an office full of vi users. They and I have our config files set up so that indentation, etc all match, so when we open each other's code it's not all goofy looking.

I *can* use vi, I just prefer emacs, and I always have.

Marijuana. Is there anything it CAN'T do?