That's why most places (at least around here) also screen for behaviours which could end with blood borne disease spreading.

i.e.: You can't immediately donate blood after having a tattoo done.
Even if you are HIV negative, there might be another unknown disease that could have spread from improperly cleaned tools.
Need to way some time (1 year) before starting giving blood again.
By that time you'll have started showing symptoms and/or news of a new blood borne disease will have been heard.

Not exactly "So like every other prototype "hoverboard", then"

This one uses magnetic levitation. (Thus works only over a steel surface).

The one from the kickstarter project uses magnetic induction (Thus works over any conducting surface).

Get a bunch of engineers, split them into groups, and pack each group in a different room.
Ask them something awesome like an hoverboard, and they'll come out with probably a dozen of different solutions, each with its own advantage and short-comings. Including levitation solutions that explicitly work over water.

They more precisley said :

Which is true.

Except that, recent firmware fixes from Samsung (you know, the whole "speed decay on aging data" fiasco) had suddenly started to falsely report support for TRIM+NCQ.

So it might be possible that unkowningly to them, their Linux installation has suddenly started to issue queued TRIMs, even if the drive actually don't support them, because it trusts what the firmware told to do.

Indeed, that right: Windows doesn't support TRIM+NCQ, whereas Linux does and will enable it if the drive reports it as present.

In this case it's purely accidental. Samsung issued a firmware upgrade for some Samsung SSD to fix a problem causing a decay of speed as data ages on the SSD. That new firmware happens to falsely report support for TRIM+NCQ whereas it doesn't actually support it.
It's a bug left in a new firmware fix, not a tweak intentionally designed to work around quirks and bugs in windows.

The bug doesn't trigger in Windows because windows doesn't support the feature. Linux (and BSD ?) do and are affected.

You're shielded from the problem because of 2 different things:

- Samsung 850 aren't as much affected by speed decay as Samsung 840. Thus a firmware fixing the speed problem was only shipped for 840s, not for 850s - and it's that firmware which had the problem. You drive simply didn't get the problematic firmware.

- That newest firmware falsely advertises that the drive supports TRIM together with NCQ. But the drive actually doesn't.Re-ordering should happen while TRIM is used.
Linux follows the standards: it asks the drive and only uses the feature that are advertised as supported. Because that specific firmware on that specific drive falsely reports supporting a missing feature, corruption happens.
Windows simply doesn't support TRIM with NCQ at all. The bug isn't triggered.

The current fix in linux is to put the drive on a blacklist and mimic Windows behavior by ignoring TRIM+NCQ.

So: The differences is that Linux uses TRIM+NCQ when instructed by the drive, whereas Windows doesn't. And your drive didn't happen to get the firmware that falsely report this.

it's not trim by itself that is problematic.
it's the combined use with NCQ (= reordering of commands).

The latest firmware (the one that fixes the speed decay) has started to falsely advertise support for this combination, whereas the drive doesn't actually support it.
The drive isn't actually able to re-order TRIM commands, and the wrong bit might end up being erased due to NCQ.

So this but will only show up:
- your drive is a Samsung 840 EVO (850 aren't affected by the speed decay and didn't get the faulty upgrade)
- if you have upgraded the firmware to the latest (faulty) version.
- you run an OS which is actually able to use TRIM+NCQ (Linux and BSD, basically)
- your OS also follows the standards (asks the drive what is supported and gets the false advertisement of TRIM+NCQ).
- you actually enable TRIM on the drive.

remove any one point of this chain and the bug doesn't happen.

Because the fix is relatively simple.

To put in general terms:
- The problem is that the drive advertises a bunch of features. Linux tries to use them. But the firmware is buggy and the feature don't work or aren't even implemented.
- The fix is to ignore any advanced feature even if advertised by firmware. Stick to only the small subset of features that are also used in windows.

e.g:
- the most frequent problem with trim is that the device advertises supporting TRIM with NCQ (= reordering of commands).
(the latest firmware for Samsung 840 EVO started advertising this in addition of fixing the speed decay).
Linux *can* issue TRIM together with NCQ. So when the drives says it does, it will start using it.
But the drives doesn't work with TRIM and NCQ combined. There's a bug in the implementeation, or the firmware doesn't even support it.
(no Samsung 8?? actually support TRIM+NCQ. It's falsely reported as present by the firmware).
- Windows (and perhaps Mac OS X) aren't affected by this because they don't support it to begin with.
- Linux fix is to simply ignore the falsely advertised TRIM+NCQ. It reverts to either use NCQ, or use TRIM in a blocking (slow) way.
And that is a permanent fix because is simply reverts to a behavious similar to windows. No new problem should arise in Linux because it simply mimics the behaviour of Windows. If anything was still broken, it would be affecting Windows too.
It will work against any version of the firmware (Linux isn't tricking the firmware or trying to compensate. Just plain ignoring missing features).

Of course, the best would be to use 100% standard compliant SSD.
But reality is that not much *are* actually standard compliant.

So unless you're ready to shell lots of money for some actually enterprise-grade SSD,
accepting SSD with patched support is the next best option.

Which is specifically NOT the modus operandi of the majority of viruses aroudn (except a few like Stuxnet which had very specific targets).
Thus this would require writing custom code to address this very specific and unusual configuration.
So who's going to throw the ressources at writing a completely new virus specifically targetting the few movie sharing sneakernets around the world ?

As the poster above has noted: nobody. Nobody gives a fuck about Cuba and other such sneakernets.

There's no point in getting these machine or the data on them.
It's not worth blackmailing them. The cuban will probably earn even less money than the chinese guy who would have written the USB-transmitted ransom ware.
It's not worth trying to own the machine: you can't use it for DDOS nor Spam nor some alt-coin mining.
Whatever data they have probably concerns goods and money that are probably valued to 0.0001$ on your local market...

Sometime, "pencil and paper" *are* the best tool for the job, because they work everywhere.

Same for C++:
It's maybe not Dart (for Google Chrome), nor Rust (for Firefox), nor Swift (latest gen iOS), nor whatever is the latest cool thing (scala ?) to run on a Java machine (for Android), nor Ruby (is that the lastest hipster thingy on servers ?)
But it works everywhere. Thus there *are* legitimate solution were using the older or simpler tool is better than all the modern hyped bells and whistles.

For quite some time, Eionrob has written a Skype plugin for purple (thus works in pidgin, adium, etc.)

Currently 2 versions available:

One requires the skype client running and uses the official Skype API to use it.
It still requires Skype, but at least it's being now routed to a half-decent client.
Voice calls work by opening a window from the original skype client.

The other version uses "Skype for Web".
It works thus 100% natively on any installation, without needing the original client.
Voice calls currently not implemented (because actually voice calls in "Skype for Web" aren't done with official web technologies, but using a proprietary binary plugin. But microsoft has mentioned considering upgrading that to WebRTC and such standards at some point of time in the future, so there's still hope)

Not perfect yet, buton the right track.

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)