2024-04-18, 02:23 AM
(This post was last modified: 2024-04-18, 03:00 AM by douglasparker. Edited 4 times in total.)
(2024-04-09, 07:12 AM)niels Wrote: Screaming "this is keeping me away from Jellyfin" doesn't help at all.
This isn't my intention. I linked to numerous bugs and have communicated about it quite a few times on Discord, including going into details about server specs, network conditions, web server configurations, etc.
(2024-04-09, 07:12 AM)niels Wrote: We have tons of users without any SyncPlay issues, you gotta be a bit more specific in what is going wrong. We have a big team of contributors and if there is a clear issue description with reproducible steps the changes of it getting fixed are high.
This is simply not true, it is well known that there are major issues with SyncPlay. People have been discussing it for years, and nothing has been done to resolve it. I myself have dedicated time to debugging to try and assist in finding a solution, but I am told that nobody is taking ownership of the current SyncPlay code and it will likely NOT be fixed unless we do it ourselves.
That said, I know everyone here is a volunteer. I know there is a lot of work to be done, and nobody is being paid to do it. So I do not blame anyone, especially for a free offering such as Jellyfin-
That said, many people have tried assisting in debugging and nobody has seemed to want to fix it- So I highly disagree with what you said about the chances of getting it fixed being high.
If you personally want to take accountability for fixing SyncPlay- or someone else on the dev team, I would be more than willing to work with you all to fix SyncPlay. Please let me know where we can discuss the matter and I will make sure that I provide everything you need to debug.
EDIT:
Seems like you're aware of a lot of the issues people are having as well-
Once again, let me know if you want to take charge and help get this fixed for everyone. I personally would gladly pay money to have this addressed. If there is a way we can fund this, we can discuss that too.
I've just seen this discussed for years and it doesn't seem like the chances of getting it fixed are high, as you said.
EDIT:
For full transparency, I've been ignored as well as many others on those GitHub issues. Looking forward to the high likelihood of getting this fixed. If we can get communication from the dev team we can get them the info needed, but nobody responds and stalebot just marks the issues as stale.