From the article it's 'just' a 1x PCI-E 2.0 lane (theoretical 5Gbps throughput). This is all the VL805 expects so all that's broken out to it's pads and 'easily' accessible.
I've enjoyed Xubuntu 18.04 for the light-ness. I pull the taskbar down to the bottom of the screen, swap out the "Whisker menu" for the more classical "Applications Menu" and I'm happy.
It has been pointed out to me that this produces effectively a reskinned Windows98 experience, I'm not unhappy about that.
Towing a magnetic field generator behind a boat or aircraft is a common minesweeping technique. The generator is usually mounted on a floating 'sled' to maximise depth capability, but aircraft-mounted degaussing coils were used in minesweeping by the British in WWII.
I think, I haven't looked at their implementation; they'll be an artifact of piping the encrypted/mis-decrypted stream into a video decoder. A lot of video coding techniques use variable-size blocks to describe changes to areas of the image, so it's reasonable that piping pseudo-random data into the decoder would produce some noticeable block shapes.
I'm happy to see this, however I'd be far more excited if I thought there was a chance of it landing in the upcoming Ubuntu 20.04 release - else I'll likely be waiting impatiently until 22.04 for server-side support.
My understanding has always been that e-recycling centers have to pay to responsibly dispose of the junk they collect / are given, and they fund this by sorting through it for any equipment that can be refurbished or cannibalised and sold for re-use. There's nothing nefarious about this.
The "DSLRKIT" splitters that are around on Amazon are reasonable in my experience, although the nominal output voltage varies by upto 10% between units.
The 802.3at-specced ones are a little more efficient than the af for the same power draw, I'm using them at home in a couple of applications where I'm feeding 802.3af but the power budget is cut a little close.
My understanding is that the 'gzip' directive applies to HTTP compression, which is only performed on the body of the response (both in HTTP & HTTPS), and not SSL/TLS compression which compresses the headers and so is vulnerable to the CRIME attack.
SSL/TLS compression has been disabled in nginx since 1.3.2[1]