thayerw 9h ago • 100%
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
thayerw 10h ago • 94%
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.
thayerw 10h ago • 100%
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.
thayerw 6d ago • 100%
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.
**Update:** There's any existing bug report: https://github.com/aeharding/voyager/issues/1602 Original post: Fellow voyagers, For several weeks now I've been having Android keyboard issues when using the Voyager app and I'm just trying to figure out if it's a me thing, or a voyager thing. I use Gboard as my default keyboard, and I've noticed that when creating a post, or replying to a post by selecting a reply icon, the keyboard isn't raised into focus automatically. Once I manually select the input field, a completely crippled Gboard keyboard pops up. The keyboard defaults to lower case lettering, has no spell check or predictive text, and doesn't support any gestures, such as swipe backspace. If I then bring up the input method selection menu, it shows that Gboard is already selected. If I select Gboard again, or even just back out of the input method popup without selecting anything, a proper working version of Gboard now appears, with predictive text, swipe gestures, etc. If I reply to a comment by swiping left, the keyboard is immediately brought into focus and works as expected. Same goes for editing a comment. The issue only seems to appear when selecting a Reply icon, initiating a reply from the 3-dot menu, or when creating a new post. I can consistently repeat this every time, and it is only happening for me within the Voyager app. * Voyager v2.18.2 (app.vger.voyager) * Gboard v14.6.03.665297282-release-arm64-v8a (com.google.android.inputmethod.latin) Any thoughts? Edit: I found the related post here from last month. It sounds like it might be related to GrapheneOS, but it's strange that it only happens within Voyager. I'm wondering if Voyager is triggering input in a way that is contrary to GOS' hardened security.
thayerw 1w ago • 95%
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.
thayerw 1w ago • 100%
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.
thayerw 2w ago • 100%
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!
thayerw 2w ago • 100%
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
.
thayerw 2w ago • 94%
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.
thayerw 3w ago • 100%
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!
thayerw 3w ago • 100%
dnf autoremove
might do the trick. I'm on Fedora Silverblue, so thankfully don't have to worry about this anymore.
thayerw 3w ago • 100%
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.
thayerw 4w ago • 100%
That's an impressive list of changes!
thayerw 1mo ago • 100%
Mullvad VPN provides a variety of blocklists, including ads, trackers, malware, gambling, social media, and adult content.
thayerw 1mo ago • 100%
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.
thayerw 1mo ago • 100%
Hah any time, man! Your work and YT vids are what really got me hooked me on Silverblue and the cloud native workflow! I'll never look at computing the same way again lol.
thayerw 1mo ago • 100%
The biggest hurdles are unavoidable under stock Android, but it really depends on your needs. What are you trying to protect against?
thayerw 1mo ago • 100%
Hah nice, I'd never heard of this one but there's been plenty of times I've wanted to make a quick loop and didn't want to fuss with it in ffmpeg directly. Will definitely check it out!
thayerw 1mo ago • 100%
I still haven't taken any of the uBlue images for a spin, but I sincerely appreciate what they're doing and Jorge has been the perfect champion for the project.
I like to use upstream as much as possible. Partly to minimize breakage and complexity, but also for the increased security and overall focus of resources on a given project. That said, I have no doubt they're awesome builds and have helped win a lot of folks over to this way of computing!