69% of developers report losing 8+ hours weekly to inefficiencies—20% of their time (Atlassian, 2024)

Yep. If there is any company that knows what it takes to drive inefficiencies, it’s Atlassian. (Fuck them and their software.)

When I use it, I use it to create single functions that have known inputs and outputs.

If absolutely needed, I use it to refactor old shitty scripts that need to look better and be used by someone else.

I always do a line-by-line analysis of what the AI is suggesting.

Any time I have leveraged AI to build out a full script with all desired functions all at once, I end up deleting most of the generated code. Context and “reasoning” can actually ruin the result I am trying to achieve. (Some models just love to add command line switch handling for no reason. That can fundamental change how an app is structured and not always desired.)

The fan is good, but the orientation seems like it would struggle pushing air between the drives. Maybe a push-pull setup with a second fan?

My general attitude is similar to yours. Let OP figure out that the reporting and blocking is basically just creating more noise that has to gets filtered out and bot supply is basically infinite.

“It’s a learning experience.”

Good luck with that, I suppose. Botnets can have thousands, if not hundreds of thousands of infected hosts that will endlessly scan everything on the interwebs. Many of those infected hosts are behind NAT’s and your abuse form would be the equivalent of reporting an entire region for a single scan.

But hey! Change the world, amirite?

Old 386 and 486 code was really easy. I also got lost around the Pentium era as well. At the time, it was getting really hacky to work through extended and expanded memory while also learning to work with 32bit registers.

At the time, correctly or not, I just felt I was learning to navigate a bunch of architecture bandaids and not anything that was going to be static for the next few years. I just kinda put it aside, TBH.

ASM is still useful for MCUs at times and developing that feels like the good ol days…

You can generally cross compile across architectures, but there can be instruction or build nuances that can cause hiccups. Also, you need to build everything against the target architecture as well, not just the kernel.

I would look into something like Doppler instead of Vault. (I don’t trust any company acquired by IBM. They have been aquiring and enshittifying companies before there was even a name for it.)

Look into how any different solutions need their keys presented. Dumping the creds in ENV is generally fine since the keys will need to be stored and used somehow. You might need a dedicated user account to manage keys in its home folder.

This is actually a host security problem, not generally a key storage problem per se. Regardless of how you have a vault setup, my approach here is to create a single host that acts as a gateway for the rest of the credentials. (This applies to if keys are stored in “the cloud” or in a local database somewhere.)

Since you are going to using a Pi, you should focus on that being a restricted host: Only run your chosen vault solution on it. Period. Secure and patch it to the best of your ability and use very specific host firewall rules for minimum connectivity. Ie: Have one user for ssh in and limit another user account to managing vault, preferably without needing any kind of elevated access. This is actually a perfect use case for SELinux since you can put in some decent restrictions on the host for a single app (and it’s supporting apps…)

If you are paranoid enough to run a HIDS, you can turn on all the events for any type of root account actions. In theory once the host is configured, you shouldn’t need root again until you start performing patches.

That’s what you just got shown: Shove the configgy bits into Git.

You will likely have to find the configs you want to save first.

Sorry if it sounded like my rant was directed at you as it absolutely wasn’t. Your comment triggered me, because I absolutely fully agreed with yours as well. ;)

setenforce 0 is much cleaner, I have found.

Its just complex

When a security mechanism becomes more complex to manage than what it is supposed to protect, it becomes a vulnerability itself.

If you had a minimal system that you built from the ground up yourself and wanted to only have that system function in very specific ways, SELinux would be perfect. I would go so far as to say it would be nearing perfection in some ways.

Sorry, but in the real world, ain’t nobody got time for that shit. If you use auto configuration tools or pre-canned configs for SELinux on a system you are unfamiliar with, it’s more likely to cause application issues, create security gaps and will likely be shut off by a Jr. admin who really has no fucking clue what he is doing anyway.

It’s just easier to keep your system patched and ensure basic network security practices anyway.

It’s not impossible to manage these days. In the early days it was, but most everything is automagic now. If I am not mistaken, SELinux can be enabled to ‘log only’ which would give you data better handled by a HIPS anyway. (Don’t quote me on that.)

To add on, it supports up to 20.1.10 and that is where the protocol may shine. However, full spacial sound is not new, and Atmos is just Sony’s proprietary version.

I stole the “sound stick” bit from Benn Jordans blunt overview on atmos: https://youtu.be/5Dw3aKbw5Wo

(Atmos is all caps as well? Meh, whatever.)

I wonder what their answer is going to be for Dolby Atmos? I am sure they could think of a another protocol that is just as pointless for your standard TV sound sticks.

Who the hell writes if 'null'? If it’s a thing, what language would interpret a string like that?

Not sure if that will help in this particular case, but that looks super neat anyway. I have been planning to build a custom modular synthesizer so I’ll try that out anyway. (Thankfully, it’s Kicad integration is free. Yay!)

Build a live boot USB for windows: https://monovm.com/blog/how-to-create-a-windows-live-usb/

There is a chance that the exe is just a wrapper for a compressed archive that contains the app to flash the bios and also the image. If the bios actually supports flashing manually, that would be super convenient.

De-escalation is easy: Russia can get the fuck out of Ukraine. All of it.

If it’s useful to you, that is great.

Will rustc not just overwrite the old binary? If you are just doing a cleanup task, that’s cool. If nuking the last binary is important, then just do it first:

rm ./code; rustc ./code.rs -o ./code; ./code -mah args

I admire the willingness to share your work, but this is easier to do with a disposable one-liner at the prompt that you can repeat with an up arrow and a carriage return, if needed.

Sure, this script would be perfect for something like a cron job, but that would raise quite a few more questions as to why you would complie on a fixed schedule.

I can think of a few edge-cases where this script would be useful, but it just seems like it adds extra steps where extra steps might not be needed.