Currently we have an experimental VFS feature on all platforms that is using some suffix appended to files when they are virtual empty placeholders. https://github.com/nextcloud/desktop/issues/3668
Yeah, no thanks. It’s a very hacky work-around and breaks the moment you use an application that tries to access the files directly.
OS-level support for cloud storage. OneDrive, Dropbox and all the others work seamlessly on Windows through the Windows API. You can browse all the files on the file system and once you access them, the OS will call back the cloud provider to download them. It works through all applications, all cloud providers. I am aware that some tools on Linux have something similar to work around the issue in user land. Some solutions are less worse than others but none of them are as good as on Windows.
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.
It states the OpenStreetMap data is from May. Is it fully offline and needs to wait for the next app update?
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.
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 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.
Fresh and most up to date kinoite installation last week, based on fedora 39. The problem is not Linux, it’s proprietary codecs and Firefox’ hesitation to enable hardware decoding on Linux by default. It’s not difficult to get it to work but it simply does not work out of the box.
Linux, browsers, and hardware accelerated videos on the web don’t go along well out of the box. Which is a total shame.
The Lenovo business models (ThinkPad series) are amazing value. My 11 year old laptop is still going strong.
Just stay far away from any Lenovo non-business models.
The Tesla truck is already there and just needs to be built at scale.
Full self driving has been fully achieved in 2017 and will reach end consumers next year (as claimed by Tesla every single year since then).
It is desirable that SpaceX rockets fail hard instead of succeeding in their missions.
Musk has truly mastered this principle and only now are people getting impatient. Most investors still regard him as too big to fail. Either Elon will be able to present sufficient success in the next few years or that bubble will burst very violently. He has almost used up the good will he has built up over years (earned our not).
My (self-hosted) cloud storage is larger than the disk drive on my laptop. On demand sync is important to me. I really, really hope Linux will catch up to Windows in that regard.