Coincidentally I've been in Tampere for 6 months for work, going back to Brisbane on Monday. Being in a "short stay" apartment means that sauna power bills aren't my problem 😎

You can get smart meters in Aus now with time of use metering. What needs to happen now is that those meters get a simple, non-cloud-connected way to let your appliances know when is a good time to start up.

So for hard wired devices like your hot water heater or your pool pump you could have a simple relay-like device in your fusebox that can be set to "turn on below X cents per kWh" and it will switch them as needed.

Your air conditioner could have a linked IR remote that turns it on early in the day of power is cheap and chills the house for the afternoon heat or runs it a bit cooler than usual if it is already running.

Your fridge or freezer could have an "extra chill" setting.

Your washing machine and dryer could have simple "start now" "pause now" interfaces and they could just operate during the day whenever.

All this could be done with some newer version of the X10 protocol, and it would be great to get something like that standardised and widespread.

Microsoft is shit. Windows, is shit. Windows 11 is a privacy goddamn nightmare.

But in the end of the day, it just fucking works, those damn bastards ensure that. And even when something doesn't work, it seems, for some unknown reason, most of the online solutions do fix the issue.

Hahahahahahahahahahaha

(Pause for breath)

Hahahahahahahahahahaha

Only if you count "most of the online solutions" as "run SFC /SCANNOW and if that doesn't work, just reinstall your OS".

The effects of modern high density construction make blast zones and lethal distances a bit unknown.

500ft above St Paul's cathedral nowadays would mean that several million tons of concrete and steel would block the radiation pulse and mitigate the blast to quite some extent for those in the outer radius.

I want a music playing alarm app that's permanently locked to Sonny and Cher's , "I got you babe".

What I'm asking is how tf did text messages and whatever in the walkie talkies ignite a spark strong enough to ignite the PETN?

Pager with firmware that activates an output on date/time X/Y and triggers an ignition signal. That signal is sent o an actual detonator in the device, which sets off the explosive.

Radio with DTMF receiver that activates an output when, for example, touchtone 4 is received over the air, or alternatively if the radio has GPS, another date/time activation via firmware.

Both of these things are relatively trivial for a nation-state to pull off.

So yes, in both cases it's possible that faulty devices are still around. However, if all the rest of your group has had exploding pagers and radios, most people in the same group would have dropped their still-working pager or radio into a bucket of water by now. There's probably a few, and they're probably being carefully taken apart right now to see how it was done.

Afaik such an idea was nonsense previously.

It's not nonsense, it just takes planning and resources. And now that people know it is possible, buying and using any sort of equipment for your group without having the nagging concern there might be a bomb in it is impossible. And that's a pretty powerful limiter.

That's easy. Just fly somewhere and bring it in your carry-on, airport security will let you know.

As if the software was as permanent as the hardware lol

There's no guarantee that the software will ever be updated to something that the user finds usable though.

Google could just one day go "meh, we don't think folding displays are where we want to be right now", and - ta-da! - you're left with a folding doorstop and Google's got yet another entry on the "killed by Google" list.

As another poster has mentioned, M-Discs are written using a Blu-ray writer and are good for a few hundred years, in theory.

Blu-Ray USB drive and M-Discs is about the best you can get at present. Keep the drive unplugged when not in use, it'll probably last 10-20 years in storage.

Seeing as there hasn't been much advance past Blu-ray, keep an eye out for something useful to replace it in the future, or at least get another drive when you notice them becoming scarce.

90% of users when they are presented with the UAC popup when they do something:

"Yes yes whateverrr" <click>

I've got photos in Flickr dating from 1999 onwards. Ten thousand or so of them, and a couple of the early ones are now corrupted.

But they are my "other backup" for Google photos so I don't mind too much. I also have a USB Blu-ray drive at home that I use to periodically burn M-Discs that I hand out to a few relatives.

That's about as good as I can conveniently do for backup, and it's probably better than the single-point-of-failure box of negatives that my parents have in their cupboard.

when they're powered down.

There's no periodic cell refresh in flash memory like there is in DRAM. When USB sticks are plugged in, all you are doing is powering up the flash chip and interface ICs.

You'd have to read a block then write it back to actually refresh the stored charges in the cells.

I've commented on this previously, but this is essentially either a hit piece, or very poor reporting on Reuters' part.

Basically nobody looks at raw numbers for injury statistics. It's normalised to injures per million man hours worked, and when you take some conservative estimates on the size of SpaceX's workforce and the time periods involved, you find that they land pretty much in the middle of current "heavy industry" injury rates.

But it surrrre does look bad if you look at the raw numbers, just like if you looked at the combined raw numbers of, say, 10 steel mills across the country.

Permalink to my previous, much longer, comment

If they're so legit, they should be happy to share the footage.

Put the moral implications aside for a second and translate their actions to any other business. The business being ok with sharing the footage obtained via trespass implies that they're also ok with trespass.

That's a legal minefield no business wants to get into and out has knock-on effects. If employees are identifiable and haven't given consent - and they are not in a public place , working in a private area - then that's another headache.

If they use proprietary methods or equipment it gives a chance for competitors to gain insight and possibly an advantage if they happen to view those methods.

There are health and safety requirements as well. Regardless of who is on their site, they have a duty of care to protect them from hazards. Having people on site that aren't aware of safety processes (and processes in general) isn't great. If the trespassers method of entry was relatively easy, it means that protections that stop the general clueless public aren't the best either, and that puts them in hot water with safety regulators.

So basically, no legal counsel will tell the business, "sure, let them show the footage they illegally obtained, it'll be fine". They have to resist it, regardless of whether it's a shining example of best practice or not.

I don't think there's anything commercially available that can do it.

However, as an experiment, you could:

• Get a group of photos from a burst shot
• Encode them as individual frames using a modern video codec using, eg VLC.
• See what kind of file size you get with the resulting video output.
• See what artifacts are introduced when you play with encoder settings.

You could probably/eventually script this kind of operation if you have software that can automatically identify and group images.

Dammit now I have to reduce the block size of my discord-based cold storage filesystem.

They need to learn how to use their tools better. Winscp does all that transparently for you if you press F4 on a file on a remote system. Or maybe they did and you just didn't see it.....

It's quite a handy function when you're diving through endless layers of directories on a remote box looking for one config file amongst many.

Most times what I get when asking it coding questions is a half-baked response that has a logic error or five in it.

Once I query it about one of those errors it replies with, "You're right, X should be Y because of (technical reason Z). Here's the updated code that fixes it".

It will then give me some code that does actually work, but does dumb things, like recalculating complex but static values inside a loop. When I ask if there's any performance improvements it can do, suddenly it's full of helpful ways to improve the code that can make it run 10 to 100 times faster and fix those issues. Apparently if I want performant code, I have to explicitly ask for it.

For some things it will offer solutions that don't solve the issue that I raise, no matter how many different ways I phrase the issue and try and coax it towards a solution. At that point, it basically can't, and it gets bogged down to minor alterations that don't really achieve anything.

Sometimes when it hits that point I can say "start again, and use (this methodology)" and it will suddenly hit upon a solution that's workable.

So basically, right now it's good for regurgitating some statistically plausible information that can be further refined with a couple of good questions from your side.

Of course, for that to work you have to know the domain you're working in fairly well already otherwise you're shit out of luck.

If library devs do versioning correctly, and you pin to major versions like "1.*" instead of just the "anything goes" of "*", this should not happen.

Your unit tests should catch regressions, if you have enough unit tests. And of course you do, because we're all operating in the dream world of, "I am great and everyone else is shit".