FWIW, clicking on that link with Safari showed an unexpected popup: "WebProcess wants to sign using key "Apple ID Authentication [timestamp] in your keychain". Using some sort of client cert for SSL? I didn't find an obvious reason for the interaction.
I'm glad to see Jawbone going for broke on the 'health and wellness via data' front. I've been a fan of their design language and technical chops since back when their headsets had wires.
My wife has been 1k for the last several years. Before we met I had no concept of mileage programs but traveling with her has really opened my eyes.
The funny part is at some point it feels a bit like playing a Zynga game, including the occasional "screw it, I'm so close I'll pay a little cash to bump up to the next level"
The folks who strolled in earlier might have more status (miles/revenue) on this airline, and having that means a great deal to the airline's systems and humans. They know what you're worth to the company and whether it's worth bumping someone else lower on the totem. It doesn't feel good but it's generally pretty rational.
Nitpicking, but on my Safari 6 this page doesn't render properly because I have 'Default' encoding selected. The page is authored as UTF-8 but doesn't declare that in the content-type header, doctype, or a meta tag.
This thread is pretty cold by now but I wanted to thank you for the link to Ignition — it's a really neat window into some of the chemistry and practice of 20th century rocketry. Reminded me of Max Gergel's "Excuse me sir, would you like to buy a kilo of isopropyl bromide?" http://library.sciencemadness.org/library/books/gergel_isopr... which, now that I look at the link, is hosted at the same server.
This reads like satire — I mean it's a clever idea but I feel like it falls into the 'too cute' category, subject matter aside. Will be curious to see a follow-up as to whether it worked, was a disaster, or turned out to be a hoax or publicity stunt.
This seems like a neat feature but it's also painfully slow. Is that normal or is the dashboard under unusual load? Mysterious slowness seems like a recurring theme on Heroku.
Hope the Twine ships eventually, it's such a slick solution. A few years ago I wired up my office basil plant to a moisture sensor so it could post to its Facebook page (Basil Green) when it needed watering. Being tethered to a computer was sort of overkill since the real data rate was three or four bits per day.
This feels like a pretty standard pattern for a lot of services — fail, come back up on backup DB, fail again when backup proves to not be capable of handling the surge of load, then eventually come back up on the primary DB once people have gotten bored and stopped hitting 'refresh'.
Is that a function of not prewarming failover DBs, or is there something pathological about the primary-secondary pattern?