An hour account, his account was marked dead. Now it's not.
2,083 karma · joined October 16, 2011
[Disclaimer: I'm an EIR at Sequoia at the ripe old age of 46]
Not kidding, I think that'd be a cool name.
Word Mark: HOLDEN
Goods and Services: IC 025. US 022 039. G & S: clothing, namely, jackets, sweaters, sweatshirts, pants, t-shirts, shirts, vests and outerwear, namely, snow pants, snow jackets, snow suits, insulated and thermal pants, jackets, and shirts; headgear, namely, hats, caps. FIRST USE: 20020000. FIRST USE IN COMMERCE: 20020000
"I first thought the calibration was off and tried selecting Jill Stein to actually highlight Obama. Nope. Jill Stein was selected just fine. Next I deselected her and started at the top of Romney’s name and started tapping very closely together to find the ‘active areas’. From the top of Romney’s button down to the bottom of the black checkbox beside Obama’s name was all active for Romney. From the bottom of that same checkbox to the bottom of the Obama button (basically a small white sliver) is what let me choose Obama. Stein’s button was fine. All other buttons worked fine."
Google got the translation right first try, and the first result, which returned in less than a second, had "over $20 billion in damage" visible.
Siri took ~8 seconds to return "Ok sports fans, the Hurricanes appear to be in first place in the Southeast right now" followed by AHL team standings.
Apple has a lot of catching up to do here. They're going to have to start translating client-side, which Google has obviously figured out, and they're going to need a data source as rich as Google. It think the first part will get done at some point, but how will they match Google on the data side?
They should buy a wildcard cert for *.comcast.com and be done with it.
2:20 PM PDT We've now restored performance for about half of the volumes that experienced issues. Instances that were attached to these recovered volumes are recovering. We're continuing to work on restoring availability and performance for the volumes that are still degraded.
We also want to add some detail around what customers using ELB may have experienced. Customers with ELBs running in only the affected Availability Zone may be experiencing elevated error rates and customers may not be able to create new ELBs in the affected Availability Zone. For customers with multi-AZ ELBs, traffic was shifted away from the affected Availability Zone early in this event and they should not be seeing impact at this time.
12:07 PM PDT We are experiencing elevated error rates with the EC2 Management Console.