2024-04-18, 08:13 AM
Look, I didn't say we're not aware of the issues. We know they are there. But they are not that significant as most users make it appear to be. SyncPlay works fine in a lot of cases. Only when it breaks, it breaks hard, we know that as well.
The unfortunate part is that we want to fix it but most of the server team members don't have the time to invest in it or don't care about the feature (which is fine). I'd love to fix all the SyncPlay issues myself but I also don't have that time (I'm primarily the maintainer for the Android apps, all other stuff I do are "extras").
My message from a month ago that you digged up was in a reply to someone trying to figure out how SyncPlay is implemented to potentially work on fixing it. I'm not sure what the status of that is now.
Regarding the stale issues, we have created a triage team a few months back that are actively helping out with the issues on the server and web client repositories. This team tries to make sure invalid reports are closed (e.g. configuration issues) and valid reports are reproducible/confirmed. If you think they wrongfully closed an issue please let them know (with as much detail as possible), if an issue was closed as stale earlier; please recreate, as our issue template has changed.
Regarding my previous comment in this thread, it wasn't directed at you but the other commenter.
The unfortunate part is that we want to fix it but most of the server team members don't have the time to invest in it or don't care about the feature (which is fine). I'd love to fix all the SyncPlay issues myself but I also don't have that time (I'm primarily the maintainer for the Android apps, all other stuff I do are "extras").
My message from a month ago that you digged up was in a reply to someone trying to figure out how SyncPlay is implemented to potentially work on fixing it. I'm not sure what the status of that is now.
Regarding the stale issues, we have created a triage team a few months back that are actively helping out with the issues on the server and web client repositories. This team tries to make sure invalid reports are closed (e.g. configuration issues) and valid reports are reproducible/confirmed. If you think they wrongfully closed an issue please let them know (with as much detail as possible), if an issue was closed as stale earlier; please recreate, as our issue template has changed.
Regarding my previous comment in this thread, it wasn't directed at you but the other commenter.