spotify-player
A Spotify player in the terminal with full feature parity (by aome510)
| spotify-player | com.spotify.Client | |
|---|---|---|
| 17 | 50 | |
| 1,202 | 64 | |
| - | - | |
| 8.8 | 6.5 | |
| 6 days ago | 17 days ago | |
| Rust | Python | |
| MIT License | - |
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.
spotify-player
Posts with mentions or reviews of spotify-player.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-07-05.
-
Spotify_player on Steamdeck with distrobox
The Spotify on the Discover Store doesn't allow you to run in the terminal and using the terminal will give it a nice performance boost without the GUI overhead, which is what is being achieved using spotify-payer. From checking the project, it looks pretty good for something minimal: https://github.com/aome510/spotify-player
- Show HN: spotify-player – A command driven Spotify player
-
who is telling the "truth"??
btw, check out the epic CLI spotify_player of aome510 its on github, its really ram efficient ~45mb of ram ( orig. spotify uses sometimes up to 400-800mb...) craaaazy
-
Spot - a simple spotify CLI made in python
The one I use, spotify-player, https://github.com/aome510/spotify-player
-
Working on a Spotify TUI/CLI in GO using bubbletea
I'll look into it. But, I don't want to control spotify-player, itself can be used as one, https://github.com/aome510/spotify-player
-
Replacing the root partition
That's probably a good suggestion. I've done this a few years ago but not with X11, just minor applications to test the concept. I'll look into this, Netflix is the only thing remaining. For Spotify, I've just built spotify-player (https://github.com/aome510/spotify-player) with the alsabackend and it's working fine.
-
Question about Spotify package
spotify-player, https://github.com/aome510/spotify-player - not available but, the one I use
- Show HN: Spotify-player – A command driven Spotify player
- Github - aome510/spotify-player: A command driven spotify player
- spotify-player – a Spotify music player on the terminal
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.
What are some alternatives?
When comparing spotify-player and com.spotify.Client you can also consider the following projects:
spotify-tui - Spotify for the terminal written in Rust 🚀
spotify-qt - Lightweight Spotify client using Qt
hackernews-TUI - A Terminal UI to browse Hacker News
snapcraft - Package, distribute, and update any app for Linux and IoT.
ncspot - Cross-platform ncurses Spotify client written in Rust, inspired by ncmpc and the likes.
com.discordapp.Discord
dzr - Accountless deezer.com Player (CLI & VSCode)
spot - Native Spotify client for the GNOME desktop
spotifyd - A spotify daemon
void-packages - The Void source packages collection
ice - Tool to create Chromium/Chrome/Firefox/Vivaldi SSBs in Peppermint OS.
spotify-player vs spotify-tui
com.spotify.Client vs spotify-qt
spotify-player vs hackernews-TUI
com.spotify.Client vs snapcraft
spotify-player vs ncspot
com.spotify.Client vs com.discordapp.Discord
spotify-player vs dzr
com.spotify.Client vs spot
spotify-player vs spotify-qt
com.spotify.Client vs spotifyd
spotify-player vs void-packages
com.spotify.Client vs ice