I find keep terrifically useful. But it is not supported by Google Takeout, so when they turn it off, I'd lose everything. I'm currently trying out sNotz from f-droid as a replacement.
bet
joined 1 year ago
I got started with RSS using a TUI program on unix, whose name I forget. But then Google came out with Reader (and Listen for podcasts). When they lost interest and dropped them, I exported my OPML and switched to apps I could find on f-droid. Now I back up my OPML scrupulously and am currently happy with Feeder and Antennapod; Google taught me I didn't want to depend on someone else's server for something like this; it's too important. If ever I find I want some feature that requires a server, I'll self-host something (Nextcloud?), but I seem to be well enough served by purely local clients.
Thanks! That sounds like a fun exercise for my next phone
I run LineageOS on my Nexus 6, to get ongoing security updates. I also keep one other sacrificial phone running stock android with bootloader locked, so no more security updates, but I don't run anything on it but my banking app, since it's too insecure.
I don't do Windows, but I happily sync directories between my Android phones and my Linux PCs (especially a cloud server I lease) with rsync over ssh within Termux.
If you can set up an rsync server on Windows that should work. Besides actually implementing robust and efficient sync, rsync is also smart about platform differences.
For the specific case of Windows to Android, I've heard of people scripting up tools to shove all the contents of a directory over adb push.
Jerboa. When my previous preferred discussion forum decided to erect a paywall, closing out third-party apps, I came here; and searching for Lemmy on f-droid got me Jerboa. For a while, the app was spontaneously exiting, but before I was driven to try another, it seemed to have gotten fixed.
In the sense I think you're asking, never: contributing a fix or an improvement is never a one-and-done, fire it off and forget it edit. Each contribution is a request to open a dialog. Implicit in each pull request are multiple questions, perhaps including "is this a good idea", and "do you like this attempt to do it".
If the project maintainer who reviews your PR doesn't like it, they can expend the effort to try to explain why, and teach you. So try to make their job easier, by opening with a clear explanation of why you're doing it, and if what you did involved design decisions, why you chose as you did.