spotifyd
A spotify daemon (by Spotifyd)
com.spotify.Client | spotifyd | |
---|---|---|
50 | 43 | |
64 | 9,546 | |
- | 0.9% | |
6.5 | 7.3 | |
15 days ago | 9 days ago | |
Python | Rust | |
- | GNU General Public License v3.0 only |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
com.spotify.Client
Posts with mentions or reviews of com.spotify.Client.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-12.
-
Being someone who doesn't fully understand AppArmor vs SELinux, how well do snaps work on Fedora?
There is nothing "unsafe" about flatpak. In fact for every package on flathub you can see exactly what the "unofficial" packagers do in the corresponding github repository. For example here is the repository for Spotify, if you look at the json manifest file you can see they are repackaging the "official" Snap with the necessary libraries and scripts to support it running as a flatpak. Everything there is open source and able to be examined.
- Food for thought
- Spotify with dark theme titlebar
-
Are flatpaks that are unverified safe?
If you click on the "Manifest" link for the package on flathub, it will take you to where the code that packages the app resides. There you can review exactly what the packager does in the json manifest. Here's the one for the Spotify client, for example, which shows where it pulls in dependencies and where it downloads the proprietary code from (in this case they base it on the snap) and what commands it executes while packaging the flatpak.
- lpf-spotify-client
-
How to get Spotify to launch?
Try installing it via Flatpak
-
Flathub's index now shows you which apps are verified
Flatpaks builds are made to be reproducible. Everything is done openly and you can check how the apps like for example Spotify where made.
- Install software using normal account instead of an administrator account
-
Problem with spotify install
Why not just use the flatpak?
-
Error about connecting to snapcraft.io showed up while updating spotify flatpak.
Judging by the manifest, the Spotify Flatpak is built from the Spotify Snap.
spotifyd
Posts with mentions or reviews of spotifyd.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-03-21.
-
Ask HN: How is the Spotify app so bad?
For those unaware, it's possible to use alternative clients for Spotify using a 3rd party daemon.
https://github.com/Spotifyd/spotifyd
-
Use Spotify made for Developers
[Unit] Description=A spotify playing daemon Documentation=https://github.com/Spotifyd/spotifyd Wants=sound.target After=sound.target Wants=network-online.target After=network-online.target [Service] ExecStart=/usr/bin/spotifyd --no-daemon Restart=always RestartSec=12 [Install] WantedBy=default.target
-
Update on the suggestion for Spotify to take ownership of the Flatpak
you don't need another frontend. preferred client to handle streaming for spotify-tui is spotifyd.
-
Spotify users, do you recommend spotify-easyrpm or the flatpak?
If you're using a premium account, you could also try to use the browser to control and spotifyd to play: https://github.com/Spotifyd/spotifyd
-
Trying to make e ink device with Linux. Kind of lost
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.
-
I used a Raspberry Pi and Arduino to fix/upgrade an old broken Jukebox
Spotifyd runs on Linux, can also be recognized by Spotify app as an output requires premium, not sure about touch screen compatability
- As a micro services expert, I know the fix for that: did you try sticking it into a systemd daemon that restarts it automatically when it crashes?
- Spotifyd
- spotifyd: open source Spotify client running as a UNIX daemon
What are some alternatives?
When comparing com.spotify.Client and spotifyd you can also consider the following projects:
spotify-qt - Lightweight Spotify client using Qt
raspotify - A Spotify Connect client that mostly Just Works™
snapcraft - Package, distribute, and update any app for Linux and IoT.
librespot - Open Source Spotify client library
com.discordapp.Discord
spot - Native Spotify client for the GNOME desktop
spotify-cli - Control Spotify playback on any device through the command line.
ice - Tool to create Chromium/Chrome/Firefox/Vivaldi SSBs in Peppermint OS.
ncspot - Cross-platform ncurses Spotify client written in Rust, inspired by ncmpc and the likes.
org.videolan.VLC
spotify-tui - Spotify for the terminal written in Rust 🚀
com.spotify.Client vs spotify-qt
spotifyd vs raspotify
com.spotify.Client vs snapcraft
spotifyd vs librespot
com.spotify.Client vs com.discordapp.Discord
spotifyd vs spotify-qt
com.spotify.Client vs spot
spotifyd vs spotify-cli
com.spotify.Client vs ice
spotifyd vs ncspot
com.spotify.Client vs org.videolan.VLC
spotifyd vs spotify-tui