> There seem to have been some changes in Spotty. It now requests a client ID
> and a Web token.
None of the two is required. But both can solve some issues.
- the client ID can solve the issue where you'd get blocked ("rate
limite reached", status 429) by Spotify due to too many requests using
the shared client ID. I only made the message clearer in the latest
revision, as this problem has become a major painpoint recently
- the web token was required in the previous version if you wanted to
get access to additional content (the "Home" item). With 4.4.3 this
should no longer be required, but would be used to fall back to if the
default method failed. I'm probably going to remove the web token
handler again.
> According to the instructions I must create an app. Then I get a client ID
> and a secret. Must I assume the 'secret' is the 'Web token'?
No, the secret you most likely will never need. You might need it if you
implemented your own application with some special sign-in flow.
But really, forget about the web token for now.
--
Michael
> and a Web token.
None of the two is required. But both can solve some issues.
- the client ID can solve the issue where you'd get blocked ("rate
limite reached", status 429) by Spotify due to too many requests using
the shared client ID. I only made the message clearer in the latest
revision, as this problem has become a major painpoint recently
- the web token was required in the previous version if you wanted to
get access to additional content (the "Home" item). With 4.4.3 this
should no longer be required, but would be used to fall back to if the
default method failed. I'm probably going to remove the web token
handler again.
> According to the instructions I must create an app. Then I get a client ID
> and a secret. Must I assume the 'secret' is the 'Web token'?
No, the secret you most likely will never need. You might need it if you
implemented your own application with some special sign-in flow.
But really, forget about the web token for now.
--
Michael