2024-05-07, 01:49 PM
(2024-04-18, 06:39 PM)joseph Wrote: I actually registered for an account after reading this post (I'd been searching for something unrelated) just so I could respond.
First... Just heartbreaking... I actually cringed when I read this.
As for the rest... I concur with the overall sentiment that this was user error and not a product defect.. but that said, couldn’t a feature request be added to either:
• Prevent setting the cache directory to a non-empty directory. Or..
• Issue a strongly worded popup confirmation if the system detects the cache directory is being changed to a non-empty directory
Understanding that it’s impossible to ever build software that cannot do bad things inadvertently… but warnings can at least reduce the likelihood that someone makes a careless mistake that ends up being so costly.
Self-hosted applications generally aren't targeted at lowest common denominator users - it's typically assumed if you are running your own services you have some idea of how computers, networks and operating systems work. Personally, I think there are more important lines of effort to be developed than protecting users from doing dumb things.
I don't want to change my sig with every new version. I'm running whatever the currently packaged version for Ubuntu Server 22.04 