Shades of Max Headroom (circa 1985):

TV network guy: "His TV has an off button. He'll get 30 years for that!"

If they don't care to give you a high-quality translation, they should be honest and use the tag FU. (Unlikely to ever be intentionally assigned to a real country.

Showing the URL doesn't help. QR codes typically link to an opaque URL shortener (similar to bit.ly), never to the final destination.

Why would these features remain "largely untested" if they were used in multiple attacks?

"ship, shipmates, self" actually gets the old sailors' slogan backward. It suggests you should place the welfare of the company ahead of your own. He has just declared toxic culture to be part of the company values. I can't imagine the stupidity of that, but there it is.

I've always heard it as "Bunk mate before mess mate, mess mate before shipmate, shipmate before friend". That is, place those closest to you above those you merely work with, or those you just know.

Another slogan is "One hand for yourself, one hand for your ship." In other words, it's a dangerous world out there (especially on a sailing ship), so keep your own safety in mind when working to ensure the safety of your ship.

"More and more websites started offering HTTPS connections, and now practically all sites that Google links to do so."

You'd think the "News for Nerds" site would be on top of this, but they only fixed the readily-visible urls. Slashdot web pages are all HTTPS, but their RSS feed http://rss.slashdot.org/Slashdot/slashdotMain stubbornly refuses to move into the 21st century.

I'm just waiting for evil.org to inject a feed with links to drive-by exploits. Despite the exasperation I have toward the long-standing Unicode problem, I pray that Slashdot gives some priority to this security weakness.

Additionally, Firefox 95.0.2 in HTTPS-Only mode blocks Feedbro extension from reading the feed, despite adding exceptions for the relevant host. A workaround is to turn off HTTPS-only mode and enabling the HTTPS Everywhere extension.

No, not previously exposed. Per TFA, the training set was more than 10 billion chat logs which people sent to the Science of Love app and paid about $4.50 each for an analysis of whether the counterparty had romantic feelings for them.

You can tell that Vienna University of Technology doesn't have a naval architecture department. The picture with the caption "The platforms remain steady - even when the sea is rough" shows ripples that a blue-water sailor considers "dead calm". Also, the statement "When the air tanks are correctly dimensioned, the waves rise and fall under the Heliofloat without making any significant impact on the platform" can only be true for a limited range of wave frequencies. The deck will need significant stiffness, or lots of flex joints, to deal with all other conditions.

Obviously, you missed the RSA Tattoos: Illegal Tattoos: RSA Tattoos

Several people obtained them when U.S. International Traffic in Arms Regulations (ITAR) banned export of cryptographic software with keys longer than 40 bits, making these tattoos "munitions". Apparently, no arrests were made.

In 1996, the ITAR restriction was ruled unconstitutional, instantly making all these tattoos "retro".

16-4-20-Order-Motion-to-Suppress.pdf The order notes that a district judge may have the authority to issue the NIT warrant. "The jurisdiction of district courts is usually defined by subject matter and parties rather than strictly by geography." Magistrate judges (such as the one who actually issued the warrant) must follow additional rules which confine their authority essentially to within their own district.

IANAL, but this was not a slam dunk for privacy. If a sharp U.S. Attorney had reviewed the request, it might have been sent to the proper judge. Also, a proposed amendment to the Federal Rules of Criminal Procedure would negate this specific issue.

To put this in perspective, a 1000 sq ft house might require a electric furnace rated for 15-30 kW (which will cycle on and off). The only homes drawing this much continuously will be server farms or grow houses. The Chelan Power District presentation indicates the surcharge would probably apply to any high density load, not just Bitcoin miners.

The Chelan Power District presentation indicates that the aggregate household load averages ~2.4 kW per house.

You may have confused distribution network capacity with generating and transmission network capacity. The "flood of requests" are for individual service hookups. This requires buildup of the distribution system, the layer of the electric system that runs radially from substations to customers. This can't be resold easily; if the BC miner goes bust, the capacity is stranded unless the landlord finds a new power-intensive tenant or a lot of new construction happens.

The 220 MW of new connection requests dwarf the utility's typical annual growth of 3 MW and will put a serious dent in long-range planning. If they need new generation or transmission capacity, construction of either will take several years (not counting environmental impact studies and public comment periods).

In the meantime, the utility will have less of the inexpensive power to sell (which is probably a hot item on the national grid), since their watershed will still have the same rainfall. As they operate closer to maximum capacity, there will be more occasions requiring the utility to import higher-priced electricity.

The reason the initial requirements docs and RFP are inadequate is because the Government (not just the Navy; everybody's guilty of this) is trying to buy capabilities they don't already have and don't know how to completely describe. You should apply Hanlon's razor to your opinion of "shenanigans".

As the system develops, the contractors will need to choose design details which weren't spelled out in the spec. The contractor preference is more-or-less technically reasonable (depending on the experience level of their assigned engineers), but tending toward low cost. The Government usually wants something more robust than the low cost solution, and usually doesn't have the time or the estimating resources to fully understand the cost & schedule impact before issuing the technical response.

That's for a normal contract; LCS intentionally took a faster, higher-risk route. The RFP asked the bidding teams to submit their ideas of what the Ship Specification and the Interface Specification (between the ship and the modular warfare systems) should look like. (That, at least, meant that the Navy had three different inputs to mix and match).

A common opinion from people low down on the totem pole is that the effect (if not the intent) of the LCS program was to split up the cost overruns into separate piles for the ships and the weapon systems.

Since the emissions test is done on a dynomometer, constant-speed portions of the test will have much less speed variation than normal driving. The lack of small accelerations could fool an "honest" emissions control algorithm to spend an abnormal amount of time in an ultra-low emissions mode. Therefore, making the algorithm "completely honest" would require that it know when it was under test and select operating modes which more closely emulate real-world driving conditions.

The above argument ignores the fact that it is perfectly legal to "design to the test". Since the beginning of the US EPA tests, cars where designed to have their fuel consumption minima at exactly the condition used in the EPA test, without explicitly sensing that they were under test. (In the early days, when the national speed limit was 55 mph, the highway mileage test was done at a constant 49 mph.)

My point is that, as both emissions control algorithms and the associated regulatory tests become more sophisticated, it may be necessary for the engine to cooperate with the test equipment. In that case, prudent regulators should institute some degree of code inspection to ensure that the cooperation is not malicious.

We already have enough technologies to make user input ambiguous: (1) My Synaptics touchpad thinks my index finger is a two finger gesture about half the time. There doesn't seem to be an adjustment to reduce sensitivity for this. (A middle finger gesture doesn't work any better, tempting as it is.) (2) Kindle Fire sometimes thinks that holding it by the black border, well outside the screen area, is a tap on whatever is the nearest screen-edge icon. (3) Disuse of the Accelerator Key input method, making me aim my carpal tunnel at everything (including targets obviously sized in the days of 14" 800x600 pixel displays).

There are many ways Force Touch might miss: An arm-length reach for a phone on the table will not have accurate force input. Perhaps potholes, too much coffee, or Parkinson's or other tremor disease. ([sarcasm]Assuming smartphones are otherwise disability-friendly.[/sarcasm])