1,211 karma · joined July 17, 2010
I can put it up to my face (it's already on, because I can leave it on for days), frame, focus, and take a picture in less time than most phones can even turn on. That and, just as important, it never lights up or beeps at all (except for the memory card write LED).
The heliopause is a pretty reasonable way to define the edge of the solar system. A stated goal of the Voyager mission is to search for the heliopause boundary[2]:
Both Voyagers are headed towards the outer boundary of the solar system in search of the heliopause, the region where the Sun's influence wanes and the beginning of interstellar space can be sensed. The heliopause has never been reached by any spacecraft; the Voyagers may be the first to pass through this region, which is thought to exist somewhere from 8 to 14 billion miles from the Sun. This is where the million-mile-per-hour solar winds slows to about 250,000 miles per hour—the first indication that the wind is nearing the heliopause. The Voyagers should cross the heliopause 10 to 20 years after reaching the termination shock.
That having been said, this is a poor title. The news is not that the spacecraft has simply crossed a boundary. The news is that the boundary, until now unknown, was discovered (potentially).
The difference is "Ship successfully crosses Atlantic Ocean" vs "Columbus discovers New World". Perhaps a better title would be "More evidence that Voyager 1 has found the heliopause, considered to be the edge of the solar system".
----
[1] http://en.wikipedia.org/wiki/Solar_System#Farthest_regions
http://slashdot.org/story/99/12/25/114201/microsoft-hotmailp...
I'm sure the deal takes into account legacy devices, but I wonder how long that extended support would last.
That would mean the iPhone, the iPhone 3G, and the original iPad (none of which support iOS 6) will lose all mapping ability starting next year. Unless, of course, Apple backports their maps app to iOS 5 (and even that wouldn't help original iPhone users--if there are any left).
You can be asleep (I tend to fall asleep before takeoff). You can drink quite a bit of alcohol in the airport and on the plane. You can take a Xanax. You can be deeply into a sudoku puzzle, a book, or a conversation. You can even wear earplugs and an eye mask!
I'm pretty sure my attentions can turn to the emergency at-hand just as quickly if I'm playing Angry Birds or I'm reading a magazine.
Also, you can just specify your own encryption key. Everything is encrypted locally.
In AF447, one of the pilots had a nose up input held during a stall. Because the other pilots couldn't see his stick, they weren't aware of his inputs. Also, at certain times, the other pilot was giving contradictory (nose down) inputs to the aircraft. This input was averaged (read: canceled) with the other pilot's nose up input.
The side stick has two problems: 1) Lack of awareness of what inputs are being given to the plane by other pilots in the flight deck. 2) The computer has to make decisions about how to resolve contradictory inputs.
Edit: Misread your comment...the bytes at the beginning of the file are hidden by CSS (as pointed out by others).
In the single datacenter that did not successfully transfer to the generator backup, all servers continued to operate normally on Uninterruptable Power Supply (“UPS”) power. As onsite personnel worked to stabilize the primary and backup power generators, the UPS systems were depleting and servers began losing power at 8:04pm PDT. Ten minutes later, the backup generator power was stabilized, the UPSs were restarted, and power started to be restored by 8:14pm PDT. At 8:24pm PDT, the full facility had power to all racks.
It sounds like they were too optimistic about their generator startup times.
You'd be much better off using ARIA (which has pretty broad support from browser vendors and assistive technology vendors):
<span class="icon" aria-hidden="true">Facebook</span> Facebook
<span class="icon" aria-hidden="true">Twitter</span> Twitter
This keeps assistive technologies from rendering the text (not just screen readers, but Braille displays, etc).Put another way, if I'm Microsoft, can I put my website at http://microsoft? Or do I have to use http://www.microsoft?
I've looked to see if there is a policy from ICANN on this, but I can't find one. Historically, TLDs did not themselves point to hosts (or have other things like MX or TXT records).
Can I assume that my Availability Zone us-east-1a is the same location as someone else's Availability Zone us-east-1a?
No. Currently, we do not support cross-account proximity. Each account's Availability Zones are independent. For example, the us-east-1a Availability Zone for one account might be in a different location than for another account.
http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/FA...
The delay is there to allow you lift your finger and see the link turned gray (or whatever the selection color is). This feedback is crucial even in cases where you tapped on the right thing--how else would you know you got the right thing?
There are valid reasons to override this, but developers and designers should be sure that their tap targets are huge when they do. Otherwise they're depriving users of a pretty important piece of feedback.
75.75.75.75
75.75.76.76
2001:558:FEED::1
2001:558:FEED::2
In fact, any CO-OP Network ATM works just as well as my own CU's ATM (no fees, deposits, etc). They have locations nationwide, as most credit unions are members.
Edit: also included in that list: most ATMs at 7-Eleven.
75.75.75.75 and 75.75.76.76