I appreciate the writeup and that you’ve taken the time to post about it here, however I am 100% leery of managing remote access or credentials using closed source software. I’ll definitely keep an eye on the project, but it’s a hard pass for me until the app is fully open source.
I hear Anna’s Archives is great for ebooks. I don’t do audiobooks, and can’t stand podcasts, but it sounds like a lot of good suggestions were made for those already.
Simple SMS, obtained from F-Droid, is probably the best universal option until the Fossify project adds the fork to their suite (assuming they do).
If you have the ability to toggle network access for your apps (GrapheneOS, etc.), Google Messages is a very solid SMS app that receives regular updates. I would normally only recommend FOSS apps, but many of those options are limited and/or dangerously outdated for SMS.
I too like to review changes between images, but I’m just as content to run rpm-ostree status and/or rpm-ostree db diff to see what exactly has changed.
You should be forced to reboot though? And if you don’t want to reboot, can’t you just do an --apply-live?
I’m hoping to eliminate the extra reboot each day that is usually necessary to activate the latest image. I know that a lot of this will depend on exactly when the image drops from the repos (versus when I shutdown a host), which is why I was looking for some general feedback from others who might have done the same thing…I didn’t know if it’d be worthwhile in the long run, but I guess there’s only one way to find out. As for the –apply-live, I use it on occasion but I don’t want to rely on it for system updates (if that’s even possible).
Thanks, yeah I’ve found a few articles already on running scripts at shutdown…something like this should do it (using Tony Walker’s update script), though I’ve not tested it yet:
I was an rxvt/urxvt fan for nearly 20 years, then Alacritty for a while. Nowadays, I just use gnome-terminal and I’ve been happy with it. Looking forward to trying Prompt though.
5 days later: Prompt is the bee’s knees! Highly recommend for anyone wanting a snappy, feature-rich GTK4 terminal, especially if you work with containers.
My vote is Fedora. It offers fresh yet stable packaging, and a polished experience that you can rely on. You can then use flatpaks for even newer apps, or opt to run Arch in a container with distrobox/toolbox and play with as many cutting edge apps as you want, all as if they were installed on the host.
Finally, if you like what you see in Fedora, consider trying Fedora Silverblue, Kinoite, or any of their other immutable distros.
The best and most official explanation I’ve read is the 2017 GNOME blog post, Status Icons and GNOME.
Essentially, tray icons are a throwback to the days before designated notification and media playback APIs, and they now create some ambiguity for app developers, in addition to being ripe for abuse.
It’s a worthwhile read and the writer makes several valid points, but doesn’t address as much as I’d like in terms of actual solutions for things like instant messengers.
Personally, I would be happy if most traditional tray apps could be displayed in the dash, with status indicators, and started in a minimized state, but I still see the benefit of having some always-visible panel icons, such as instant messengers and VPN indicators.
I don’t think you’ll be able to build anything with €100, but you might be able to buy an old PC or laptop locally and use it as is. I’ve never run nextcloud myself, but from I’ve read it’ll be the most taxing service on your list. Everything seems pretty minimal, though I don’t know anything about Photoprism.
While I’m a big fan of Vim, it’s definitely not for everyone.
I spend about half of my writing time in VSCodium, which is a community-based release of Microsoft’s open source VS Code editor. There are several markdown, grammar, and focus-oriented plugins for the platform, and you can pretty much shape it into whatever kind of editor you want.
I use VSCodium for the vast majority of my personal notes, technical writing, and project documentation (nearly all of which are written in markdown format).
I won’t pretend to know how tightly integrated the keyboard is within the Android OS, but given the interoperability between app and keyboard it seems likely that vulnerabilities could be leveraged to gain malicious access to the clipboard and other sensitive data.
It seems that BT 5.3 in USB format is a challenge to find, let alone support under Linux. If 5.0 is acceptable, the TP Link UB500 uses an RTL8761B chipset which has been supported since around kernel 5.16.
I have a few UB500 and UB400 adapters and both have worked OOTB without issue under Fedora.