evandavid

+1 recommended reading for "In Defense of Food". It's way outside my regular reading tastes (pop-ish science + nutrition related), but I enjoyed every moment of it, and it's definitely changed the way I think about eating.

You could still keep a record of all calls made, and the tower(s) used to make each call, without getting down to this level of granularity. I might be wrong here, but it seems that they're storing a stream of triangulated location data for a given handset, regardless of the actual network activity like calling.

Let's say that the carriers only stored call records with tower IDs for each call. If there was a dispute every so often because a call was made on a close-by tower that itself happened to be located in a different toll bracket (resulting in an incorrect overcharge to the customer), I'm sure the carrier would happily write off that charge if you disputed them about it, which is probably what they'd do right now anyway.

There must be another reason they're keeping it, even if it's just a case of it being super-cheap to store, and they think that they might figure out something to do with it later.

I'd also like to know whether this information can be or has ever been used in court as evidence. "Where were you on the night of such and such...?" may become a question of the past. Frightening.

Thanks! Moving to San Fran in 2 days (from New Zealand). Hopefully there's some useful stuff in there.

The new layouts for both gizmodo & lifehacker seem quite buggy to me (Mac, latest Chrome). Most obviously, there is a grey line that tracks its way up the screen as I scroll past 'the fold'. And I agree with earlier posters: user test before release (qualitative), and split test as part of the release (quantitative).

I think the better all round solution (in terms of privacy, functionality and maintenance) is to go with a free private git hosting provider like assembla.com. I have tried both the dropbox solution as well as setting up git+ssh on a vps, and assembla is now my goto for personal and side projects.

Haha. Make that three.

I like the idea. I have two quick questions:

- what happens when my site is experiencing issues and you receive massive volumes of complaint/problem emails

- how do I continue to integrate support in our product/feature management workflow, to ensure that the voice of the customer is heard?

- are you hoping to introduce phone calls and other support methods?

Thanks!

Fair. Would you feel the same way about a web application, as opposed to a content-heavy site?

Not trolling. But I admit that I'm overstating my position a little bit to see if any interesting discussion comes of it. The reality of my current situation (a one, sometimes two person team) has meant that I have indeed been following the convention I just described. That's not to say I want to, but as I mentioned, I will probably continue to for the foreseeable future without too much hesitation.

For the time being, I will personally continue to build #!-only websites, designed exclusively for javascript enabled browsers. Maintaining two versions (along the guidelines of progressive enhancement) is just too much work (maintaining and testing html view templates as well as jQuery or moustache templates) considering that so few people lack javascript. I wouldn't let a release go live without running a selenium suite across it in any case. My perspective would be different, I imagine, if I worked on a large team that could 'afford' to take the progressive enhancement route.

I worked in Biometrics for a few years. I was on a fingerprint team, but I was part a wider team that was also responsible for forensic-quality facial recognition technology (a world leader). To put it bluntly, the technology is still very, very, very weak. When it works, it's really impressive, but that's normally during a demo from a nicely curated database. There are some facial technologies that can "work" from a distance (and they are used in airports already), but the success rate is low and the original image still needs to be of decent fidelity. Often times the results from the automated matching will be shortlisted for comparison by human operators. Maybe I was blinded by the awesomeness of fingerprint technology (still blows my mind thinking about it).

Combine this general lack of automated matching awesomeness with the fact that people age, can wear glasses or a beard, etc, and we are still many years away from this kind of capability.

Still, it's always fun to think about the possibilities that biometrics can and will provide.

I'd also like to hear some pragmatic CSS professionals weigh in on this topic. From what I've seen so far, I agree that some of the resets are over the top, but I'm not sure whether the opposition to them is a result of purism over pragmatism. I really just want to speed up CSS development...

Requires a Linkedin profile to sign up!? Really!? There are so many reasons that is a stupid idea.

For people who can't remember if they ever signed up:

Go to gawker.com and use the 'forgot my password' utility. It's under login > forgot my password. Enter your email address in the field provided. It will tell you straight away "That email address is not in our records. Please try again."

I can't think of any reason this would be incorrect based on the recent events. Of course, this doesn't tell you whether your password is vulnerable, just whether you have an account.