oauthclientbridge VS psst

The way auth tokens are setup for Mopidy-Spotify *you* hold the encryption key for the blob with the OAuth data, and the intermediate server just has an id and the encrypted data. Note that the id is not a Spotify OAuth client-id but an internal one. This is done so we don't have to ship Mopidy-Spotify with the client-secret for the App registration (this was pre PKCE auth).

I.e. I would be highly surprised if our OAuth integration was the source for this issue, but I'm obviously biased as the author of https://github.com/adamcik/oauthclientbridge

As for libspotify, there you had to put in a (device) password and username, so if something scraped that config I guess all bets are off...

On the other hand, this Rust-based one called Psst looks awesome and works: https://github.com/jpochyla/psst

Psst but currently very limited in features and have to build yourself.

psst, https://github.com/jpochyla/psst

I don't know how can I install this open source software from github.

Would like to add that you can also use clients such as spotify-qt and Spotify TUI to control said "device". There's also Spot and psst that are standalone (librespot not required but no Connect functionality).

You can also take a look at Psst. I use Symphonia for decoding and CPAL or CubeB for output. CubeB is a bit nicer.

There's also this project, written in Rust, which is a great GUI Spotify client https://github.com/jpochyla/psst

There‘s a Spotify client, psst, which has an Async widget (with a Promise state struct) that works very well for loading states etc. That project has a bunch of other tidbits and interesting patterns for Druid, I learned a ton from the code.