[GH-ISSUE #1000] Project Update #443

Open
opened 2026-02-28 14:49:11 +03:00 by kerem · 13 comments
Owner

Originally created by @Rigellute on GitHub (Jun 30, 2022).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/1000

I sincerely apologise for my lack of maintenance, I do love this project but I have not been able to dedicate any time to it - life/other commitments have been getting in the way! I hope to be able to make more space for development in the future.

A serious amount of work is needed to upgrade the underlying spotify library. What's more, the current architecture has grown in complexity and needs a rethink. I had spent time exploring this refactor, but ran out of steam trying to reimplement existing features.

Just know that I do intend to return to it!

Originally created by @Rigellute on GitHub (Jun 30, 2022). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/1000 I sincerely apologise for my lack of maintenance, I do love this project but I have not been able to dedicate any time to it - life/other commitments have been getting in the way! I hope to be able to make more space for development in the future. A serious amount of work is needed to upgrade the underlying spotify library. What's more, the current architecture has grown in complexity and needs a rethink. I had spent time exploring this refactor, but ran out of steam trying to reimplement existing features. Just know that I do intend to return to it!
Author
Owner

@Rigellute commented on GitHub (Jun 30, 2022):

It's rather fitting that this is issue #1000 😁

<!-- gh-comment-id:1171044841 --> @Rigellute commented on GitHub (Jun 30, 2022): It's rather fitting that this is issue #1000 😁
Author
Owner

@sewnie commented on GitHub (Jun 30, 2022):

LETS FUCKING GOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO

<!-- gh-comment-id:1171571989 --> @sewnie commented on GitHub (Jun 30, 2022): ### **LETS FUCKING GOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO**
Author
Owner

@elijahmg commented on GitHub (Oct 20, 2022):

@Rigellute Thx for your work. I faced some issues because of underlying library and since I needed only couple of feature, I've started to build my own pure cli tool. It's very mature.
Here it is https://github.com/elijahmg/spotify-rust-cli
Thank you for inspiration

<!-- gh-comment-id:1286149767 --> @elijahmg commented on GitHub (Oct 20, 2022): @Rigellute Thx for your work. I faced some issues because of underlying library and since I needed only couple of feature, I've started to build my own pure cli tool. It's very mature. Here it is https://github.com/elijahmg/spotify-rust-cli Thank you for inspiration
Author
Owner

@nopeless commented on GitHub (Oct 25, 2022):

@Rigellute I feel like there are just too many bugs for this project to be viable for every day use and way many edge cases that cause discomfort

I really do like the concept of this project but for now, I feel like someone has to rewrite the codebase with better underlying ui engine

<!-- gh-comment-id:1291222687 --> @nopeless commented on GitHub (Oct 25, 2022): @Rigellute I feel like there are just too many bugs for this project to be viable for every day use and way many edge cases that cause discomfort I really do like the concept of this project but for now, I feel like someone has to rewrite the codebase with better underlying ui engine
Author
Owner

@Oppen commented on GitHub (Nov 22, 2022):

Hi @Rigellute. Thanks for all the work you put on this project. I'd like to say I love it but I got too late to the party to try it :( I'm sure I would tho ❤️
I was thinking, is there anything we can do to help keep the project alive? I thought maybe we could create a GitHub org so some more people can review and merge PRs. I see a lot of people has enough interest to contribute fixes, so what's missing the most is a few people in charge of the follow up.
Of course, my suggestion only applies if you agree, and setting you as owner (you deserve it), just with some other people helping to keep it afloat.

<!-- gh-comment-id:1323710920 --> @Oppen commented on GitHub (Nov 22, 2022): Hi @Rigellute. Thanks for all the work you put on this project. I'd like to say I love it but I got too late to the party to try it :( I'm sure I would tho :heart: I was thinking, is there anything we can do to help keep the project alive? I thought maybe we could create a GitHub org so some more people can review and merge PRs. I see a lot of people has enough interest to contribute fixes, so what's missing the most is a few people in charge of the follow up. Of course, my suggestion only applies if you agree, and setting you as owner (you deserve it), just with some other people helping to keep it afloat.
Author
Owner

@aromeronavia commented on GitHub (Dec 20, 2022):

Yes, we are quite a few people interested in contributing to this <3

<!-- gh-comment-id:1358836840 --> @aromeronavia commented on GitHub (Dec 20, 2022): Yes, we are quite a few people interested in contributing to this <3
Author
Owner

@sewnie commented on GitHub (Dec 20, 2022):

Me waiting for @Rigellute to have someone takeover the project or have a organization 💀

Honestly, can someone here responsible enough make a fork of this project that takes PRs and accepts contributions, and fixes to this project? Many parts of it is broken (1000+ issues relating to broken)

<!-- gh-comment-id:1358854910 --> @sewnie commented on GitHub (Dec 20, 2022): Me waiting for @Rigellute to have someone takeover the project or have a organization 💀 Honestly, can someone here responsible enough make a fork of this project that takes PRs and accepts contributions, and fixes to this project? Many parts of it is broken (1000+ issues relating to broken)
Author
Owner

@sewnie commented on GitHub (Dec 21, 2022):

i have now created a fork of this repository that lives at https://github.com/spotify-tui/spotify-tui; with some PRs merged and a cargo.lock update, but i do not know Rust if at all so i have applied some that do work.

<!-- gh-comment-id:1361337662 --> @sewnie commented on GitHub (Dec 21, 2022): i have now created a fork of this repository that lives at https://github.com/spotify-tui/spotify-tui; with some PRs merged and a cargo.lock update, but i do not know Rust if at all so i have applied some that do work.
Author
Owner

@sewnie commented on GitHub (Jan 28, 2023):

edit: https://github.com/aome510/spotify-player

<!-- gh-comment-id:1407308022 --> @sewnie commented on GitHub (Jan 28, 2023): edit: https://github.com/aome510/spotify-player
Author
Owner

@hoomp3 commented on GitHub (Mar 13, 2023):

edit: https://github.com/aome510/spotify-player

this one is so good, definitely recommend everyone use this instead

<!-- gh-comment-id:1466529727 --> @hoomp3 commented on GitHub (Mar 13, 2023): > edit: https://github.com/aome510/spotify-player this one is so good, definitely recommend everyone use this instead
Author
Owner

@sewnie commented on GitHub (Mar 13, 2023):

EVERYONE should use this anyway, the developer is super nice and extremely active, plus tui looks much better and has way more features that can actually replace the propietary spotify client.

<!-- gh-comment-id:1466564830 --> @sewnie commented on GitHub (Mar 13, 2023): EVERYONE should use this anyway, the developer is super nice and extremely active, plus tui looks much better and has way more features that can actually replace the propietary spotify client.
Author
Owner

@Rigellute commented on GitHub (Apr 27, 2023):

Sorry again for my radio silence. I've been unable to spend any time on spotify-tui 😞. Consider the project in a deep sleep until I can return to make the needed, but considerable, updates/fixes

<!-- gh-comment-id:1524948352 --> @Rigellute commented on GitHub (Apr 27, 2023): Sorry again for my radio silence. I've been unable to spend any time on `spotify-tui` 😞. Consider the project in a deep sleep until I can return to make the needed, but considerable, updates/fixes
Author
Owner

@ErtanTaner commented on GitHub (Oct 25, 2024):

Thank you for all your work but if this project not going to be updated, can we make this as archive?

<!-- gh-comment-id:2437202716 --> @ErtanTaner commented on GitHub (Oct 25, 2024): Thank you for all your work but if this project not going to be updated, can we make this as archive?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-tui#443
No description provided.