puetzk

But if two nodes that have added each other's keys cannot reach each other directly (e.g. are in separate private networks/behind firewalls/etc) but both can reach an external relay server, it may act as a dumb pipe bouncing encrypted traffic between them.

https://docs.syncthing.net/users/relaying.html

There is a public pool of such relay servers (https://relays.syncthing.net/), and by default syncthing will reach out and connect/announce its itself there so other nodes looking for it could contact it via a relay.

You can host your own relay server and configure your clients to use it exclusively: https://docs.syncthing.net/users/strelaysrv.html#client-conf... or if you only want syncing when your nodes are on the same local network you should be able to just not configure any relays at all.

Actually, ThinkGeek made a production run a couple years back (though I guess I don't know that they were US-made). Doesn't seem to still be on their website, but I have one so it definitely existed. https://www.amazon.com/ThinkGeek-Slide-Rule/dp/B003M5B84C still shows a listing.

1) automated stations and satellite communication making it much easier/cheaper to sample remote locations

2) use of whole-globe numerical weather models which require complete initial conditions, even for regions where nobody much cares about the output

3) increased interest in climate research

would lead to a greatly increased number of Alaskan stations operated by NOAA (and of course corresponding moves by other national agencies)

But the alleged crime here is years old, and I have don't remember anything (or find anything in a google news search-by-date) to suggest there were charges or an arrest warrant before July 2017. That makes it seem like they didn't think the evidence was strong enough to get British cooperation, and waited to even mention it until they'd have have a chance to act alone.

Either that, or they really had nothing linking Hutchins to Kronos until very recently. If it turns this really was based on new information, and the timing really was coincidental, I'll be a lot more comfortable with how it was handled. But that's sure not what it looks like right now...

But running a snatch and grab at a security research conference looks really bad, and is bound to have a much wider chilling effect on people's willingness to attend US conferences.

Server/embedded/etc headless environments presumably want .NET Core instead, which added most of these updates in version 1.1 a few months back (along with VS 2017).

That supports Android 7.1 on lots of devices the manufacturers don't (I have it on a 1st-generation Moto G).

Or looking at what's already popular, USB-C connectors already spec do 3A@5V while handling data, or in PD mode (re-purposing pins) can do 5A@20V (100W).

So the first case of a charge 3000mAh in a minute doesn't seem completely ludicrous, though it's going to be challenging to make everything efficient enough the heat isn't prohibitive.

CNNIC was the root of trust for a breach involving false certificates for gmail. They claim it was an accident. It might have been. It might not have been.

Git also has smudge/clean filters if you want to transform your file to a format where line-by-line textual merge is more meaningful

And you can use .gitattributes to make certain extensions/folders/file/whatever default to a certain treatment.

A good example is https://bitbucket.org/sippey/zippey which unpacks zip archives (and hence file formats based on them, like .jar, .docx, etc) to allow the contents within to be tracked in the git repo better. Other custom formats could do something similar...

The results probably won't be well-optimized, though; C isn't actually very portable at this level, there's too much implementation-defined behavior that needs to be taken into account. You'll probably spend as much effort trying to robustly handle the quirks and deficiencies of some obscure platform's compiler than doing an LLVM backend for the processor...

Musical tracking has to take special measures to keep the latency low enough even when its all local; see the need for ASIO, jackd, etc.

It's basically a shibboleth for "Are you a fan of Richard Feynman". I doubt very many people have actually heard of it directly, but his "Cargo Cult Science" commencement address (http://neurotheory.columbia.edu/~ken/cargo_cult.html) is moderately famous.

Sadly, this means IE doesn't get forward secrecy, because it can't do do DHE with RSA keys, only DSS.

Storing the same amount of energy in a lead-acid battery would only take 21kg, a LiFePO battery only ~10kg. And those don't require digging out a 500m hole, or the supporting equipment to winch a car up and down a skyscraper.

When disconnecting, break the connections in reverse order.

Lead-acid batteries release hydrogen during discharge (and may vent it if the discharge is rapid), or from overcharging (water can electrolyze). So the live battery is likely releasing some, and the dead battery might be if it's actually damaged and not charging properly.

So making the final, sparking connection (or first disconnection) is safest using the negative/ground wire (no potential), on the dead vehicle (avoiding the definitely-discharging live battery), and some distance away from the dead battery (mostly aviding the possibly-outgassing dead battery). This minimizes your chance of the spark igniting a cloud of hydrogen gas and getting a fireball.

And now that you know why the order is what it is, you'll probably be able to remember it :-)