AyeZeeBB 83f148390a Spotify device and streams: secure connections of their own, not Windows' ...

nder Wine and Proton the Spotify device signed in but was never taken up
by Spotify as a device to play on: librespot never logged "active device
is ...", nothing could be started on it, and after a minute and a half its
control connection failed ("Websocket connection failed: Remote sent after
having closed"). Its HTTPS and websocket went through Windows' security
layer, which there is Wine's own.
librespot and reqwest are now built with rustls and its built-in
certificate authorities (rustls-tls-webpki-roots, ring) in place of
native-tls, so the same code makes the connections on Windows and under
Proton. This covers the Spotify device, online radio and anything else
fetched through the helper. Not yet confirmed on Proton.
Cargo.lock changes with it. ReSkate.dll is about 2.5 MB larger.

2026-10-13 18:05:06 -05:00

..

.cargo

Music: Spotify, YouTube Music and External Audio through the in-game player

2026-10-12 03:16:36 -05:00

examples

Music: local files, online radio, equaliser, queue, and a Music page in the menu

2026-10-12 16:03:35 -05:00

src

Music: local files, online radio, equaliser, queue, and a Music page in the menu

2026-10-12 16:03:35 -05:00

Cargo.lock

Spotify device and streams: secure connections of their own, not Windows'

2026-10-13 18:05:06 -05:00

Cargo.toml

Spotify device and streams: secure connections of their own, not Windows'

2026-10-13 18:05:06 -05:00