I’m a technical kinda guy, doing technical kinda stuff.
You are flashing the chip directly so apart from inadvertent short circuits and such if it doesn’t work you can just keep trying until it does.
As for wire length it all depends on how fast they clock the SPI bus when flashing. You’ll probably be able to get away with 20cm or so without difficulty , I’ve driven SPI displays with that kind of wire length before.
Well this seems to go against all sorts of disaster recovery practices, so I’m torn between believing they are truly incompetent or they are just lying.
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.
There’s a lot to be said for “http://yourISP.com/~username” being available 24/7 at no particular effort to you.
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
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”.
They also came from a time when hard drives could draw several amps while in use and much more on spin-up. There was a good reason why SCSI drive arrays used to spin each disk up one-by-one.
Molex connectors are good for 10 amps or so, SATA connectors couldn’t have handled that amount of current.
Excuse me, “UXers” is not the preferred term any more. You should be using “HXers”, as per the article.
In my opinion, replacing “users” with “humans” feels wrong in much the same way as when incels replace “women” with “females”.
They are reducing the accuracy of the description. All users of computers can generally be assumed to be human. All humans cannot generally be assumed to also be users.
Letting it ring has no impact. They have autodiallers that call, and when someone picks up, only then is that call assigned to someone in the call centre.
You can often tell this because there is a marked delay in the response to your initial “Hello?”. Long enough that you can reliably just hang up if you don’t hear a response in two seconds.
If it’s a real person who actually wants to call you and they you call again straight away, you can just shrug off your hang-up as a network issue.
how the IT team tries to justify being locked into Microsoft, and then telling me I could potentially become a point of vulnerability
Because they can manage and control all the windows PCs , pushing updates automatically, restricting what users can do locally and on the network, they have monitoring tools and whatever antivirus and antimalware tools they have, and are able to easily manage and deploy/remove software and associated group licensing and so on and so forth.
Meanwhile you’re a single user of unknown (to them) capabilities that they now have to trust with the rest of their system, basically.
The first rule of corporate IT is, “control what’s on your network”. Your PC is their concern still, but they have no effective control over it. That’s why they’re being a bit of a pain in the ass about it.
Mainly the issues are about providing ~600 kilowatts for 8 minutes to charge your typical size EV battery.
A row of 5 chargers of that size soaks up 3MW if they’re all in use, and that’s not something that can be quickly or easily shoehorned into a suburban electricity grid.
It’s about 500 houses worth of electricity usage, for comparison. For just 5 fast chargers.
Not to say it’s impossible, but infrastructure doesn’t come cheap, and so it’ll cost quite a bit to cram that 80 percent charge into your car’s battery.