• 1 Post
  • 343 Comments
Joined 3 years ago
cake
Cake day: June 25th, 2023

help-circle
  • I’d argue that most things that are currently in the crosshairs for exclusion under age verification are also harmful to at least a third of the adult population and to society in general.

    Actually maybe that’s just for profit algorithm based social media and / or mass scale surveillance and personal information gathering and advertising.

    The point being, if you’re going to make a case for something being harmful to kids, you need to also make a case for it’s being OK for adults or maybe it just needs banning outright for the good of society, see also smoking. Personally I’m in favor of leaving this in the hands of the individual and parents, and perhaps making easy tools for less technically adept parents to use.

    TLDR: If Facebook is bad for kids, why isn’t it bad for adults?


  • Seems pretty plausible, not 3-2-1 yet, but on the way, and should get the habits established well enough. Just having an offline backup is a huge step up from most. Consider a waterproof box (perhaps buried) in the back yard instead of just another room (in case of fire / flood).

    If you have a friend with a similar setup, or who perhaps wants one, you can sync over internet and both get your offsite without the expense of online backups or the inconvenience of lugging HDDs around.






  • I’ve never heard about any privacy issues there, but, it’s worth keeping in mind

    You would hear about it, and as someone happy there, it’s a recurring nightmare, but an actual credible threat would be worth so many dollars lost to them that there’s a low likelihood. Shit, Torvalds runs fedora, still, keep a weather eye open.

    Mostly Linux has the virtue of the many eyes on open source protection, but it’s far from absolute, as the rise of supply chain exploits demonstrates.



  • Layer things that genuinely need (often in boot sequence) low level access like filesystems (e.g. I have mergerfs+snapraid on my desktop). If you’re OK with a longer rpm-ostree update, you can layer some self contained things like btop with little risk, perhaps also your preferred shell. Also anything you want in TTYs if something breaks.

    vim edit /etc/fstab works fine from within a distrobox, you just need to do sudo vim /run/host/etc/fstab or distrobox-export the binary to your main shell, which means that the container will start, but you don’t have to enter it. If you fire a terminal profile into the container by default at login you won’t need to start the container when you use an exported command.

    Embrace the distrobox experience for development and generally mucking around, use Arch’s AUR, archive entire environments, there’s lots going for it.

    Linux brew is coming along nicely, use it first if there’s a formula, but I’ve been fine with flatpak, distrobox and layers (in that order) for a couple of years now.





  • I run podman containers on my bazzite machines, basically you convert a docker-compose file to a .container file, here’s a bunch of examples, nextcloud is there, drop it in ~/.config/containers and run systemctl daemon-reload and it’s now a systemd unit that you start stop etc like any other. Updates are with podman autoupdate.

    You can use podlet to convert docker-compose files (90% it works, otherwise it gets you 90% of the way there). It’s basically the fedora (/redhat) way to run containers.

    I have no idea where you got it not being recommended (but adding to the main image sure is discouraged), and it’s certainly better than adding a vm for containers, which pretty much defeats the purpose of containers (to run using your main kernel, but contained).

    I’ve been running my arr stack (with gluetun in a pod) etc this way for years now, very trouble free. Here’s a immich example.

    It’s a bit of a learning curve, but it pays off.