KOReader Questions (Sync libraries, Clara 2E, Rendering)

[CleanYourNibs]

I have a few questions about KOReader, most of them probably infeasible (or theoretical) but I'm curious to a fault.

1. I know KOReader has SFTP support, but is there a way to use this to sync my library? I've got a couple ereaders with KOReader, so being able to do it this way (instead of needing to plug them in one after the other) would be nifty. I imagine I'd need to write my own .sh for it, but I figure it's better to ask if it's even possible before I try. For reference, this includes Kobos (where I don't imagine it'd be a problem) and a Kindle.
2. Why is there no equivalent to KoboUSBMS for Kindles? Is it a solid limitation (due to Kindle firmware being finicky) or is it just a low priority thing?
3. What makes the Clara 2E and the Libra 2 buggier on KOReader?
4. Is there a way to make books render faster or be able to be read while rendering? I've got some very large books (if you get the physical set, it's something like 27 volumes) and rendering can take about five minutes. It's so big that you've basically got to wait that long any time you try opening that file. Being able to read a little, even if the page count isn't accurate, would be nice.

[mergen3107]

1) There is a plugin called Progress Sync. Have a look at the KOReader Wiki on Github.
2) Kindle OS is pain for external apps to run. Linux shell plus Java runtime and shenanigans with fused storages comprise the injustice league lol.
3) Kernel. So it is difficult to mitigate via software. Not only KODeader, but their own Nickel hangs from time to time, go figure.
4) No, not really for reflowable documents. You should divide these volumes in smaller books.

[CleanYourNibs]

1) That syncs progress, and not the books themselves. That's on me for being unclear about what I meant by sync.

3) Does that mean that Kobo could release updates that have added stability? (Funny, actually wanting an update that says "Improved stability!")

4) The issue with doing that is that there's a lot of hyperlinks, but it's also an outlier. No other omnibus is anywhere nearly as intensive, so I'll probably just read it in Nickel if I can't find a workaround for it, since breaking it up manually sounds very tedious.

[mergen3107]

1) Ah sorry. Yes, you need to come up with something custom by now.

3) I wouldn’t put my high hopes in updates, because the hardware platform is faulty, not the software.

[CleanYourNibs]

Ah, so it's more in the realm of "whatever hardware they used is (for lack of a better word) finicky and the drivers in the kernel aren't going to be great" than "they botched the kernel and can simply update it whenever enough people complain". Shame, but it's stable enough most of the time.
Thanks for the quick responses!

[mergen3107]

You’re welcome! Yeah, they are not bad per se unless you pull a direct comparison or switch from a more stable device.

[Ken Maltby]

Regards your #1; there once was a "ZSync" share/publish/copy a book you are reading, in KOReader from one device, to other devices running KOReader.

Luck;
Ken

[NiLuJe]

We murdered that at least a year ago, as it was unmaintained .

[Ken Maltby]

Perhaps, with an older version of KOReader running (like mine), it would still work.

Luck;
Ken