fivebanger

I don't want to keep this issue pending so I added a PR that fixes the issue for me. Providing two similar `get_token()` functions is maybe not the smartest way...

I have the following understanding: Current dev (v0.6.0-dev?): - `get_token()` is not used any longer by librespot core, `login5().auth_token()` is used instead. - `get_token()` is only used by the get_token...

``` let my_session_config = SessionConfig::default(); info!("Client id: {0}", my_session_config.client_id); ``` returns ``` 2024-10-30T11:56:04Z INFO librespot] Client id: 65b708073fc0480ea92a077233ca87bd ``` always when running librespot on Linux. Should be always this client_id,...

My feeling is, having both functions `get_token()` and `get_token_with_client_id()` provides the most flexibility: One function for convenience and one in case someone wants to provide a custom client_id (or simply...

I have updated the comment for function `get_token()`. BTW, there was another issue revealed when digging into the original problem with respect to getting tokens at startup. There were some...

I have merged the changes from https://github.com/kingosticks/librespot/commit/24bbc6314c991c64d1846162f739f223c44e5779 into my code, based on v0.6.0 release. I'm running librespot + changes without any issue. I'm using default features, compiled for Windows, PC/Linux...