My E-Reader Setup (Mk II)
By Christopher Burg
This is an update to my original post about my e-reader setup. Since I wrote that, I experienced major performance issues with AnnotationSync. The issues aren't consistent and impact functions beyond syncing data. When the AnnotationSync plugin is installed and enabled in KOReader on some of my devices (this issue doesn't manifest on my laptop or Boox Palma 2), things like bringing up the top or bottom menus will cause the program to lock up long enough that Android offers to kill the application. If I continue waiting, the menu will open but it can take minutes. I initially experience the issues on my Boox Go 6 (Gen II) and thought they were related to the lackluster hardware of that device. However, I experienced the same performance issues on my Pixel 10a, which is quite powerful. The performance issues went away when I disabled the AnnotationSync plugin so I knew that was the culprit.
Due to this, I had to find a different solution for syncing my reading progress between my various devices. I learned that there aren't a lot of Android applications for syncing files between a device and a Nextcloud instance. The Nextcloud application can only do automatic uploads from a device to a Nextcloud server of new files. It can't detect when a file has changed. This means the initial KOReader metadata for a book will be uploaded but no updates (such as reading progress) after that. I briefly considered Syncthing-Fork, but dismissed it when I couldn't find an up to date version of Syncthing for Linux that could be installed via Flatpak (my laptop runs an immutable Fedora-based distro so installing Syncthing via the official Debian packages without spinning up a Distrobox instance isn't an option).
Eventually I settled on the same tool I use to sync my notes: git. KOReader defaults to storing metadata like highlights and reading progress in a subdirectory of the directory where the e-book is stored. The metadata is stored in text-based files, which makes them ideal for syncing via git. I installed GitSync on my Boox e-readers and turned my KOReader directory into a git repository.
I've mentioned in a previous post having performance issues with GitSync. I still have those issues, but only on my Pixel 10a. GitSync runs fast on my Boox Go 6 (Gen II) and Palma 2. The performance issues appear to be specific to GrapheneOS (killing GitSync on my Pixel and restarting it fixes the performance issues temporarily).
There's still the issue of me not trusting the Boox devices since the both run Android 13, which is no longer supported. Like my Nextcloud-based sync setup, I create a new account on my Forgejo server for my KOReader instances. Each device accesses the repository via a unique access token that only grants read and write access to that single repository. To make it easier for me to add e-books to the repository, I added my main user account as a collaborator to the repository. The e-readers still connect to my guest Wi-Fi network, which isolates any device connected to it from anything on the local network, so they lack access to anything other than the Internet. This means any damage they can do if they're exploited is limited, especially since I don't have any personally identifiable information on the devices.