Ansible playbook is perfect for this. All your configuration is repeatable, whether on a running system or a new one. Plus you can start with a completely fresh newest version image and apply from there, instead of starting from a soon-to-be outdated custom image.

Cool, thanks

It states the OpenStreetMap data is from May. Is it fully offline and needs to wait for the next app update?

Postgres handles NoSQL better than many dedicated NoSQL database management systems. I kept telling another team to at least evaluate it for that purpose - but they knew better and now they are stuck with managing the MongoDB stack because they are the only ones that use it. Postgres is able to do everything they use out of the box. It just doesn’t sound as fancy and hip.

Also, Kanban was invented in the 40s as a process for automotive production lines. That’s why it aligns so well with maintenance and operations projects in IT. It’s ridiculous how more and more people claim it comes from software development and would not fit hardware projects, when that’s the core use case of the methodology.

Modern browsers happily show you the actual characters, while sending their encoded entities to the server. So, from a user perspective there is no ASCII limitation. Case in point: söhne.at (just some random website, I have no idea what they are or if they are legitimate)

Sure, there were electric cars. But if I remember correctly, Tesla was the first to deliver the whole next-gen package with an every day, everywhere car, plus charging stations plus the whole automation. If you wanted that, there was no way around Tesla for quite a while.

Teslas were the “best”, as in the only option for what they did. They were never the “best”, as in better than existing products for what they did.

Being first to market for such a long time was an incredible feat and it speaks volumes that their position isn’t much, much stronger at the end of it.

When I installed Kinoite to start using Linux as my primary daily driver, the first thing I did was setting up Ansible, creating a new playbook and all Linux configurations I made from that point on, are only ever done through that playbook, which is backed up in my Forgejo instance. One command and everything is being set up exactly the way I want. It feels extremely liberating.

Windows hss supported slashes in both directions for a very long time. I almost exclusively use forward slashes to reduce mental load when switching between OSes.

To me it feels like it doesn’t do much better than the Google keyboard. But it does follow my custom dictionary while swiping, which Google never did. After all these years it still suggested a word I never use instead of a name I type often. Heliboard just casualty does the correct thing after adding the name to the dictionary. That plus showing the detected word directly above the finger so I can keep my eyes on one spot instead of constantly checking the text for bullshit words are killer features to me.

You can implement public or semi public ledgers without Blockchain. That’s what banks are doing already by sending huge CSV files internally and externally. Blockchain is not a technology of zero trust. It’s close to the opposite. You trust a few peers and blindly trust everyone they trust. That way you trust a network that you know nothing about and if the network decides on a common truth that you are convinced is incorrect, there is nothing you can do about it. The consensus always wins and there is no single entity to complain to and get it fixed. This is great for making sure that many actors need to be bad actors in order to have the whole system fail. It’s bad if you don’t trust anyone and want to make sure that your standards are always observed. From a technology standpoint I love the concept of Blockchain. But use cases that are not forced are few and far apart. Too few for the amount of hype it receives.

It depends. Some hardware degrades gracefully while my current desktop system won’t even boot and throws error codes on an empty battery. It took me hours to figure out what was wrong the first time it happened.

Coffee seems to be a self enforcing meme at this point. It’s not unhealthy enough to have suffered the same fate as cigarettes. Which had pretty much the same jokes not too long ago.

It’s the same argument. Getting a reasonable amount of charging is possible in 15 minutes. But not everyone has immediate access to fast charging stations. If everyone could always make a deliberate decision whether to go easy on the battery and save money or having to be places, EVs may look much more appealing to a lot of people.

It turns out there’s still plenty I don’t know, and I spend much more of my time confused and frustrated than I did before. The cool part is that I’m now confused and frustrated by really interesting problems.

This is spot on. Your whole response ist just a trove of insight, I wouldn’t have been able to articulate so eloquently.

Paperless -> Paperless-ng -> Paperless-ngx

Yeah, it’s the same for me. The content is awesome but requires a lot of concentration.

As you mentioned, with Fedora the best alternatives are immutable spins. Updating means downloading a new base image, applying overlays and additional installations to it and on the next reboot you start from that image. You can configure it to keep as many previous versions as you need and boot into those directly on startup. Since you never change your current image once it’s built, you can’t break a known good system. You can only ever break your next version and in that case, just boot the previous.

I’ve created an Ansible playbook that configures a vanilla Kinoite the way I want it. No need to back up the system if I can recreate it with less than a megabyte of text files. Secrets are in my password vault, personal files are in my personal cloud and get synced to and from the laptop continuously. I would never go back to backing up system files as opposed to recreating it with a playbook. That seems so wasteful in hindsight.

Flatpak with Fedora 39 must have come a long way. Almost every tutorial with workarounds or discussion of broken features you can find online is now obsolete. It just works out of the box, especially under KDE. Mostly. That makes searching for actual issues extremely hard because I find myself chasing down paths of issues that have long been resolved.