spotifyd VS spotify-qt

For those unaware, it's possible to use alternative clients for Spotify using a 3rd party daemon.

https://github.com/Spotifyd/spotifyd

If you want to run Spotify on a Raspberry (or PinePhone or some other device), there’s Spot, which is great, but kinda heavy and slow. There’s Spotify-qt which is faster, requires messing with Spotify developer dashboard, and UI doesn’t fit on small screens. Spotify-qt is itself based on Spotify-tui which runs in the terminal (pretty cool IMO). And a bare client/daemon is spotifyd. So you have quite a few choices there.

Spotifyd runs on Linux, can also be recognized by Spotify app as an output requires premium, not sure about touch screen compatability

None of the maintainer staff use Windows, but a working PR that doesn’t cause any regressions would likely be accepted.

[1] https://github.com/Spotifyd/spotifyd/pull/602

Spotify https://github.com/Spotifyd/spotifyd

https://github.com/Spotifyd/spotifyd/blob/master/contrib/spotifyd.service and the service file, see how it has WantedBy=default.target under [Install]? pretty sure it starts/enables when that target is reached during the init process of the system.

Better yet would be to use spotifyd[0] for this. I tried to set this up with my RPi a while ago but was defeated by Linux audio. Instead I just bought a Sonos. Oh, well.

[0]: https://github.com/Spotifyd/spotifyd

I'm trying to cross-compile Spotifyd for a 64-bit Raspberry Pi. But whatever I try, I end up with an error at the final linking step:

If you want to run Spotify on a Raspberry (or PinePhone or some other device), there’s Spot, which is great, but kinda heavy and slow. There’s Spotify-qt which is faster, requires messing with Spotify developer dashboard, and UI doesn’t fit on small screens. Spotify-qt is itself based on Spotify-tui which runs in the terminal (pretty cool IMO). And a bare client/daemon is spotifyd. So you have quite a few choices there.

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).

spotify-qt, https://github.com/kraxarn/spotify-qt - in the repos

You could use an an unofficial client, for example: - Spot (GTK, can stream directly) - spotify-qt (QT, just a Spotify connect frontend, so you need something like spotifyd running) - spotify-tui (terminal, again just a Spotify connect frontend) - spotifyd (daemon that is controlled via Spotify connect)

IIRC, Spotify requires that you be a premium user to have API access to be able to use unofficial native clients like this one, and Discord will straight up ban your account if you try to use a third party client too much. BetterDiscord is a mod for the first-party client, so it behaves similarly enough that it's difficult for them to detect it. But it happened to a friend of mine that was using the WeeChat plugin while it was still being developed. There's plenty of other instances of similar situations with other services.

> Spotify is a big ask because google would have to port widevine (the web DRM.)

Spotify shouldn't be a problem [0][1] using librespot [2]. As for banking, I can't speak for all of Europe, but web apps are generally optimized for desktop use, apps have some convinient features, like scanning the QR code of a bill and pay it with one tap, instead of having to type in everything manually when it's on paper, or copy paste it from a PDF.

Additionally some banks require an app for 2FA for the web interface on PC too.

[0] https://github.com/kraxarn/spotify-qt