-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Is login_oauth_simple still relevant? #284
Comments
Well currently, yes. login_session_file() calls login_oauth_simple() (or login_pkce().) so it is definitely used. You have multiple ways to login, but I suggest using the login_session_file() in most cases. I do think we should cleanup the methods related to login, perhaps combine them and make some of them protected member classes to avoid calling them directly.
Yes, by setting the quality to high_lossless, you can still use the get_url() method. |
Hello, getting back to this, I have to tell you that I don't use the login_oauth_simple() anymore in my code. Would you accept a pull request removing this method and cleaning up the code if needed? Edit: sorry I inadvertently closed the issue |
Well it is used in python-tidal, so we cannot remove the method (yet). See my previous answer.
|
yes, sure you are right, maybe we can make it private as you were saying? |
Hello, in an effort of cleanup up the code of my tidal plugin for upmpdcli and remove unnecessary old stuff, I was wondering whether the login_oauth_simple method is still relevant. It seems to me that it eventually calls the login_session_file method, but I am not sure if something is different from calling that method just after creating an instance of the Session class.
OTOH, is there still a way of forcing streaming from FLAC files and avoiding MPEG-DASH, even if this means to lose access to hires content? That would still leave the change to select players that are not able to natively process MPEG-DASH.
If that is not possible, I'd like to clarify that in the documentation of the plugin.
Thank you for any help!
The text was updated successfully, but these errors were encountered: