[slondr]

Hi, I'm one of the spotifyd maintainers, happy to answer any questions people have - though I'm coming to this thread awfully late...

We recently cut a new release for the first time in over a year, which is very exciting for all of us (and I'm guessing why the project has been submitted here now :D)

[ponco]

Is there an existential threat looming? Could Spotify make an API change that would completely break libespot and Spotifyd? Any insights as to why/why not that might be likely?

Also, any plans to add the ability to save the tracks that are streamed? (for e.g. offline playback or for exporting to mp3 etc.)

[slondr]

I don’t think so; we’ve never had a regression related to the Spotify api that I’m aware of. I know librespot has big plans in the near future to switch to a newer version of the Spotify api so I think we’ll be good for now.

Definitely no plans for saving tracks.

[nsteel]

> Also, any plans to add the ability to save the tracks that are streamed?

I hope not. Sounds like a great way to provoke Spotify into a breaking API change.

[anonomousename]

Does the team plan to have an official Windows release? I’m using an older version and with a few changes, was able to create a fork for windows. It works fine for my purposes but was wondering if it was ever considered.

[slondr]

There was an open MR to add windows support for awhile but I think it fizzled out due to lack of OP interest.[1] None of the maintainer staff use Windows, but a working PR that doesn’t cause any regressions would likely be accepted.

[1] https://github.com/Spotifyd/spotifyd/pull/602

[spotifyboii]

any ideas to add reporting playback to spotify servers? it isn't fair if you ask me? you're forced to use premium but you are not even helping the artists