The only thing about this story that keeps people in Cupertino awake ist the simple fact that people could use this vulnerability to reset the charge counter of the battery and try to file a warranty claim.

Sadly. that's not the case.

• (1) No liability for taking down generally. — Subject to paragraph (2), a service provider shall not be liable to any person for any claim based on the service provider's good faith disabling of access to, or removal of, material or activity claimed to be infringing or based on facts or circumstances from which infringing activity is apparent, regardless of whether the material or activity is ultimately determined to be infringing.
• (2) Exception. — Paragraph (1) shall not apply with respect to material residing at the direction of a subscriber of the service provider on a system or network controlled or operated by or for the service provider that is removed, or to which access is disabled by the service provider, pursuant to a notice provided under subsection (c)(1)(C), unless the service provider —
  • (A) takes reasonable steps promptly to notify the subscriber that it has removed or disabled access to the material;
  • (B) upon receipt of a counter notification described in paragraph (3), promptly provides the person who provided the notification under subsection (c)(1)(C) with a copy of the counter notification, and informs that person that it will replace the removed material or cease disabling access to it in 10 business days; and
  • (C) replaces the removed material and ceases disabling access to it not less than 10, nor more than 14, business days following receipt of the counter notice, unless its designated agent first receives notice from the person who submitted the notification under subsection (c)(1)(C) that such person has filed an action seeking a court order to restrain the subscriber from engaging in infringing activity relating to the material on the service provider's system or network.

And if that doesn't help, there's certainly something in youtube's terms and conditions that they can host or not host anything they want at any time they want for any or no reason, and that it is your own fault to rely on their services. I'd expect their liability to be limited to what you pay them for hosting your content, some very low symbolic amount or just plain nothing, whichever they can get away with in the relevant jurisdiction.

There's about 1kW of photons centered around the visual spectrum hitting every square meter of the moon. It's very difficult to detect a measly laser among all that noise. In the radio spectrum, it's much easier to get a few kW of transmit power, and there's not all that much natural noise, so the signal is much easier to detect.

If you want to know how hard it is to bounce a laser off the moon, read up on the Apollo Retroreflectors, where "Even under good atmospheric viewing conditions, only one photon is received every few seconds".

There was a crash bug in linux quite some time ago (around the 2.6.18 timeframe, CVE-2006-4145) involving large files on UDF filesystems. The workaround fomr 2.6.18 on was a hard limit of the filesize on UDF filesystems of only 1GB. This limit was still around when I last tried to create a UDF DVD filesystem, but that was 1-2 years ago. Is this limit still in current kernels?

My experience from 1996 is quite the oppiosite. I bought a S3 964 based card after those were on the market for more than a year, and I had to find that XF86 was running in false-color so to say. S3 sent me the printed programming for free by international airmail essentially no questions asked.

It turned out that the problem was the way the external IBM RAMDAC was wired to the S3 chip - easily fixed with a 2 or so lines patch, Back in those days manufacturers of graphics cards dodn't just implement a reference design, but had lots of choices which components to connect in which way, which didn't really make things easier for open source developers without access to every hardware variant out there.That essentially ended with the S3 Trio/Virge and the ATI and NVida 3d cards.