KoReader Sync #509
-
|
Does it work in both directions? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
It should work in both directions, but it won't maintain different progress states per device. KoReader sends some kind of identifier for the device being used, which Stump will attach to the record(s) it uses for tracking progress. Stump will update the device if it changes, but progress isn't loaded based off of the device requesting it. This means if another device asks for progress, it will send the progress from the other device (the record is shared). If the new device syncs progress, the device gets updated on that same record. I'll add that devices are stored in the database when they are first encountered, but nothing is surfaced on the UI for that yet. I have thoughts/plans to allow you to add nicknames/aliases for them. |
Beta Was this translation helpful? Give feedback.
It should work in both directions, but it won't maintain different progress states per device.
KoReader sends some kind of identifier for the device being used, which Stump will attach to the record(s) it uses for tracking progress. Stump will update the device if it changes, but progress isn't loaded based off of the device requesting it. This means if another device asks for progress, it will send the progress from the other device (the record is shared). If the new device syncs progress, the device gets update…