Hacker News Reader

Comment by explaininjs | Hacker News Reader

Congrats! Now you get to experience the glory of the deque. Your days of being restricted to stack pushing are in the past.

View on HN

That (deque) is actually one of my favorite features, and something that had tempted me in the past. I have to relearn some behavior on queue creation though. I'm use to just clicking play, rather than adding to queue, so I end up with a bunch of songs in queue that I didn't intend (because I played a song from a longer playlist to start).

There’s definitely some annoyances… the paramount one for me is actually the opposite of what you describe: I click on an item to simply play it and it makes me deal with a pop up asking me how it should interact with my queue, even when I have no queue at all! Just play the damned song, stop asking me questions.

Ugh… things like this make me wish we had just one FOSS music player with a paid backend. I’d comment out all the modals and get on with life.

Nothing is stopping you from donating to Navidrome development

As I understand it that is for listening to a library of personally owned material remotely? That's not really what I'm looking for. I appreciate the MAAS model, it's just the UI's that suck.

Lots and lots of FOSS music players use libspotify or can otherwise connect to your Spotify account.

Here's just one. It's BYO frontend. Last I knew, there were a bunch of them. https://mopidy.com/

Also look into mpd, the music playing daemon.

That's a good attempt, but I'd rather not run a server - if I'm paying for the service I'd like to have an API I can run/write a frontend against. And ideally I'd have the ability to listen to lossless music, not whatever encoding Spotify thinks I deserve.

Reply on news.ycombinator.com