Using the above bookmarklet will archive the entire page in the Internet Archive immediately (timestamped by the Internet Archive). The Internet Archive crawler respects robots.txt, but it doesn't appear the Flickr robots.txt file will prevent you from using this method.
Not 2^16 (Unicode already has way over 2^16 codepoints assigned). The maximum Unicode codepoint value is 1114111, which is somewhat over 2^20 (and happens to be the highest codepoint encodable in UTF-16).
They're nothing to do with nuclear test monitoring, they just happened to use data from the monitoring network to count the number of kiloton scale events in the last decade or so.
The B612 Foundation is a non profit organization trying to raise money for a asteroid discovery spacecraft, a telescope that will sit down near Venus's orbit and look outwards, enabling it to see asteroids near earth without the sun dazzling the optics (half the asteroids passing near earth are invisible because they are too close to the sun). It's not an unreasonable goal when you consider that high profile museums and educational institutions regularly raise hundreds of millions of dollars in donations.
GoGo is provided by a company called Aircell, out of Itasca, IL. They rely on a network of ~400 AT&T cell tower locations to provide connectivity (its all interconnected over MPLS). Row 44 is a competitor, and they use satellite connectivity, and hence can provide coverage over the ocean or international countries.
Not all relevant info, but thought I'd throw it out there.
It's 2Ah, so 240A.
Now, it could be that their battery runs at a higher voltage (and thus not really 2Ah, but they're using that figure as a 3.7V li-ion equivalent capabity), or that there is a power converter built into the battery pack (unlikely for a prototype, though). Still, even for a 37V battery (vs. 3.7V for a normal Li-Ion cell), we're talking 24A. That cord didn't look like 24A cord, and I highly doubt they were using a voltage higher than 37V to charge (especially not with exposed banana jacks like that).
I call the demo highly dubious if not an outright fake/mock.
Sorry for the threadjack, but this is yet another case of horrible security reporting.
From watching the video, what it seems happened here was that eBay chose phpBB for their community forum, but did not integrate its authentication system directly with eBay's on the server side. Instead, the site was set-up as a standalone system, and whoever implemented the integration had the bright idea of hardcoding the forum password for everyone as username+123456, and then just having the eBay login page issue a hidden POST request behind the scenes to authenticate users to the community forum section.
Thus, this allows anyone to trivially impersonate anyone else on the forum. It shouldn't have anything to do with the rest of the site, though. Nor does this have anything to do with initial passwords, salts, or any of the other terms that have been thrown around.
A case of absolutely retarded login integration for the community site, but not something that would allow people to take over others' main eBay account. What this says about the people running eBay is another matter entirely...
Telematics (like OnStar), over the air software updates, etc.
OnStar from GM is something like $300/year. To get that same level of control, plus all service included, for $600? Sign me up.
You are not the target market.
$600? For you to come pickup the car and give me a loaner? And do over the air software updates? And provide telematics like OnStar?
Shut Up And Take My Money. (I make ~$150K/year, $600 is only a couple hours of time)
Did you actually read that article? It clearly describes exactly what I said: they use resistors on the data pins to signal the available current. There is no bidirectional negotiation going on. There are no extra pins or wires. The charger just has 4 resistors to create two voltage dividers for the D- and D+ pins.
This is incorrect. There is no bidirectional negotiation between chargers and devices, nor are there any magic extra pins (at least for pretty much all Android and Apple products - dunno about Zune).
What there is is one USB charging standard, that basically says one thing and one thing only (that matters): if the data pins are shorted together (but otherwise not connected to anything), then the port is a Dedicated Charging Port. A DCP must meet certain voltage/current curve ranges and may be engineered to supply anywhere from 500mA to 1.5A (or more), with the voltage dropping as the device exceeds the charger's maximum. Devices are simply supposed to regulate current draw upwards until the voltage drops below a threshold, indicating the charger's capability. No digital negotiation takes place. Devices are limited to 1.5A charging current, which is quite typical for modern devices (and significantly better than the 500mA of a non-charging port).
There is a newer USB Power Delivery specification that is much more recent, supports higher powers, probably uses more complex negotiation (I haven't read it), and nothing implements it yet.
Then there's what Apple does - they have an incompatible implementation that uses resistors on the data pins in the charger to signal its current capability. Different resulting voltages mean different current levels. This is completely incompatible with the USB charging standard. Recent Apple devices (since the iPhone 3G or so) do support DCP chargers (to some extent - some charge more slowly, and I don't know about larger iPads?), but non-Apple devices will only charge at 500mA or worse from Apple chargers.
Not paying for the damage you do to the water and the air is a subsidy.
The human brain doesn't fully develop until 25. We don't even hold teenagers responsible for their actions until they're 17-18.
This is false. Decoding for modern video formats is strictly defined, and all decoders must produce bit-perfect output. You can add as many filters as you want after that, but that's a postprocessing step in the video player and has nothing to do with the decoder. Things like in-loop filters are strictly defined as part of the decoding process and must be there for the decoder to be considered correct.