diff options
author | (quasar) nebula <qznebula@protonmail.com> | 2023-05-13 22:11:58 -0300 |
---|---|---|
committer | (quasar) nebula <qznebula@protonmail.com> | 2023-05-13 22:11:58 -0300 |
commit | 56ad0bab6cbcc079887d5a5086cb116844bc351e (patch) | |
tree | 03a29da7de303bd985461aed5b69cea51741338c | |
parent | 4ea5e57d2b6c12f42ff21c4b43056021553f07a0 (diff) |
tododododododo
-rw-r--r-- | todo.txt | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/todo.txt b/todo.txt index da6c9e6..d1cb2cc 100644 --- a/todo.txt +++ b/todo.txt @@ -738,3 +738,15 @@ TODO: GHOST BACKEND for socket server... the main thing is syncing duration data. It sucks to have the player, like, actually be tied to a specific instance of MPV or whatever, so we'd use a ~ghost player~ which supports all the usual interfaces and lies about its current playback time. Yay! + +TODO: There should be a way for the server to handle disputes between two + clients disagreeing on the duration of a track. Options could include, + for example, "longest": always wait for everyone to be done playing; + "shortest": don't wait for anyone to be done (past a 1 second threshold + or whatever), just skip to the next track almost right away; and "first", + where duration just depends on whoever shared the track. This can all be + done without everyone sharing their own playback duration, which is kinda + wasteful; it would be controlled totally by the server deciding when to + send out events to start the next track, and in reaction only to the + clients' own "done playing" events (or the GHOST PLAYER reaching the + playback time provided when the track was first shared). |