starred/spotify-tui

Fork 0

mirror of https://github.com/Rigellute/spotify-tui.git synced 2026-04-27 00:25:53 +03:00

[GH-ISSUE #1080] spt forces web, cannot select spotifyd #496

New issue

Open

opened 2026-02-28 14:49:31 +03:00 by kerem · 8 comments

kerem commented

2026-02-28 14:49:31 +03:00

Owner

Originally created by @AlexCzar on GitHub (Apr 11, 2023).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/1080

; spotifyd --version
spotifyd 0.3.4
; spt --version     
spotify-tui 0.25.0

I have spotifyd set up and working.
when I run spt, as per https://github.com/Rigellute/spotify-tui#using-with-spotifyd I cannot select spotifyd, because spt asks for Client ID and won't allow me to do anything else.

Originally created by @AlexCzar on GitHub (Apr 11, 2023). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/1080 ```text ; spotifyd --version spotifyd 0.3.4 ; spt --version spotify-tui 0.25.0 ``` I have spotifyd set up and working. when I run spt, as per https://github.com/Rigellute/spotify-tui#using-with-spotifyd I cannot select spotifyd, because spt asks for Client ID and won't allow me to do anything else.

kerem commented

2026-02-28 14:49:31 +03:00

Author

Owner

@sewnie commented on GitHub (Apr 11, 2023):

solution: https://github.com/aome510/spotify-player, no need for spotifyd, this is an actual client.

@sewnie commented on GitHub (Apr 11, 2023): solution: https://github.com/aome510/spotify-player, no need for spotifyd, this is an actual client.

kerem commented

2026-02-28 14:49:32 +03:00

Author

Owner

@AlexCzar commented on GitHub (Apr 11, 2023):

Good to know, but it is not a solution, in this instance I'd like to have a local UI for spotifyd, not another client, mostly I'm using spotifyd remotely, but occasionally would like to control it from the same machine.

@AlexCzar commented on GitHub (Apr 11, 2023): Good to know, but it is not a solution, in this instance I'd like to have a local UI for spotifyd, not another client, mostly I'm using spotifyd remotely, but occasionally would like to control it from the same machine.

kerem commented

2026-02-28 14:49:32 +03:00

Author

Owner

@sewnie commented on GitHub (Apr 11, 2023):

Then setup spotifyd and use spotify_player to control it.

@sewnie commented on GitHub (Apr 11, 2023): Then setup spotifyd and use spotify_player to control it.

kerem commented

2026-02-28 14:49:32 +03:00

Author

Owner

@AlexCzar commented on GitHub (Apr 11, 2023):

Again, good to know, thanks, I may go that route, but would prefer to fix the issue which is in the OP.

@AlexCzar commented on GitHub (Apr 11, 2023): Again, good to know, thanks, I may go that route, but would prefer to fix the issue which is in the OP.

kerem commented

2026-02-28 14:49:32 +03:00

Author

Owner

@sewnie commented on GitHub (Apr 11, 2023):

Please do know that spt has been abandoned. Which is why I was reccomending another client.

Additionally, your spotify remote configuration might be invalid, try setting it up again. And if that doesn't help, then that means spt is now outdated in terms I'd spotify api.

@sewnie commented on GitHub (Apr 11, 2023): Please do know that spt has been abandoned. Which is why I was reccomending another client. Additionally, your spotify remote configuration might be invalid, try setting it up again. And if that doesn't help, then that means spt is now outdated in terms I'd spotify api.

kerem commented

2026-02-28 14:49:32 +03:00

Author

Owner

@AlexCzar commented on GitHub (Apr 11, 2023):

Thanks, but it looks like it's stalled, not abandoned, so I'll keep the issue open for future reference.
Here is a tweet from the author on that account.

@AlexCzar commented on GitHub (Apr 11, 2023): Thanks, but it looks like it's stalled, not abandoned, so I'll keep the issue open for future reference. Here is a [tweet from the author](https://twitter.com/AlexKeliris/status/1596262599397494784) on that account.

kerem commented

2026-02-28 14:49:32 +03:00

Author

Owner

@sewnie commented on GitHub (Apr 11, 2023):

but it looks like it's stalled, not abandoned

I know. They've been saying that they are getting it back but, it has already been half a year, and a new, and MUCH MUCH better project is here.

It deserves some fucking praise. This does not.

@sewnie commented on GitHub (Apr 11, 2023): > but it looks like it's stalled, not abandoned I know. They've been saying that they are getting it back but, it has already been half a year, and a new, and MUCH MUCH better project is here. It deserves some fucking praise. This does not.

kerem commented

2026-02-28 14:49:32 +03:00

Author

Owner

@ed9w2in6 commented on GitHub (Nov 27, 2023):

@apprehensions While recommending an actively maintained alternative is a good thing, your comment here is down right rude. I strongly recommend you to consider rewording them, especially the foul language.

As I have commented in another issue, I disagree with your classification as abandonware, especially when the program still works and that the author is reachable, as you may already know, as mentioned in issue https://github.com/Rigellute/spotify-tui/issues/1000. There can be any reasons that the author cannot catch up on writing fixes, work or study, especially when it still works. As long as the author has not publicly announced archival or end of life, it is NOT abandoned.

As a fellow programmer, you should also read this gist and this HackerNews thread, and the linked article on open source maintainer's obligations - there are (almost) none. I too was once like you, which is why I believe you can change.

I believe you can do better than this especially if you maintain any software yourself. If you have strong feelings with this software then you can consider redirecting those feelings into writing up fixes - which will benefit the whole community.

@ed9w2in6 commented on GitHub (Nov 27, 2023): @apprehensions While recommending an actively maintained alternative is a good thing, your comment here is down right rude. I strongly recommend you to consider rewording them, especially the foul language. As I have commented in another issue, I disagree with your classification as abandonware, especially when the program still works and that the author is reachable, as you may already know, as mentioned in issue https://github.com/Rigellute/spotify-tui/issues/1000. There can be any reasons that the author cannot catch up on writing fixes, work or study, especially when it still works. As long as the author has not publicly announced archival or end of life, it is NOT abandoned. As a fellow programmer, you should also read [this gist](https://gist.github.com/richhickey/1563cddea1002958f96e7ba9519972d9) and this [HackerNews thread, and the linked article](https://news.ycombinator.com/item?id=16631476) on open source maintainer's obligations - there are (almost) none. I too was once like you, which is why I believe you can change. I believe you can do better than this especially if you maintain any software yourself. If you have strong feelings with this software then you can consider redirecting those feelings into writing up fixes - which will benefit the whole community.