aes's comments

Just from looking the code it seems pretty sloppy, not what I would expect from security sensitive code.

Mixed tabs and spaces, inconsistent indentation, two empty lines in a row, sometimes "if (...)" and sometimes "if(...)".

Jewelry.

A human-friendly JSON-like serialization format.

Time permitting, a simple bitcoin gambling site.

Time permitting, a really easy way to do microdonations.

>> "Especially for common workflow tasks like switching from an app to 1Password and back to the app."

> Use the task switcher, which is now much faster than before?

This was actually one of the "Wow! They've thought about the little things" moments on iOS7. I was copying a phone number or an address from another app, and with the new task switcher I didn't even have to launch the other app since the information I was looking for was already visible from the switcher.

Let's see...

No HTML allowed - ok - I just don't buy the explanation. A better way to sell it would be "A 100% secure Markdown clone you can use on the web with no questions asked, no HTML injection possible because no HTML is possible."

When I see a Markdown clone I expect to see some new features: modularity and extendability, a well-defined grammar or translation process (if that's even possible without sacrificing usability, simplicity, or performance), perhaps being exceptionally fast. And I keep looking, because the world needs a better Markdown. Unfortunately, a feature removed from Markdown and a few others slapped on top of it is not enough to make me try it. So I wish you good luck with your project and hope that it evolves beyond that.

And ThinkPads used to have a fingerprint sensor, many years ago. It's not that the technology itself is very cutting edge, or even claimed to be. (Of course, marketing claims anything to be cutting-edge. Apple's marketing doubly so.)

In the light of recent knowledge, it makes me wonder whether IBM had NSA backdoors, too.

They don't even say fingerprints are not uploaded:

According to the press release, "fingerprint information [...] is never stored on Apple servers or backed up to iCloud." But nowhere do they claim it doesn't ever leave the phone. It looks like this leaves Apple the option to upload the data to "trusted partners".

http://www.apple.com/pr/library/2013/09/10Apple-Announces-iP...

Assuming the phone isn't locked.

A combination with email confirmation plus two-step verification like Google Authenticator could work as well.

1. Writing a blog post about this - good

2. Naming and shaming the company - better

3. Quitting your job and letting them know about it - even better

Here's a data point for you:

For me, the text on that article felt way too big when viewed in a full screen browser on a 1280x800 display. Frankly, it's about as bad as if the font-size were 12px or 13px.

Resizing the browser window to only take half of the screen width makes it better on my eyes (it appears to be 17px). Still, after that, I felt the need to go to developer console and change line-height to 1.4.

I chuckled a bit when, after these adjustments, I arrived at the sentence:

> The fact you’ve read to this paragraph is proof that there is something to my argument.

I'm on a 13" Macbook Pro, and lying on a couch, so my viewing distance may be a bit closer than if I were sitting on a desk. I'm 33 years old, with relatively ok eyesight (no glasses), and totally buy your other arguments (I'm a fan of Bringhurst myself).

It's just that anything more than 18px on a laptop display just feels too big.

Ok, you'll have to run it through the compiler first with the -m option:

test.coffee:

  require 'source-map-support'
  throw new Error("Test")

Now do:

  npm install source-map-support
  coffee -c -m test.coffee
  node test.js

This gets you the correct line numbers.

So is there a way to use the source maps with node.js stacktraces?

Specifically, I tried this test.coffee:

  throw new Error("Test")

Now running it with

  coffee test.coffee

still reports the wrong line number in the stack trace.

There's supposedly node-source-map-support (https://github.com/evanw/node-source-map-support), but even installing that and adding "require 'source-map-support'" won't help.

I tested this on my @me.com account, and it's exactly how it works. Email containing the words "barely legal teens" is simply dropped.

I find it obscene to an Orwellian extent that Apple actually seems to think that no valid email would ever contain the words "barely legal teens". I wonder what other things Apple thinks are not worth talking about?

I have no trust in Apple's email services any more.

Not really; as they say in the post itself, "Facebook’s business is different than Amazons and the impact on their business will be different."

Amazon's core business is selling stuff to customers: additional latency might occasionally turn away a customer. In Amazon's scale, that's a million-dollar opportunity.

Facebook's core business is having users click on ads: at first, latency's role there might seem insignificant, but it is an interesting intellectual exercise to figure out whether it really matters in Facebook's scale.

Even more interesting would be if you had some data to show precisely how much.

On an iPad, the experience seems to be identical to using http://here.net/ in Safari. So this is not particularly big news.

Funny, I was just reading this on an iPhone and it's completely legible (even in portrait mode).

Nifty project.

But I have hard time believing that there still are web providers that don't support SSH. Are there any? Good ones?

Gizmodo's Apple coverage has been quite tasteless for some time now. Not much value in this article.

As also covered here http://www.powerpage.org/2012/09/27/apple-files-patent-for-i... and here http://www.pt-news.org/apple-inc-aapl-patent-shows-inductive...

If may be strange because of the asymmetry but I'd actually prefer `if` to be come first all the time and `unless` to come last all the time - precisely because `unless` reads like it's for exceptional circumstances:

  value = cache[key]
  if value?
    return value

  return file.readContents() unless not file.exists()