You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Server-side sync for library sort order & display type (revisiting #1445)
#2085
At the risk of sounding like I'm beating a dead horse, I'd like to come back to the topic of server-side sync for library sort order and display type. I'm insisting a bit because, honestly, I still can't wrap my head around this choice or the reasoning behind it... 🤔
Let me try once more with a concrete comparison that shows where my confusion comes from.
The "UI Scaling" example
Moonfin lets you sync the UI Scaling setting server-side. No problem with that at all, it's a nice option to have. The more settings we can sync, the better!
But think about it: between a 70" TV and a 30" TV (both on Android TV), you will most likely not want the same UI size. So syncing this particular setting actually forces the same interface size onto very different screens. In other words, it's a setting that arguably makes less sense to sync.
Library sort order and display type are the exact opposite. Whatever TV I'm sitting in front of, I'd expect to find the sort order and layout I set up on the first one, without redoing everything on the second. And even more so after reinstalling the app!
The effort isn't comparable either
If UI Scaling couldn't be synced, that would be a shame, but fine: it's one setting to change on the new device and you're done.
For libraries, it's 2 settings × every single library × every device. With 15 libraries and 4 devices, that's 120 manual changes, versus 4 for UI Scaling. And that's without even bringing up my previous point: being able to fully configure a profile without having to be physically in front of the device.
So, why not?
Hence my genuine confusion about the reluctance to make these two settings (sort + display type) available server-side, when so many other, arguably less essential, settings already are.
Maybe the real reason is technical complexity? If so, I'd be happy to contribute if I can help in any way.
Otherwise, I'd really like to understand the reasoning: why so many things are offered as server-synced, and why this particular request can't be considered. ^^
Because let's be honest: these two settings are pretty much the only thing standing between this app and perfection! 😄
Huge thanks to everyone for the insane amount of work. The app looks incredible on my 55" Ambilight TV. I barely dare to open the stock Jellyfin client anymore, it feels like launching Netscape 😅
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi team!
At the risk of sounding like I'm beating a dead horse, I'd like to come back to the topic of server-side sync for library sort order and display type. I'm insisting a bit because, honestly, I still can't wrap my head around this choice or the reasoning behind it... 🤔
Let me try once more with a concrete comparison that shows where my confusion comes from.
The "UI Scaling" example
Moonfin lets you sync the UI Scaling setting server-side. No problem with that at all, it's a nice option to have. The more settings we can sync, the better!
But think about it: between a 70" TV and a 30" TV (both on Android TV), you will most likely not want the same UI size. So syncing this particular setting actually forces the same interface size onto very different screens. In other words, it's a setting that arguably makes less sense to sync.
Library sort order and display type are the exact opposite. Whatever TV I'm sitting in front of, I'd expect to find the sort order and layout I set up on the first one, without redoing everything on the second. And even more so after reinstalling the app!
The effort isn't comparable either
If UI Scaling couldn't be synced, that would be a shame, but fine: it's one setting to change on the new device and you're done.
For libraries, it's 2 settings × every single library × every device. With 15 libraries and 4 devices, that's 120 manual changes, versus 4 for UI Scaling. And that's without even bringing up my previous point: being able to fully configure a profile without having to be physically in front of the device.
So, why not?
Hence my genuine confusion about the reluctance to make these two settings (sort + display type) available server-side, when so many other, arguably less essential, settings already are.
Maybe the real reason is technical complexity? If so, I'd be happy to contribute if I can help in any way.
Otherwise, I'd really like to understand the reasoning: why so many things are offered as server-synced, and why this particular request can't be considered. ^^
Because let's be honest: these two settings are pretty much the only thing standing between this app and perfection! 😄
Huge thanks to everyone for the insane amount of work. The app looks incredible on my 55" Ambilight TV. I barely dare to open the stock Jellyfin client anymore, it feels like launching Netscape 😅
All reactions