Your community is so new that you might as well look to the few users who have contributed so far (OpenStars, Tux, etc). Clearly, they’ve identified with the group and may be interested. I would check out their comment history just to ensure their general behaviour aligns with your expectations, and go from there.

Same here, I use Silverblue as host OS on all of my workstations now, and Arch for nearly all of my containers.

Flatpak for just about everything in the userspace.

I can’t say that I’m surprised when a privacy-focused company has a dose of unfounded or biased paranoia. For me, this is not reason enough to distrust them.

I also don’t fault them for doing away with SMS when most of the populated world had already moved away from SMS by then too. As a North American relying on SMS for about half of my messaging needs at the time, I wasn’t happy about it either. But I don’t fault them for making that decision, and ultimately it did push me to rely on more secure options, which I see as a good thing.

Great shots, I love the low contrast moody tones. Definitely adding these to the mix!

Noooo! Ugh, that’s so disheartening to hear but I can’t fault imsodin for his reasons. I sincerely hope that someone steps up to the plate, even if only for the F-Droid releases.

For anyone else interested, the discussion is taking place here:

https://forum.syncthing.net/t/discontinuing-syncthing-android/23002/7

I can only speak for myself, but I would never trust opaque, proprietary software to manage my credentials, especially in a networked environment. For me, that’s a total showstopper.

I’ve never had need to use Bitwarden or Vaultwarden as I’ve always been happy with KeePass, but this news would definitely have me choosing an alternative.

For what it’s worth, I only ever had sync issues when sharing a database between devices with transient connectivity. Once I added an always-on instance of Syncthing into the mix, collisions were a thing of the past.

We’ve been using KeePass trouble-free for many years now, sharing a single database across more than 6 devices, with frequent use and modification.

It seems to be isolated to GrapheneOS users, but I do think it’s something that Voyager is doing since it isn’t happening anywhere else. Either there’s an issue with the reply function, or the way it’s being called in certain circumstances. Anecdotally, I recall that it started after a GOS update, and Voyager hadn’t been updated at the time. Maybe something changed in GOS’ Vanadium/WebView which has essentially broken Voyager.

Since adopting a Flatpak and containerized workflow, the choice of distribution matters a lot less to me now than it did 10 years ago.

The majority of apps that I use everyday can be run from any host. And I can install fedora, arch, debian, or whatever I want as a container, whenever I want it, without any thought to my host system.

Ideally, Flatpak’s UX will continue to improve, and upstream app devs will continue to adopt it as an official support channel, which will improve overall security and confidence of the platform. Image-based, atomic distros will be further streamlined, allowing for even more easily interchangeable host images. At that point, traditional distros will be little more than an opinionated collection of command line tools and programming environments.

If you want free tier with good privacy practices, Proton is going to be the best option.

I have several paid webhost accounts already, so I just use those for email. Any important messages (which are increasingly rare) are saved to PDF and stored offline (business/tax/medical info, etc.), and the rest is purged once read/sent.

Your fstab file can remain unchanged and still fail, if the drive or user identifiers have changed unexpectedly. It depends on how you’ve configured your fstab entries, which is why it’s helpful to share them. In future, no one will be able to offer much assistance without seeing the entry details. Either way, glad you were able to get it sorted!

Can you read/write to the disks as root? If so, then something has likely gone sideways with your fstab entry. For example, the device name, order, or UID/GID may have changed, depending on how you’ve configured the entry.

It’s difficult to assist much more without seeing the contents of /etc/fstab.

Despite some of the comments here, I suggest that you don’t overthink it; just buy an APC Back-UPS 600VA and be done with it. You have relatively low power requirements. The UPS will provide some surge protection (490J), several minutes of uptime, and a USB connection for automated shutdown.

The 600VA unit is less than $100 USD and replacement batteries are about half that. I’ve been using several of this same model for years without issue and we have many brown/blackouts being in a rural BC community. The batteries have lasted me 4-5 years.

You can always plan for something more significant down the road, if your hardware or needs change, but this should do fine in the interim.

I used DDG for the first link, but then searched Google with a portion of the error message in quotes. Either way, I’m glad it sorted itself out!

dnf autoremove might do the trick. I’m on Fedora Silverblue, so thankfully don’t have to worry about this anymore.

Sounds like a server-side issue to me. Found something similar from 6 months ago…and another here.

Lots of great responses here already. In terms of simplicity and ease of maintenance, Hugo is going to be the best solution with its single binary, built-in features, and ease of setup/use.

That’s an impressive list of changes!

Mullvad VPN provides a variety of blocklists, including ads, trackers, malware, gambling, social media, and adult content.

I experienced similar resizing issues with 47 and Flatpak Firefox, but in my case I was forcing FF to use Xwayland to accommodate my password manager. Once I enabled Wayland support in Flatseal, performance was back to normal.