Badabinski

I was looking for this comment so I can vent my extreme irritation to the world.

God, can this concept please die already‽ If you want to put solar panels where the cars/trains are, just 👏 fucking 👏 put 👏 them 👏 on 👏 top👏

Do not put them on the ground where they will get smushed and covered in dust and snow and dirt. do not. Just make a little roof for the train tracks/road/bike path/sidewalk/game trail/snail raceway and then put the panels on top of the roof and then if you’re feeling fancy angle the panels to point towards the sun and if you’re feeling really quite fancy then you can use bifacial panels to capture the backscatter from the ground and shit and then we can all be happy. solar ground no, solar roof yes, ground no roof yes. do not play the trolley problem with solar panels on the railroad tracks. we have been doing solar energy for decades and have fucking minmaxed this shit so why are they still trying to do this just STOP.

Fuck.

Person I’m responding to, please know that none of this is directed at you. I’m just sour right now and should get off the internet.

The arch wiki has a udev rule that can automatically do something if the battery crosses a certain threshold: https://wiki.archlinux.org/title/Laptop#Hibernate_on_low_battery_level

No polling which is great. I always try to do stuff on an event driven basis where possible for efficiency reasons. Gotta test this out though, since your battery might not send events for every percent change.

oh fuck I did misread it. Man, now I sound like a big ol’ asshole. Sorry, OP :/ I had a bad week thanks to some ChatGPT code and just kinda jumped out when I saw the word “ChatGPT” next to Bash.

Ugh, I hate ChatGPT. If this is Bash (which it is, because it’s literally looking for files in a directory called ~/.bashrc.d), then it should god damned well be using syntax and language features that we’ve had for at least twenty fucking years. Specifically, if you’re writing for Bash (and not POSIX shell), you better be using [[ ]] rather than [ ]. This wiki is my holy book I use to keep the demons away when writing Bash, and it does a simply fantastic job of explaining why you should use God damned double square brackets.

ChatGPT writes shitty, horrible, buggy ass Bash. This is relatively decent for ChatGPT (it even makes sure the files are real files and not symlinks), but I’ve had to fix enough terrible fucking shitty AI Bash to have no tolerance for even the smallest misstep from it.

Sincerely, A senior developer who is known as the Bash wizard at work.

EDIT: Sorry, OP. ChatGPT did not, in fact, write this code, and I am going to leave my comment here as a testament to what a big smelly dick I was here.

I played so many games on my Palm Pilot back in middle school. My Palm Tungsten T3 was great, and there were a shitload of freeware or shareware games released over the years.

Yeah, I’ve been wondering how the fuck they pulled this off. If it turns out that the only pagers that exploded belonged to Hezbollah members, then that would signal to me that this was done entirely digitally.

I’ve heard that batteries (can’t remember if it was laptop or phone batteries) contain the energy of a small grenade, but getting it to release that energy all at once without physical access is absolutely fucking wild and has serious fucking implications for device security.

EDIT: To avoid spreading misinformation, I’m providing this edit to say that the batteries absolutely were not the cause of the explosion. This was a supply-chain attack. Explosives were inserted into the pagers. The batteries in these pagers cannot be made to explode like this. I was overly excited when I made this comment.

For me, it’s Arch for desktop usage. When I first started using Arch it would not have been Arch, but now it’s Arch. The package manager has great ergonomics (not great discoverability, but great ergonomics), it’s always up to date, I can get a system from USB to sway in ~20 minutes (probably be faster if I used the installer), it’s fast because it doesn’t enable many things by default, and it’s honestly been the most reliable distro I’ve ever used. I used to use OpenSUSE ~10 years ago, and that broke more in one year than Arch has in ten.

I personally feel like Arch’s unreliable nature has been overstated. Arch will give you the rope to hang yourself if you ask for it, but if you just read the emails (or use a helper that displays breaking changes when updating like paru) and merge your pacnews then you’ll likely have a rock solid system.

Again, this is all just my opinion. It’s easy for me to overlook or forget all of the pain and suffering I likely went through when learning how to Arch. I won’t recommend it to you, but I’ll happily say how much I’ve come to enjoy using it.

The tiered storage stuff is pretty cool. You can say “I want this data on this disk, so if I get a cache miss from a faster disk/RAM it’ll come from this other disk first.”

I believe it also has some interesting ways of handling redundancy like erasure coding, and I thiiiink it does some kind of byte-level deduplication? I don’t know if that’s implemented or is even still planned, but I remember being quite excited for it. It was supposed to be dedupe without all of the hideous drawbacks that things like ZFS dedupe have.

EDIT: deduplication is absolutely not a thing yet. I don’t know if it’s still on the roadmap.

EDIT: Erasure coding is deffo implemented, however.

What if you need to file a bug? What if you have a question on the config that’s not easily answered by the docs? If you never, ever find bugs and never, ever have questions, then sure, separate the two. There are genuinely people like that, but they’re not common. If you’re one of them, then I’m genuinely glad for you.

My opinion is this: You use software. You don’t use people, but you sure as hell rely on them.

Because Vaxry (the lead dev) got banned from contributing to wlroots or any other FDO projects.

As for why he was banned, this is the only thing I’ve read about the whole thing: https://drewdevault.com/2024/04/09/2024-04-09-FDO-conduct-enforcement.html

Basically, he violated the FDO Code of Conduct when being told that a particular thing he said/enabled in a Discord community would not be acceptable if it was seen in spaces covered by said CoC.

This appears to be his response.

Were you using the kernel module? We’re using Flatcar which doesn’t support their .ko, and we haven’t been getting panics on any of our machines (of which there are many).

Falcon uses eBPF on Linux nowadays. It’s still an irritating piece of software, but it no make your boxen fail to boot.

edit: well, this is a bad take. I should avoid commenting on shit when I’m sleep deprived and filled with meeting dread.

The other person may have responded with a fair amount of hostility, but they’re absolutely correct. I run Kubernetes clusters hosting millions of containers across hundreds of thousands of VMs at my job, and OOMKills are just a fact of life. Apps will leak memory, and you’re powerless to fix it unless you’re willing to debug the app and fix the leak. It’s better for the container to run out of memory and trigger a cgroup-scoped OOM kill. A system-wide OOM kill will murder the things you love, shit in your hat, and lick your face like David Tennant licked Krysten Ritter.

Ahhh, I’d love it if I could tie that in with a Bluetooth OBD dongle and Home Assistant. It’d be awesome if I could set up a BLE proxy in my carport to automatically update stuff. It’d be especially handy if I could get alerted about check engine codes.

Which mouse and which distro? I’m genuinely curious. I’ve plugged my MX Master 3S directly into my work laptop running Arch many times and have never had to do anything to make it work.