• 37 Posts
  • 473 Comments
Joined 2 years ago
cake
Cake day: June 2nd, 2023

help-circle
  • Protect from accidental data damage: for example the dev might have accidentally pushed an untested change where there’s a space in the path

    rm -rf / ~/.thatappconfig/locatedinhome/nothin.config

    a single typo that will wipe the whole drive instead of just the app config (yes, it happened, I remember clearly more a decade ago there was a commit on GitHub with lots of snarky comments on a script with such a typo)

    Also: malicious developers that will befriend the honest dev in order to sneak an exploit.

    Those scripts need to be universal, so there are hundreds of lines checking the Linux distro and what tools are installed, and ask the user to install them with a package manager. They require hours and hours of testing with multiple distros and they aren’t easy to understand too… isn’t it better to use that time to simply write a clear documentation how to install it?

    Like: “this app requires to have x, y and z preinstalled. [Instructions to install said tools on various distros], then copy it in said subdirectory and create config in ~/.ofcourseinhome/”

    It’s also easier for the user to uninstall it, as they can follow the steps in reverse










  • Right, it’s not a genocide, they’re simply killing everyone that is living in a specific region. In fact, between the dead there aren’t exclusively Palestinians, but also some aid workers, volunteers from western countries and sometimes even their own kidnapped citizens. So it is not strictly a dictionary definition of genocide, rather a “mass murdering of the population”.

    In fact, I don’t see why they’re paying billions to Google to place AI on weapons when the algorithms seems to be like “hospital = target” and “if it moves = target”












  • for FOSS projects, google itself could sponsor the certification, if they really cared about security and not just closing the garden. The code is public and they could definitely write automated tests to check all they need to check, and at every single commit, and not just yearly, done in secret by some auditor.

    For google drive integration, i saw that most devs are just removing support for it because doesn’t make sense to pay $500 yearly to support it when there’s a million of better alternatives



  • If you have new drives: make a zfs array and copy all files there

    If you want to recycle drives while temporarily keeping the parity drives: from unraid 7 set a drive as unused, use the mover (or unbalance) to empty it, check if it’s actually empty by going to /mnt/diskX , format it as btrfs, set it as preferred for your shares, choose another disk to empty, use the mover to move all the data from the next disk to the new btrfs one, then remove the empty drive and add it to the btrfs raid. Repeat.