Open playful1510 opened 1 year ago
Pull moved to https://github.com/tachiyomiorg/tachiyomi/pull/9675
Pull moved again to https://github.com/tachiyomiorg/tachiyomi/pull/9790
Also, I would mention SyncYomi - server that's doing "Sync magic"
Pull moved again to mihonapp/mihon#40
Since SyncYomi is a separate server that needs to be run anyway, wouldn't it make sense to just implement the server-side part of Tachi sync in the Suwayomi server so that clients can sync directly to it? That would halve the number of applications needed for those running it on a server (and, in doing so, the number of moving parts and their maintenance burden on server owners) and not negatively affect those not doing so. The API of SyncYomi doesn't seem particularly small, so that undertaking might be too expensive, but it seems very useful.
Since SyncYomi is a separate server that needs to be run anyway, wouldn't it make sense to just implement the server-side part of Tachi sync in the Suwayomi server so that clients can sync directly to it?
I believe @KaiserBh once said that he will PR an implementation in Suwayomi once Tachiyomi/Mihon merges support, the only issue is that they are taking forever to review and merge the code.
Another approach that we considered was implementing a special Suwayomi sync backend using the existing API directly in Tachiyomi/Mihon.
What feature should be added to Tachidesk?
As it seems that vanilla Tachiyomi is getting a sync service in the near future, it seems like it would be a good idea to move in line with their method of sync, rather than having to install a separate extension/tracker.
Why/Project's Benefit/Existing Problem
By moving in line with Tachiyomi's sync method, it should make it easier to keep everything synchronized between libraries, and will ensure interoperability.