• 0 Posts
  • 10 Comments
Joined 2 years ago
cake
Cake day: August 8th, 2023

help-circle

  • Until a couple of weeks ago I used Fedora Silverblue.

    Then, after mostly using GNOME Shell for about a decade, I (reluctantly) tried KDE Plasma 5.27 on my desktop due to its support for variable refresh rate and since then I have fallen in love with KDE Plasma for the first time (retrospectively I couldn’t stand it from version 4 until around 5.20).

    Now I am using Fedora 39 Kinoite on two of my three devices and Fedora 39 KDE on a 2-in-1 laptop that requires custom DKMS modules (not possible on atomic Fedora spins) for the speakers.

    Personally I try to use containers (Flatpaks on the desktop and OCI images on my homeserver) whenever possible. I love that I can easily restrict or expand permissions (e. g. I have a global nosocket=x11 override) and that my documentation is valid with most distributions, since Flatpak always behaves the same.

    I like using Fedora, since it isn’t a rolling release, but its software is still up-to-date and it has always (first version I used is Fedora 15) given me a clean, stable and relatively bug-free experience.

    In my opinion Ubuntu actually has the perfect release cycle, but Canonical lost me with their flawed-by-design snap packages and their new installers with incredibly limited manual partitioning options (encryption without LVM, etc.).


  • In my opinion Plasma has gotten much better with the last couple of releases. Around 5.21 the defaults actually got pretty good and since 5.24 Wayland support is quite good, on par with GNOME in my opinion.

    After using GNOME Shell for a decade I have recently switched to Plasma 5.27 on my desktop due to its VRR support (I have two 170 Hz QHD monitors). A couple of weeks later I also moved my laptops to Plasma, even though I wanted to keep GNOME on them, since Plasma has gotten so nice!

    Just wanted to give a heads-up in case you haven’t tried Plasma in the last couple of years. ;) But especially if you rely on dynamic workspaces and don’t want to adapt your workflow (like I did when I switched to Plasma), there’s just no alternative to GNOME and it has gotten really polished and nice as well.


  • My whole infrastructure is designed so that my homeserver is expendable.

    Therefore my most important tool is Syncthing. It is decentral, which is awesome for uptime and reducing dependance on a single point of failure. My server is configured as the “introducer” node for convenience.

    I try to find file-based applications, such as KeePassXC or Obsidian, whenever I can so that I can sync as much as possible with Syncthing.

    Therefore there is (luckily) not much left to host and all of it is less critical:

    • Nextcloud AIO: calendar, contacts, RSS, Syncthing files via external storage
    • Webserver: Firefox search plugins (Why is this necessary, Mozilla?!), custom uBlock Origin filter list, personal website

    So the worst thing that can happen when my server fails is: I need to import my OPML to a cloud provider and I loose syncing for some less important stuff and my homepage is not accessible.

    Since I just rebuilt my server, I can confirm that I managed a whole week without it just fine. Thank you very much, Syncthing!



  • I was in a similar situation not too long ago.

    My criteria for another scripting language included that it should be preinstalled on all target systems (i. e. Debian and Fedora), it should be an interpreted language and it needs to have type safety.

    Afterall I settled with Python due to its popularity, its syntax and features (type safety since v3.6, etc.) and the fact that it is preinstalled on many Linux distributions. System components often use Python as well, which means that libraries to interact with the system tend to be included by default.



  • Actually that’s one of the main reasons I use Syncthing: It doesn’t need a server, as it is a peer-to-peer architecture. Unlike a centralised solution (cloud storage, Nextcloud, etc.) devices sync directly with each other. If they are on the same local network, you get to enjoy the full bandwidth of your local network. If they need to sync over a long distance over the internet, you are limited by the upload and download speeds of your internet provider, just like with centralised storage.

    I have a server that serves as an introducer, so I don’t have to connect each device with every other device manually. But the server doesn’t need to be available once all devices are connected with each other.

    Syncing continues to work without it for as long as I don’t reinstall any of the other devices. And even if I’d reinstall a device, I could delegate any other device to be the introducer or connect the devices manually with each other. It really is quite robust and fail-safe.



  • For text-based notes I use Obsidian.

    It isn’t open source, but it writes standard markdown files to disk, so I can switch programs whenever I like and I am not locked into the Obsidian ecosystem with my notes. That was the main reason why I decided against using Joplin, especially after my experience with converting recipes from Nextcloud Cookbook to markdown …

    In general I am always trying to find a simple file-based solution for whatever I need to do. I want to be able to sync it with Syncthing instead of something fancier that requires a centralised web server or even relies on a cloud service.


  • I am surprised that no one has mentioned Rnote yet.

    It is my favourite newly-created program for Linux. It is a relatively new app which supports annotating files and taking handwritten notes. You can import PDFs, set the page size to infinite or a fixed size (something OneNote can’t do), adjust the background to display grids or lines or dots or nothing with any spacing you like, input text with your keyboard, … It is available on Flathub for easy installation.

    The only major downside is the following: Disclaimer: The file format is still unstable. It might change and break compatibility between versions.