• 0 Posts
  • 25 Comments
Joined 11 months ago
cake
Cake day: December 5th, 2023

help-circle


  • smallest part of the problem

    This is what I’m trying to get across to you here. You’ve posted the same notion multiple times in this thread. The consumer share isn’t the smallest part, it’s most of it. All the oil we extract serves to make products, transport products, sell products to the consumer - you. It’s not being being burnt for fun.

    When you engage in consumption, any amount of it, you’re pulling a string connected to a million other strings that mostly end up in an oil well one way or another. The luxury you speak of is in that consumption, not the lack of it.

    And if you think otherwise, compare your lifestyle, your lifelong level of comfort to that of someone who spent their whole life living in a hut in Mali, whose lifelong emissions equal a few months worth of yours. Now try to tell that person that you’re not responsible for the gas you burn, it’s the fault of those that provided you with the option to do it. It’s insulting.


  • If the providers are to blame for all emissions and the consumers are free of responsibility, then all consumption is equal. If Exxon is the responsible party, then the guy buying the gas guzzler to stick it to the libs is the same as the guy driving a hybrid, as neither is to blame for their emissions.

    I understand choosing comfort over living in a cave or dying, obviously, but that doesn’t mean we’re free of any and all blame. Any time a new climate report comes and it’s worse than the one before I understand that my existence and choice of comfort played a part in it . I don’t just go “oh that Exxon, smh” and carry on guilt free.








  • What’s up with the abuse of the word open lately. I had a look at that project to see how they were doing the conversion, but I couldn’t find it. But I found this:

    Short answer, yes! OpenScanCloud (OSC) is and will stay closed source…

    Your data will be transferred through Dropbox and stored/processed on my local servers. I will use those image sets and resulting 3d models for further research, but none of your data will be published without your explicit consent!

    I feel like I’d rather use Autodesk at that point. At least I know what I’m dealing with right out of the gate.







  • I’ve been in love with the concept of ansible since I discovered it almost a decade ago, but I still hate how verbose it is, and how cumbersome the yaml based DSL is. You can have a role that basically does the job of 3 lines of bash and it’ll need 3 yaml files in 4 directories.

    About 3 years ago I wrote a big ansible playbook that would fully configure my home server, desktop and laptop from a minimal arch install. Then I used said playbook for my laptop and server.

    I just got a new laptop and went to look at the playbook but realised it probably needs to be updated in a few places. I got feelings of dread thinking about reading all that yaml and updating it.

    So instead I’m just gonna rewrite everything in simple python with a few helper functions. The few roles I rewrote are already so much cleaner and shorter. Should be way faster and more user friendly and maintainable.

    I’ll keep ansible for actual deployments.


  • Not sure what you’re on about, most package managers have a literal database of most package manager installed files. Debian and derivatives have dpkg --verify or debsums to verify the files, arch has paccheck, I’m sure other distros have something similar. And fixing them is just a matter of reinstalling the package, which you can do from a chroot if the system won’t boot.

    Or you can just run your system on a checksumming FS like btrfs which will instantly tell you when a file goes bad.