ecaron

The title doesn't do this article justice. Digg is ditching comments and rebranding themselves as "v1".

> more or less the same for each site, with one of the sites being slightly different

That's because the Clojure library isolated you from the vastly different interpretations that those providers have of the spec. Had you written your connectors from scratch, you would have experienced the "mess."

I think the best hope of getting OAuth back on course is getting the current spec-writers to separately right a mechanism that interfaces with Google, Facebook, Twitter and LinkedIn. After they've each done that, they can get together and talk about how to rectify the train-wreck.

I don't see any confirmation in the forum that the "e-mail addresses of users" was leaked by Dropbox. It also appears to be mainly Euro-centric accounts. So while there is certainly a problem and it is very likely originating with Dropbox, the title is quite misleading and overly condemning given the known facts.

Except that there's a significant difference between "trust" of input from the user vs. "trust" of the software stack you use as a foundation.

Unless you've read every line of the Linux kernel, we all succumb to the later point sooner or later.

This is rather interesting, given that Mozilla had recently adopted the lead developer from the Mozilla-based IM client Instantbird to incorporate chat into TB15. Knowing the software is deadpooled, I wonder in hindsight if that was a last-ditch effort to stay relevant or if that effort helped highlight the inevitable decline/futility of desktop-based email.

tl;dr - 128kbps CBR audio has such bad quality nobody should use it, but all options of higher quality are indistinguishably different to the masses.

Now if only Patrick L. Jones (Senior Manager of Continuity & Risk Management) would step aside. His involvement in the gTLD continually sides with "what's best for corporations and $$" rather than "what's best for the future of the internet" (which I would argue is ICANN's first responsibility.)

A list of Jones' gTLD involvement can be found at http://www.icann.org/en/about/staff/jones.htm, and an quick example of his corporate-bias is at http://forum.icann.org/lists/jobs-phased-allocation/msg00315....

ICANN's appointment of Kurt Pritz actually bodes well for the future of the [seems to be a doomed endeavor] gTLD process, given his no-nonsense approach in the previous train wreck that was the .jobs TLD (http://news.dot-nxt.com/2012/01/11/dot-jobs-could-kill-icann)

> Want to report it to the vendor? Great. Fine. Making a website dedicated to the crash? Waaaay too much time on your hands.

Time to report bug to Microsoft: 30 minutes. Time to create website for bug: 4 minutes. #justsayin

I updated the page (which I hadn't touched since mid-2011) to say it doesn't crash the current RC of IE10. Hopefully people will stop flaming me on Twitter now...

I'm the author that discovered this bug - and went way out of my way to tell the Internet Explorer team about it. I uncovered the error while working on a client's SharePoint site and figuring out why a certain page always caused their computer to freeze up.

The most amazing part of this exercise has been analyzing the traffic trends. This page gets a crazy amount of traffic in Japan and China - I still can't figure out why.

It has also been a remarkable insight into the dysfunction that is Microsoft; I'll hear from some random Microsoft employee twice a year who became aware of the site and wants to fix it, after pointing to the closed "not a bug" thread on MSDN they all vanish (apparently keenly aware of how atrocious the IE team reacts to external interest/support.)

> God what flamebait, how is this near the top of the front page?

Because the source is widely respected and has an amazing demonstrated grasp of what good programming involves.

It is hard to read this story without thinking about the massive scale of "we just built this building, but we're going to tear it down because it is a deathtrap" demolitions that are happening in Beijing and the other populous cities in China that are still growing at obscene rates: http://www.zerohedge.com/article/china-proudly-demolishing-b...

I think none of that really matters until we see the price. There's a trial version and a free version of Microsoft SQL, but their full version can quickly top $20k without much effort - knowing how bad your "ouch" will be is key before I'd spend any time on the "ahhhh."

I read this on a day when I'm about to head home and install Windows 7 on my new machine, because Ubuntu12/Mint13/Fedora17 all crash on the hardware because of known bugs with the modern hardware that haven't been fixed yet and I don't have a PhD in kernel development to fix it myself.

There's just something cruel in the world for reading this and being reminded of why I've dreaded the install I'm about to do.

I have to imagine that this will open the potential for a viral website of the "is your spouse still playing the field" variety.

In fairness to Twitter, it was never actually known if the accounts/passwords came from Twitter.com (proper) or (more likely) leaked from some 3rd-party Twitter-integrating app that had pre-OAuth integration.

I thought Google's CityHash - http://code.google.com/p/cityhash/source/browse/trunk/README - was their successor to the MurmurHash variants.

It doesn't matter if the solution is publicly available - if their interview process is based on the assumption that the candidate is completely unaware of the problem, this method neglects the (more common) case of a candidate asking other people in her network who've interviewed at Airbnb what happens in the interview.

In the interviews I've done, I have actually had a recruiter (Robert Half Technologies) ask the candidate about the interview, the candidate discusses my coding challenge with the recruiter afterward, and then the recruiter made sure all other candidates knew of the problem long before my interview so they could be prepared.

My solution has been to have a multi-stage problem that shifts in an unexpected way - if from the 1st stage the candidate anticipates my "plot twist" I end the interview because they've been caught cheating (think "Design a car" and then later "turn this car into a boat" - if from stage 1 the car has boat-like tendencies, they're cheating.)

You're right, my title was a bit sensational. I softened it a bit by appended mod_cgi. I think it is very telling that the PHP core recognizes that the people using mod_cgi probably can't upgrade so they're offering a .htaccess adjustment - very commendable.

There have been Windows installers for quite a while: http://gimp-win.sourceforge.net/stable.html You'll see the 2.6 stable is available at the top and 2.8 RC1 is at the bottom (I'm guessing 2.8.0 will be up by week's end.)

This project was recently discussed on HN at http://news.ycombinator.com/item?id=3899829

It may not be a big market that the masses are clamoring for, but it will soon be similar to services encrypting passwords in the database. The outside world shouldn't be expected to know about the existence of rainbow tables and the futility of md5-hashes. The educated, however, know what to demand, will expect their services to offer it, and will leave lacking-services for support-services - and in their exodus the masses inevitably follow (e.g. Hotmail -> GMail)

An excellent recruitment program to find talent for their own projects.

The comments in this post really demonstrate the widespread pain points that everyone has when dealing with CSS sprites, and the existence of 30+ solutions indicates that nobody has really figured out how to fix it yet.

The lack of attention to SVG stacks (http://simurai.com/post/20251013889/svg-stacks) is very curious to me - being a proponent of this method/movement seems analogous to being pro-PNG in the era of GIFs.

Is this different than the Dabble that TechCrunch covered in 2006: http://techcrunch.com/2006/07/23/dabble-launches/. Looks very different (platform and project concept), but the similar name makes me wonder if the same team was behind both.

Much more interesting is the link to their complete styleguide - http://www.starbucks.com/static/reference/styleguide/

That depends a significant amount on if you're interested in the "I want to work for company X" crowd.