• 0 Posts
  • 13 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle







  • asap@lemmy.worldtoLinux@lemmy.mlHow to have a boring and low-maintenance system?
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    1 month ago

    They won’t apply unexpectedly, so you can reboot at a time that suits. Unless there’s a specific security risk there’s no need to apply them frequently. Total downtime is the length of a restart, which is also nice and easy.

    It won’t fit every use-case, but if you’re looking for a zero-maintenance containerized-workload option, it can’t be beat.






  • That’s not a caveat, as you should be making your own backups of your photos no matter where they’re located.

    As an example, this man who lost all his photos because Google closed the account for an invalid reason, with no recourse.

    For something irreplaceable like photos, you should take your own backup no matter where they are. If you’re not already doing this - have a good think about how painful it would be to lose all your photos, even if the perceived risk is low.

    This doesn’t apply to just Google Photos of course. Any cloud provider has the possibility of losing your data or locking you out of your account. Even if the risk is low, do you want to roll those dice?