Open HanJoJ opened 1 month ago
Sorry, just noticed that there is some information about it being discussed already in #592 ... Somehow I must've missed that when I searched for "SyncYomi" before.
So unless you can "utilize" this issue for something else (like stating the current status on this) it can be closed.
no one is working on it.
I see. Now I'm wondering, do you have information whether this is because of the "prerequisite" mentioned in #592 not being fullfilled yet, or because there is no bigger interest in adding support for it in general?
the server generally follows mihon's feature set, if its not happened there then its not likely to happen here.
What feature should be added to Suwayomi?
(Optional) Setting to add synchronisation using the SyncYomi server to sync data with other supported Apps (only TachiyomiSY as of writing this, example is taken from there).
The settings would be identical to the ones currently implemented in TachiyomiSY (Preview):
When the sync process is started (automatic, trigger, manually) the defined data should be synchronised with the set SyncYomi Server and API key.
Why/Project's Benefit/Existing Problem
The existance of this project was shortly mentioned in #159, but it was primarily a mention of it existing. I am fully aware, that both projects, SyncYomi and SuwaYomi, have a similar idea of accessing the data / library on different devices and that there might be already be different plans for this. Personally, I really like SuwaYomis in-browser option which I can easily access on any device (with an active internet connection), however my main reading device is an Android tablet. While the WebUI is usable on it, it is (in my opinion) still not as good as the actual reader apps on the tablet and the current version of JUI is still lacking quite a few features other apps already implemented.
So by adding the option to also use SyncYomi to sync the data, users could have more freedom in choosing an app-fork in the future (as long as those forks also implement them). I'm certain it is planned to expand on the reader features in the WebUI and JUI in the future, but adding support for it might give the users more freedom of choice, especially if certain forks offer features that are not planned to be added to the WebUI / JUI.
At least in the current state it would already allow users to have one library they could access by 3 different ways then (TachiSY, JUI, WebUI) where all progress is properly synced between them.