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".

The problem with stack overflow is that you need to know enough about the domain you're working in to describe it accurately enough to search and find that previous great answer.

If you have no clue, and then naively ask the no-clue kinds of questions, because you have no clue, then you get beaten over the head about not searching for the existing answer that you don't know how to search for.

If you're interested in the systems behind Apollo, go find and read "Digital Apollo".

It goes all the way through the project and describes in good detail everything, how they developed the control systems, the computer hardware, how the software was designed, how they implemented one of the first real computer systems project management, all the interactions between astronauts/test pilots who still wanted to "manually fly the lander", the political back and forth between competing teams, the whole thing.

It's a great read if you have a technical mindset.

Horn switches switch to ground. Power for your original horn relay is supplied from a fused battery source, passes through the horn relay, and when you press the horn button the button completes the circuit to earth, triggering the relay.

So, you need to wire your relay coil like this -

12 volts from a fused battery source to:

Your relay coil, to:

The horn switch, which then switches to:

Ground.

Just like how your current horn relay works.

This also works for older cars that do not have the really. They supply power to the horn, and then a single wire runs from the horn back to the horn button, which then completes the circuit to ground when pressed.

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.

"Have you tried formatting your PC and completely reinstalling Windows? That often fixes icon misalignment on the desktop. Please upvote if this helps you!" - every "volunteer Microsoft Support Forum" representative ever.

Usually iterations of:

"Closed and locked due to duplicate of: (question asked 9 years ago about Visual Studio 2011 and Visual Basic, when you're using VS code '22 and C#)"

"This seems like an XY problem, what are you really trying to accomplish?", after a one thousand word post describing in detail exactly what you are trying to accomplish and the many different reasons why you can't just use #GENERIC_EVERYDAY_METHOD.

Either that or the quick and dirty method that I want for a one off data conversion that uses standard libraries is heavily down voted and lost while the elaborate, all-cases-considered, 7-third-party-library-using answer becomes the top result.