• 1 Post
  • 16 Comments
Joined 2 years ago
cake
Cake day: July 4th, 2023

help-circle


  • I agree with the general idea of what you’re saying, but it’s a slippery slope.

    Most people I know personally would never take the effort to learn anything past the point of “Ask ChatGPT” when they have a problem. What happens when the model is wrong, or simply cannot solve the problem? Or maybe they have no network connection and cannot run something suitable locally?

    At that level of coddling, then they might not even have the ability to find and open a man page, or edit a config file without a GUI. And that’s a problem. It’s not even Linux-specific. I went to school with “smart” computer science students who don’t even understand file extensions or what a shortcut conceptually is.

    What I’m getting at, is there needs to be some kind of balance, or people will just gradually become more useless.



  • Overall, it’s good, but you need to know what exactly you’re signing up for. The reality is that you can run a decentralized or centralized E2EE chat server, along with voice/video calling, without much effort. There are hiccups with the key exchange that suck, and metadata isn’t really protected. It really comes down to if it meets your particular requirements.




  • I’ve been using Arch off and on for a long time, since it was horrible to install and updates did often break stuff. This is not the case now 🖖, and the Arch wiki is your friend.

    1. Consider using btrfs with automated snapshots using yabsnap. It includes a configurable pacman hook in case something goes awry. Also just nice to have snapshots in case you accidentally delete a file or something.

    2. Use paru, an AUR helper. Good for random things which may not be officially packaged. Expect to run into failures, and learn to diagnose them. Sometimes it’s just a new dependency the packager missed. For both paru and pacman, clean the cache once in a while or automatically, or things will get out of hand.

    3. Do the “manual” setup, at least the first time, so you have an idea what’s going on. Don’t forget to install essential stuff like iwd (if needed) when you do pacstrap, or else you might have to boot from live again to fix it. Once you’re done, take care to follow the important post install steps, like setting up a user with sudo, a firewall, sshd, etc.

    As for general setup, I’ve recently embraced systemd-networkd and systemd-resolved. Might be worth giving it a shot, since there is no default network manager like application. You can even convert all your wireguard client configs into networkd interfaces.

    Best practice: Keep a personal log of various tweaks and things you’ve configured, and set up automated backups (more of general guidance).

    Have fun!