Googling around...
Apparently the story about this teen has been reported in the Washington post (among other).

I would have thought instead that this was straight out of Bruce Schneier's Movie Plot Threat Contest

External camera following the DoA girls ?

I see where this is going...

Unlock the special "colibri" mode and fly around following your team to the showers after a play !

It was all snowden's work along!
He stole the data for the sole purpose of giving to Russia and China!
He's an evil communist traitor that needs to be put on an electric chair!

The recent breach by China are just purely coincidental!

Also there's no way that Russia would the resource and know how to obtain such data, and they had to rely on a lone consultant instead of their mighty KGB/FSB !

First person ? Dead or Alive ?

You mean risking to get hit in the face by your (avatar's) own oversized breast due to jiggle physics turned up to eleven ?
That surely is going to be a wonderful first-person experience.

Hence the clamp-attachement-thingy that is on nearly every single wheel I've seen, and that's clearly visible on lots of the picture on Logitech's official website.
They even have a paragrph about mounting it securely.

To simulate the steering wheel of an actual real-world everyday car. You know, the things which got equipped with "Power Steering" for the past few decades, and which you can almost steer around with a single finger. :-D

("Reality Is Unrealistic" trope again).

(Well I get the point that the "racing wheel" are for playing car racing games, which simulate cars with differently configured steering column.
But still, a steering wheel with the forcefeed-back turned as low as possible is the closest thing to the normal car that you use to drive around)

I don't own this peculiar item, but all the Logitech gaming gear I've used (mostly WingMan joysticks) have a rather heavy-ish metal base, to keep it stable.

And all the steering wheels I've seen have special attachment to clamp/screw them on the table.

(See Logitech official page)

You would, but not necessarily all the shops you visit would too.
Welcome to the network effect !

PayPal is designed in such a way that both ends of the transaction (both the merchant and the client) must use PayPal as a payment processor.
Even if you decide on your own to switch, that won't have any impact on the merchant. If they don't switch, you'll be forced to keep PayPal to be able to buy from them.

Contrast the situation with SEPA payment in Europe:
You and the merchant are completely independent and free too choose a bank.
You can have your account at any bank of your liking.
The marchant can use any bank that pleases them.
As long as both banks follow the SEPA standard, you can do payment and buy your goods (with a couple of days up to one week delay).

Bitcoin (the protocol) was design partly to address the same problem:
you and a merchant can choose any payment processor or other source of bitcoin (the units) to do a transaction.£
The merchant could be using any payment processor that they would like (bitpay, coinbase, etc.)
You could choose instead to go for an exchange (BTC-e) or obtain your BTC by meeting someone face-to-face (localbitcoin) or even actually store them in a wallet (If you feel like gambling on the completely crazy unstable exchange rate).
As long as both ends of the transaction follow the bitcoin protocol, you're both free to pick any solution you like. You can do payment and buy your goods (with a couple of minute delay).

Note that it the meaning is still correct in topology, and the original meaning of the word when the english borrowed it from the french, before its meaning drifted appart.

What ads ?

I have both
- uBlock running
- and the Thanks again for helping make Slashdot great! box checked.

Sorry, I pay for my bandwidth, I don't want my money wasted on annoying flashing things trying to persuade me to throw money on goods that I don't give a fuck about (in addition to disrupting the flow and making the overall internet experience shitty).

Cue in 1/3 of slashdot complaining that *JavaScript* is the wrong language to start with, cripples the mind, doesn't offer enough opportunities, isn't present enoug in corporation, or in github, or isn't hype enough, etc.
With everybody instead try to convince that they should better start with Python / Perl / Ruby / Java / Scala / Haskell / Erlang / various shell scripts / SQL / PHP / Objective-C / LISP / C / C++ / Rust / Go / C# / Assembler / BrainFuck ....

Curiously none of the complaining slashdoters will suggest VisualBasic or Cobol.

Not exactly. PNaCl plugin run in a restricted sandbox, they are severly limited into what they can execute and which API they can call.
That's not the case with NPAPI: an NPAPI plugin can basically call any API it whishes (e.g.: call the OS's media API).
The closest thing to PNaCl in the Firefox world isn't NPAPI, but ASM.js, that two only runs a very limited set of API (e.g: only use WebGL) and is restricted to what it can do.

Saddly, a lot of the Java applet aren't actually "write-once run everywhere" as Java was intended to be, but rely on native libraries that are packaged together.
(This is also is the reason why some popular Java applet won't run easily on Linux 64bits without some tweaking).
These external DLL/so are clearly out of what the PNaCl model authorises. You can't do a PNaCl-port of Java instead of NPAPI and keep such functionality.

And such thing are really popular in the corporate world:
- Cisco's WebEx conferencing platform - which is immensely popular in the corporate world - relies on native libraries (.DLL or IA32 .so) for all media access.
Without it, all you're left with is using a phone connection to the conference, and you miss screen sharing/webcams.
- Several VNC plug-ins use similar native libraries for low-level access - (including popular ones to remotely admin servers from the lights-out web console)
etc.

All these won't require a simple recompile.
They would require that :
- Java gets ported to PNaCl (or the apps themselves get re-compiled targetting PNaCl instead of JVM).
- Extra functionality that the applets pack into external .so files gets rewritten from scratch to be able to used from within the restricted context of PNaCl.
(That would be great. It means less risks of hacking as everything fits within the PNaCl restrictions, and also as PNaCl is bytecoded, you get tweak-less support for x86_64, ARM, etc.)

Or:
- rewrite the whole functionality from scratch using HTML5/Javascript and using modern API.
(Even better in my taste).

What will probably happen:
- Internet is back as the corporate standard, because 2/3 of all the used business App (like most of the things running on Java in the corporate world) aren't straight recompiles.

And I might add: easier for such (relatively) smaller islands like Hawaii which can't afford lots hydroelectric dam due to limited amount of mountains (compared to the Alps here around, or compared to Japan)

I'll group the answers.

Well, you need to stick needles into the body quite big and deep to have a good contact (the probes mentioned in this Darwin award). And apply a sufficient voltage to them, for a long enough time. That's quite a convoluted way that doesn't happen in every day life.
(I hardly see example how it could happen, except deliberately as in the example).

Generally speaking, yes, I agree. A healthy heart should restart.
That's in fact the principle which is used by defibrillators:
- a firbillation: is a big electrical mess where the cells a completely desynchronised and are firing mostly at random each triggered by the mostly random fires of their neighbours. Electrically, the heart gives a signal that looks like white noise. Mecanically, the heart isn't beating in a coordinated manner, but instead its surface is more or less kind of "vibrating" making tons of small uncoordinated local micro-contraction (that's what fibrillation means).
- fire a charge a the heart
- the charge cause all the muscle cells (and the specialized muscle cells that serve as the heart's equivalent of nerves) to contract at the same time and stay contracted for the short duration of the charge.
- after the shock, most of the cell are more or less at the same position in the cycle. (and thus none will start miss firing due to other nearby miss-fires). They are more or less in "waiting state".
- natural rhythm generator generates impulse as usual, and now all the cell should follow the same impulse travelling along the heart (and its nerve-like specialised fibers).
- heart should contract in a coordinated manner and beat as it should.

BUT....
In the Darwin awards example, the current is constant. Which doesn't cause a "resync" as the single pulse that a defibrillator's shock is. Also, given the low resistance of the salty water medium, the current is probably quite high which is dangerous. (I mean relatively speaking).
There's a much higher risk of the heart going into fibrillation in this case.

Of course adding some heart disease could increase the likely hood of dying.
But the absence of disease isn't a definite guarantee to die from such shocks.

Basically: you got lucky.

Probably the shocks where short. Or by luck the travel path of the current didn't happen to reach the heart (I've once had a thunder struck patient that survived exactly because of that: the heart wasn't touched).
The fact that you survived previous shock and the fact that you don't have a heart disease doesn't necessarily make you immortal and doesn't guarantee that you won't die next time.

That could very well happen.

The reason why low voltage isn't dangerous usually, is because the skin is a damn good insulator requiring voltage above 100v to break (one of the argument invoked by countries using 100volts, whereas the rest is 220v).

The Darwin Award example did stick needle-like pointy ends of the probe *through* the skin. The skin's high insulation/resistance wasn't there any more to shield against "insignificant voltage". The serum of the blood isn't distilled water but is filled with electrolyte. Quite conducting mix. It also runs through the hearth. The rest of the fuilds inside a body are all rich with electrolytes too. That means that the *inside* of a body can conduct electricity quite well, and the hearth can easily get in its path (specially if you put each electrode pole at opposite side).
(one of the reason why it's not a bright idea to swim during a storm. the inside of your body is a *better* conductor that the water around you in the swimming pool, the skin is the only thing in the way blocking the electricity).

The actual delta-V needed for a muscle cell or a nerve to react is quite low (a few dozens of mili-volts are needed to rise above the threshold and cause contraction or impulse propagation). So with the skin barrier removed, it's quite likely that the remaining salty fuilds (mostly blood, but also extra-cellular fluids) can carry enough to cause a jolt to the hearth, enough to disrupt the normal rhythm.

You can google around and find several tutorial explaining how to compile chromium with support for Widevine turned on (That's the DRM module used by Google Chrome to play the HTML5 EME/VIDEO streams of netflix).

Now the question is:
- are there Widevine binaries available for ARM ? (Not sure. I might remember having read somewhere about such)
- or, alternatively, can similar JIT emulator as TFA's one run the x86 plugin at a sufficient speed, while leaving enough processing power to handle the remaining of the video playing ? (Luckily, there's some hardware acceleration on the Pi, so maybe it's possible to achieve).

You could do the same using a Firefox compile with support for CDM plugins, and using the Adobe CDM plugin for Firefox.
(With the same limitation, either wait until Adobe does an ARM version for all the various mobile incarnation of Firefox, or hope that the plugins can be emulated fast enough).