![](https://lemmy.zip/pictrs/image/f8786eb2-82f5-4e00-bd37-157be49f0074.jpeg)
![](https://lemmy.zip/pictrs/image/fbe4883b-64d2-4dbf-953d-789e884f5d6b.webp)
It’s the same robot. Cop bot suicide.
It’s the same robot. Cop bot suicide.
Article is vague about it, but what are the causes of death? I assume there’s a bunch. Though I wouldn’t expect children to get lung cancer, for instance.
Using rm -rf scares me. Is there a reasonable way to delete git repos without it?
I don’t know what to tell you, that’s the command you need to use.
If you’re that worried you’re going to nuke important stuff, make backups, and don’t use sudo
for user files.
It no more says that than hosting an HTTP mirror currently does.
It’s kind of funny. When I’m working on my own stuff, I could easily dump like 60+ hours a week into it. But once there’s an obligation to work on something, especially if it’s scheduled, 40 is unbearable.
Not sure what you’re getting at. Increased system efficiency lowers total emissions or at least increases work capacity.
I’m sure I won’t be very eloquent about it but simply, liberty. Freedom of compute is on par with freedom of thought and expression.
Freedom of travel is something else, but I’m sure most people that don’t like being imprisoned can appreciate.
Work (as in energy expenditure) enables these freedoms and I think it’s important not to stifle that whenever possible.
We’re literally in a technology community followed by tons of industry outsiders, of which there is a similar one on every other similar aggregation site. I don’t see any of that for things like plastics manufacturers, furniture makers, or miners. So yeah, I’d say transparency for the general public tends to be higher in tech than most other industries.
You know they just blamed the dude they fired for doing things he wasn’t asked.
You’ll probably have better luck with that. X has always been kind of annoying with displays. Especially if they change like with a dock.
Using X? I’m running a dock with triples via USB-C/thunderbolt without issue on Wayland. Maybe I had to briefly configure them but it really wasn’t anything worth remembering.
All these issues are valid and need solving but I’m kind of tired of people implying we shouldn’t do certain work because of efficiency.
And tech gets all the scrutiny for some reason (it’s transparency?). I can’t recall the last time I’ve seen an article on industrial machine efficiency and how we should just stop producing whatever.
What we really need to do is find ways to improve efficiency on all work while moving towards carbon neutrality. All work is valid.
If I want to compute pi for no reason or drive to the Grand Canyon for lunch, I should be able to do so.
Straight Gay Month! We’re taking the word back™
Engineers are often the most territorial bastards I’ve met.
It’s noticeably nice when working in a team of well adjusted folks that can work together.
It’s a privilege escalation.
The vulnerability, tracked as CVE-2024-1086 and carrying a severity rating of 7.8 out of a possible 10, allows people who have already gained a foothold inside an affected system to escalate their system privileges. It’s the result of a use-after-free error, a class of vulnerability that occurs in software written in the C and C++ languages when a process continues to access a memory location after it has been freed or deallocated. Use-after-free vulnerabilities can result in remote code or privilege escalation.
Maybe you could make a Corsi–Rosenthal Box. They’re pretty easy and cheap. It’s basically just a fan, a filter(s), and some tape.
Though it would be significantly less effective when bringing in outside air than just filtering inside air.
The red line somehow miraculously moves along with the tank about 10 meters in front of it.
Just don’t dwell on it. But you’ll probably think of it from time to time.
So it goes.
Reply to the wrong person? What does shell history have to do with zfs?
Surely that will help with your declining population issues.