This is cool! The simulator was useful for understanding what was going on, I hadn't realised until I watched a few that the roons can push marbles out in between squares.
Thanks! Glad to hear the simulator was worthwhile, took me ages to hack it into shape.
I did actually experiment with adding markings on the edges of the path roons, so that when you put them together, the "phantom channel" becomes visible. Ended up looking pretty cluttered though so I scrapped it.
I don't see planning mentioned much in the article or comments. The Town and Country Planning act is a large cause of high development costs in the UK. Roads, rail, public works, nuclear power stations, onshore renewables and above all housing have all suffered significantly because getting things approved is so difficult.
Most other affluent nations have some form of zoning instead, which make planning much much easier. Most other affluent nations have more central control over planning too, which makes consensus over megaprojects easier to reach.
This feels similar to heat pumps being >100% efficient though? Perhaps a less misleading headline would be 'Very low-power LEDs also convert heat to light'
Ukraine's drones are already partly automated because of the jamming environment: they can visually lock the drone onto a target from up to 10km away.[0][1] They're also using drones that trail a fibre optic over several kilometres to avoid jamming.[2]
> already partly automated because of the jamming environment: they can visually lock the drone onto a target from up to 10km away
This capability is basically a reinvention of the walleye television bomb, which locked onto targets using edge detection on a signal from an internal television camera. 1960s technology.
Wire guided is still the primary means of guiding torpedos from submarines, because it gives you an unjammable, un-interceptible, consistent communication interface, and in torpedoes the wire spools out for tens of kilometers.
If you want something really cool, look up old fashioned TV guidance. We built weapons that guided based a TV signal, and edge detection in that signal. In 1958.
Well, the chargers won't be pulling 1MW continuously, so you can smooth this out by installing batteries with the chargers. The grid demand becomes a more constant trickle into the batteries co-located with the charger
the idea would be to slowly charge the capacitor to its capacity in the breaks between the charger being used. That way when you arrive at the charger, the capacitor would be fairly full and able to quickly transfer that energy to your car. The charger would then replenish that capacitor more slowly (meaning that the charger wouldn't be able to be used for a bit).
I don’t know that they’d need to be, though. British-style baked beans come in tomato sauce. I just checked my tins, and they’re 36% tomato according to the ingredients list. Unfortunately they’re not that cheap anymore. We pay over CDN$2+tax per tin these days if you buy the multipack. A far cry from the CDN$1.50 all-in those Tesco beans would be.
I've used my Kinesis Advantage 2 for years and am inseparable. I'd like to swap to the Kinesis 360 but my current keyboard is just fine and it feels like a small upgrade
Systemd timer units are usually two: one for the service you want to run, one for the timer file.
I think you're confusing systemd timer units with Cronie[0], a crond implementation that I think predates systemd? It's possible there's some systemd thing I don't know about though!
I think most distros at least have an installable crond
If you're already using systemd, you can use its built-in credentials manager[0] which uses a combination of an on-disk key and the TPM2 to encrypt secrets at rest.
Probably annoying if you have more than one machine though
Hey, this is real cool. Is encryption at rest the only benefit over, for example, injecting the secrets as environment variables into a running systemd service?
I ask because my research suggests that there's a class of security vulnerabilities where attackers can read arbitrary files - but since /etc/system/systemd can be limited to be only readable by root, and the services it runs started by other less privileged users, I wonder how bad it would be to store a plaintext secret right in the .service file would be in practice. Especially since it seems this credentials management thing seems to just create a directory for the process with the decrypted passwords readable anyway (although maybe that's still not readable by an attacker? Still trying to figure this all out myself).
Gonna answer my own question here: No, actually systemd-creds is much better than just putting the plaintext secret into the .service (although that's still probably better than leaving it in a .env file if you have good user permissions set up).
Among other things, TPM and TPM2 are physical chips, which means even someone who steals your actual hard drive couldn't actually decrypt your stuff unless they also somehow got access to the rest of the computer containing that TPM chip. Huge improvement, although I'm not sure if your run of the mill cloud VM has (or even could have) such a chip permanently and uniquely bound to them.
