• 8 Posts
  • 31 Comments
Joined 2 months ago
cake
Cake day: October 2nd, 2025

help-circle
  • I went for the simplest option

    1. Installed a distro (in this case Debian)
    2. Installed tailscale on the server, logged in
    3. Installed tailscale on my other devices, logged in
    4. Used sshfs to mount the desired directory on the server to my client
    5. SSH in once a week or so to run updates

    Found it very simple. Avoided the tedious setup of samba and samba had weird reliability issues for me when copying large files. Took a bit to learn how ssh works, but very much so worth it.





  • Snap is interesting for me it can do more things than flatpak and has some really interesting sandboxing features coming up such as permission prompts for filesystem access.

    But Canonical management is a significant hindrance. The Snap Store simply cannot be trusted after so much malware got in and they still have not improved their processes. So many snaps including Canonical’s own, are still using core22 for some reason. And there’s the broken snaps Canonical pushed on users.

    I would love to see a snap repo that takes the best parts of Flathub and Fedora Flatpaks. Because as a technology, I think snap beats flatpak (if you’re using AppArmor). But it’s Canonical’s poor management that really drags it down.




  • With archinstall, I largely agree. However, you still need to make a lot of choices. Which kernel branch? Which filesystem? Enable swap? Which desktop environment? And other choices that I forget, it’s been a few uses since I used Arch.

    Gamers Nexus is very clear they want to avoid making decisions. They want to stick as close as possible to as possible, but that’s tricker since Arch doesn’t have defaults for those, unlike Bazzite. Bazzite uses the Fedora kernel (which follows the latest stable); btrfs; zswap; desktop environment they do provide a choice between KDE and Gnome, in which case is easier to choose KDE since it’s what Valve is pushing.








  • In my experience, many Gnome apps make doing complex tasks pretty easy compared to third party apps. However, it is at the cost of customization and questions like “why can’t I do this???”

    But in general, Gnome’s simple design works for me, most things feel clean and polished. I don’t need the vast majority of features offered.

    In the cases where Gnome’s default aren’t powerful enough, often times the KDE equivalent isn’t good enough for me either despite offering more features and customization.

    As an example, Gnome Text Editor vs Kwrite and Kate. GTS has the basics I need like line numbers (Apple’s text editor does not have this…) and that fits 80% of my needs. But what about more advanced things? Well, no markdown support but I don’t think Kate has that either. What about coding? I’d rather use a dedicated IDE than Kate or GTS.








  • The for argument is basically the following

    • Wayland as a protocol was designed around CSDs, protocols for SSDs came years later
    • Having the client control the CSDs simplifiies things for the compositor and apps
      • The compositor has less things to implement and test
      • Modern apps tend to prefer CSDs anyway since it provides more flexibility, very common on MacOS and Windows
      • It’s difficult to coordinate things between the client and compositor.
        • Something that annoys me about KDE is that they do this headerbar look where the top part of the application will match the color of the the titlebar. However, the top part of the application is drawn by the application and the titlebar is drawn by the compositor. But when the color changes (such as going from unfocused to focused), they do not update at the same time, so for a frame or few the top part of the application is a different color than the titlebar. That wouldn’t happen under CSDs.