Use a message log to avoid dropping messages #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On top of #10, this PR records all the messages from
BIND_URLinto a log, and then uses that log to answer questions like the current playlist ID.Actually fetching the playlist data still doesn't work, but it should start to work again whenever a replacement for the
watch_queue_ajaxendpoint is found. (Doing that probably requires running the requests from the mobile app through an intercepting proxy, since YouTube's Chromecast support in the Chrome browser no longer supports viewing the playlist, and so the browser inspector can't be used to determine the endpoint to call.)