Use Login5 Authentication Instead of Keymaster#311
Merged
kokarare1212 merged 1 commit intokokarare1212:mainfrom Aug 17, 2025
Googolplexed0:login5-auth
Merged
Use Login5 Authentication Instead of Keymaster#311kokarare1212 merged 1 commit intokokarare1212:mainfrom Googolplexed0:login5-auth
kokarare1212 merged 1 commit intokokarare1212:mainfrom
Googolplexed0:login5-auth
Conversation
Googolplexed0
added a commit
to Googolplexed0/zotify
that referenced
this pull request
Aug 17, 2025
fix #48 (once librespot-python accepts my pull request at kokarare1212/librespot-python#311) version bump v0.9.20
Owner
|
Thank you for your contributing! |
This file contains hidden or 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.
Fixes #306
It has been assumed that the previous keymaster flow for reauthenticating previous credentials has been depreciated. It is rarely used in the official client in favor of Login5.
I can't confirm it is 100% bug free, but I haven't had any issues so far. Based off a similar fix by @ermitovski here. I did a bit of cleaning and reformatting to match existing code conventions.