Wölfchen

@s-and-witch from what i have gathered while working on trying to fix the memory leaks (and what i can remember of that, it's been a while) the issue is not...

then this is about the content shape. i'd be very surprised if your compositor matters at all here. can you attempt to replicate the same shape across compositors to be...

@ManiArasteh why not? why would you not want to accept a pull request aiming to fix the issue **you** reported? either provide a valid reason why or admit that you...

why didn't you just write that instead then?

why is the commit hash in the lockfile not sufficient? if we want to update the dependency, we manually have to do so. after updating dependencies, one should always **at...

see https://github.com/aome510/spotify-player/issues/520#issuecomment-2409041468 for my response, i don't feel like typing out the same thing twice. @ManiArasteh your behavior is killing my motivation to continue working on this pr, please stop....

that's appreciated but not an excuse for your behavior.

@stanekondrej thank you so much! currently, we seem to be able to log in and generate a token, but the function `Spirc::new` fails when called [here](https://github.com/w-lfchen/spotify-player/blob/a502b088c197b901537be535b722a790fb2c01b0/spotify_player/src/streaming.rs#L223). this is a problem...

@juliamertz thank you! i'm not sure either, but the application seems to work now, i've pushed a commit implementing your suggestion. i'll do some cleanup and more tests and then...

removed a premature [commit](https://github.com/aome510/spotify-player/commit/685291dbdfbe7d0f193a66f692ea300dbdf1686f) i pushed. it lead to scope issues when reauthenticating which i didn't fully test.