Telegram is worse than even Whatsapp, since it’s not even pretending to be end to end encrypted.

The real choice is signal or threema.

This is a double edged sword. You risk hostile takeover if the Dev has bad intentions and you risk suddenly being off the store if the Dev account gets blocked for one of the other apps. For me it would not be worth the hassle.

Just a few posts down my lemmy stream:

https://literature.cafe/post/31346850

That’s what some people claim. If I remember correctly, it was determined that these large scale prestigious events are a net negative.

I agree, the ecosystem seems to be focusing too much on hype and not enough on a strong and secure foundation. I’m still hoping for the best but I feel must more hopeful towards Linux on mobile devices. They are moving at an excruciatingly slow pace, though. Not enough resources and hands.

I didn’t say they need to rip something out. I didn’t say their current efforts to open up weren’t valid. I specifically said that I don’t know whether it would have made sense to start with reduced requirements.

I just stated that they didn’t “happen” to only support Google. I simply acknowledged how they knew exactly that the standard they were writing would only be matched by one vendor as they were writing it.

Google just happened to be the only company meeting those requirements

I don’t know. They designed the requirements in a way that only Google met them. It didn’t “happen” to meet them after the fact.

It’s like demanding yellow hard hats on a construction site. Sure, they are safe and highly visible. Would it make sense to allow black hard hats as well if it means not locking into a single vendor and try pushing for high vis while having a stronger base? And also working around the issue with a vest? I don’t know the answer to that but it’s clear that they have made a conscious decision to move into the situation that they now find themselves in.

Isn’t graphene having a challenging future because they have vendor locked themselves into pixel phones and said vendor is pulling the rug by not providing drivers going forward?

Just install a panic button. The microphone is not reasonable since there are way less intrusive options available.

That’s what containers are for. Fucking up the container won’t fuck up the host. That was the best decision in self hosting I’ve done. Even that one virtual machine feels weird and uncomfortably legacy now but it needs to interact with hardware in a certain way that just won’t fully work with docker.

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.

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.

Cool, thanks

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

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.

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.