• 45 Posts
  • 2.36K Comments
Joined 2 years ago
cake
Cake day: July 5th, 2023

help-circle




  • Yes, but self-hosting does whatever the HOWTO, YouTube vid or AI slop the user follows tells them to do. If the user doesn’t know the basics, how could they know what an instruction for activating UPnP does or opening a NAT port does and why that might expose their data? Laymen don’t even understand what making theie stuff publicly accessible means. It might simply mean “Yay I can access my stuff on the go.” 😄

    If on the other had the user learns the basics, they can tell when a doc instructs them to do something dangerous and they can do something about it to avoid disaster.





  • “If you can’t configure Docker, reverse proxies, and Yaml files, you shouldn’t be self-hosting.”

    If this is an example of gatekeeping, I think you are misjudging.

    Whenever self-hosting there’s a very real risk of exposing your private data to the internet. Potentially a lot more private data than you’d otherwise expose via cloud providers. This risk necessitates a basic understanding of some of the importand bits and how to operate them securely. If not for that, then anything would go.

    Understanding docker, reverse proxy, and YAML which is used to configure those is part of probably the simplest way to get to secure self-hosting. I’d add a self-hosted VPN to access local resources. I’m not aware of a magic UI solution that does it all and securely. Docker compose files are very accessible. A couple of those followed by docker compose up -d and you have a basic env up and running.

    Generally the lack of knowledge in X or Y doesn’t mean there’s necessarily an easier path than learning X and Y and that you’re being gatekept by being told you have to learn X and Y. Some things are harder than others. Buying Apple Cloud and setting it up is easier than self-hosting Nextcloud. I don’t think that should be the case, but today it is as far as I’m aware.









  • Dear sir/madam, NVIDIA 550 is available in the Debian stable repo itself so no need for third party repos and therefore no significant risk of breakage. If that driver works well enough you’re good. Ubuntu LTS has NVIDIA 580 in its official repo. I’m running in on Ubuntu 22.04 LTS as I write. Then of course if you’re on Debian and NVIDIA 550 does not work for you, you could grab the official driver installer from NVIDIA which would very likely work fine on Debian stable, and it won’t break on its own via Debian updates since Debian stable doesn’t ship major version changes of its packages between releases. You’d likely have to uninstall, then reinstall every few years when you upgrade to the next stable Debian release, but that’s best practice for anything that was installed outside of Debian’s repo.

    There’s always a possibility for unintended fuckups but these methods are fairly safe and stable. Using 3rd party repos is significantly more risky to break things one of those days as you innocently apt upgrade.