Arve

Apple's approach goes a fair bit beyond simple servo control (which only tends to work well for truly low-frequency content.

While Apple hasn't disclosed much about the particular details, it's bound to be in the same vein as Klippel's work, which doesn't use feedback as much as it monitors a few states as input to a feed-forward error-correcting mechanism. The net result is that distortion is lower, and it's much less limited with regards to the frequency range you can support.

[1] http://www.audioxpress.com/article/louder-faithful-and-consi...

[2] https://www.klippel.de/fileadmin/_migrated/content_uploads/A...

Someone pointed out low-pass filters to you, but that's not the entire story. Built-in speakers in phones and laptops generally don't have a naturally extended frequency response.

A while ago, I made audio measurements of the built-in speakers on the iPhone 7 Plus - https://imgur.com/gallery/DRbu5

The iPhone's extension is not entirely atypical of such devices, and leaves you with a reliable passband of 500 Hz to 10 kHz - above and below those frequencies, you're getting too much noise.

If you're airgapping with audio cables, you'll have a reliable passband of 20 - 20 000 Hz or thereabouts, with some caveats for built-in audio on devices such as a Raspberry Pi that fizzle out at 15 kHz.

As noted by brian-armstrong's comment, you'll only get reliable near-ultrasonic airgapping over a wired connection.

Agreed. I have used the optical drive on my MBP exactly once, to verify that it worked.

    > None of the articles I nominated for deletion had any reliable sources to back them up

You didn't look very hard, did you?

For instance, the Alice ML homepage lists an entire page of papers. http://www.ps.uni-saarland.de/alice/papers.html - including nine thesises at various levels, something that wouldn't happen to something non-notable.

For Nemerle, Google Scholar has 81 results, http://scholar.google.com/scholar?q=nemerle&hl=en&bt...

This feature didn't exist last month -- it was added publicly on november 17th, in other words two days ago.

GMail failed in a number of the Opera 11 alpha builds and snapshots because our native implementation of Function.prototype.bind was broken. This was recently fixed.

It's also worth pointing out that we recently added a preference for enabling click-to-play for plugins. Open this: opera:config#UserPrefs|EnableOnDemandPlugin url in the browser, and check the box.

The point here is that the rotation is done by the OS, in software, so the screen is still painting from the physical left-to-right and top-to-bottom. This is something you'll never notice with the naked eye, but their camera uses a staggering 2700fps. This means that a full repaint of the screen - assuming 60Hz refresh happens in 45 frames. Those 45 frames, played back at 30 fps means that the full repaint takes a second and a half, leaving you with the ability to see the individual lines being (re)painted.

No. If you read the description of the chrome video, you'll see that they turned the LCD upside down to remove a shadow, and used software rotation in Windows to turn the display back around. The exact quote:

Chrome actually paints the page from top to bottom, but to eliminate a shadow from the driver board, we had to flip the monitor upside down and set the system preferences in Windows to rotate everything 180 degrees, resulting in the page appearing to render from bottom to top.