Portability is the key for me, because I tend to switch things around a lot. Containers generally isolate the persistent data from the runtime really well.
Docker is not the only, or even the best way IMO to run containers. If I was providing services for customers, I would definetly build most container images daily in some automated way. Well, I do it already for quite a few.
The mess is only a mess if you don’t really understand what you’re doing, same goes for traditional services.
Most likely, a Hetzner storage box is going to be so slow you will regret it. I would just bite the bullet and upgrade the storage on Contabo.
Storage in the cloud is expensive, there’s just no way around it.
There was a good blog post about the real cost of storage, but I can’t find it now.
The gist was that to store 1TB of data somewhat reliably, you probably need at least:
Which amounts to something like 6TB of disk for 1TB of actual data. In real life you’d probably use some other level of RAID, at least for larger amounts so it’s perhaps not as harsh, and compression can reduce the required backup space too.
I have around 130G of data in Nextcloud, and the off-site borg repo for it is about 180G. Then there’s local backups on a mirrored HDD, with the ZFS snapshots that are not yet pruned that’s maybe 200G of raw disk space. So 130G becomes 510G in my setup.
Imagine if all the people who prefer systemd would write posts like this as often as the opposition. Just use what you like, there are plenty of distros to choose from.
I have a feeling you are overthinking the Matrix key system.
Basically it’s just another password, just one you probably can’t remember.
Most of the client apps support verifying a new session by scanning a QR code or by comparing emoji. The UX of these could be better (I can never find the emoji option on Element, but it’s there…). So if you have your phone signed in, just verify the sessions with that. And it’s not like most people sign in on new devices all the time.
I’d give Matrix a new look if I were you.
resolvectl flush-caches just in caseLook at resolvectl dns to check there’s no DHCP-acquired DNS servers set anymore
If you use a VPN, those often set their own DNS servers too, remember to check it as well.
This is true, with a couple gigs of RAM and SATA storage Nextcloud is not at all bad. Assuming an instance with not that much simultaneous users.
It feels like slow sometimes, then after an hour with M365 at work it doesn’t feel slow at all.
There’s a base image of ublue, which is Silverblue without a DE. I’d suppose you can mostly just layer e.g. Sway or i3 on top.
Traditional package model will still have it’s usage, of course, I agree. But if Silverblue works for a developer like me, I’d say a for more “regular” users immutable distros seem like a very viable option.
I recently put the nvidia variant of ublue-os on my work laptop, which has Optimus graphics. Couldn’t be happier.
It’s great to see these variants popping up! I really think ostree may be the future for desktop Linux, and not even very far away.
Flashing the stock Pixel ROM back is just as simple as flashing GrapheneOS, the instructions in GOS website are very good for both.
The only two things I can think of that might be issues are banking apps and Google Pay, if you use that. I use Play services in the main profile and honestly there’s not much difference to the stock ROM in terms of user experience. Even Android Auto works nowadays.
For the banking apps, you can have a look at https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/. Just note that if your bank is not on the list, it doesn’t necessarily mean it wont work.