I haven’t seen it mentioned here, so just an FIY: Linux Mint is a “regular” distro, while Bazzite is an immutable distro, meaning the root filesystem is read-only.

That means a lot of the “normal” ways of doing stuff you find online will need to be done differently. For example installing system level packages requires a reboot, to boot in to the new “system image”. If something gets booked you can reboot in to an old system image to recover. Regular desktop (Flatpak) apps can be installed without rebooting.

Bazzite is based on Fedora, and very similar to Fedora SilverBlue (immutable version). So if you can’t find answers when looking online “how to do X in Bazzite” try instead “how to do X in SilverBlue”.

And FYI Linux Mint comes with an easy to use app Timeshift for system level backup and restore (by default it does not backup your documents etc in your HOME folder). Very handy to recover from a borked update or installing something you shouldn’t have.

Ugh, me neither. Bought by Snap-On according to Wikipedia:

Bahco is a Swedish brand within the hand tool industry, which is now part of SNA Europe, part of Snap-on.

Same for Cocraft as far as I know (Clas Ohlson white label)

No, full stack made in Europe. From silicon (microchips) upwards. Including cloud platforms, e-commerce, AI, and more.

Hopefully they’ll funnel a lot of investment in to growing and adopting existing open source projects from Europe.
Image for example if all EU institutions used their Office 365 license fees and instead invested in LibreOffice development, and all adopted LibreOffice

SingleFile provides a faithful representation of the original webpage, so bloated webpages are indeed saved as bloated html files.

On the plus side you’re getting an exact copy, but on the downside an exact copy may not be necessary and takes a huge amount of space.

SingleFile is a browser addon to save a complete web page into a single HTML file. SingleFile is a Web Extension (and a CLI tool) compatible with Chrome, Firefox (Desktop and Mobile), Microsoft Edge, Safari, Vivaldi, Brave, Waterfox, Yandex browser, and Opera.

SingleFile can also be integrated with bookmark managers hoarder and linkding browser extensions. So your browser does the capture, which means you are already logged in, have dismissed the cookie banner, solved the capthas or whatever else annoyance is on the webpage.

ArchiveBox and I believe also Linkwarden use SingleFile (but as CLI from the server side) to capture web pages, as well as other tools and formats. This works well for simple/straightforward web pages, but not for annoying we pages with cookie banners, capthas, and other popups.

Lol, I’m just over a week in to learning NixOS and this feels so true 😂

I feel like I’m just starting on the incline, luckily I don’t have any sturdy rope on hand 😂

Reading your post again, you should start by moving your docker management from CasaOS to vanilla docker-compose files, and keep them in a git repo.

I still think you definitely should look in to NixOS and what it can offer, cause it seems like that is where your mindset is going.

But NixOS is a drastic change, you should start by just converting your individual services one by one from CasaOS management to docker-compose files. One compose file for all services is possible, but I would recommend one compose file for each service. Later you can move from Debian to NixOS while using the same docker-compose files.

I would like to have a system when I know what I did, what is opened/installed/activated and what is not

You sound like you need to to look in to Nix and NixOS. The TLDR is that everything is declared in a configuration file(s), which you can and should back up in git. The config files tell you exactly what you did , and the config file comments together with git commit history tell you why.

The whole system is built from this configuration file. Rollback is trivially easy, either by rebooting and selecting an older build during the boot manager, or reverting to an older git commit and rebuilding (no reboot required, so usually faster)

Now fair warning, Nix (and NixOS) is a big topic, very different from normal way of thinking about software distribution and OS. Nix is not for everyone.

You should also at the very least have a git repo for docker-compose files for your services. Again, that will declaratively tell you what you did and why.

Also, if NixOS is too extreme, you should also look in to declarative management tools like Ansible etc

Not a problem when self-hosting on own hardware. Especially in winter. Overly complicated spaceheater goes brrrr

GUIs can be very good for getting started and learning concepts though. Much more “discoverable” and can allow for quicker iteration.

Then when learning the “proper” command line tools, the process should be easier as one already knows the concepts and terminology, and can concentrate on just the tooling.

The biggest problem with Discord is that its an information black hole. Its not properly searchable and not indexed by search engines.

Discord is fine for casual chat, but horrible when used for forum-type discussions and even worse when used for documentation.

You see the same problems being discussed and solved again and again, but you cant just “link” someone the solution like you could with a forum thread cause its spread out over 3-10 chat messages that are interleaved in-between other topics being discussed in the same room

Anything of long-term value for the project (forum-type discussions, documentation etc) should not recide in Discord