an HTTP sink + remote command?

[philippe44]

Hi - I need for one application to make output data available through an HTTP server where a player can GET the audio. I assume I can do that with pipe and/or subprocess but I was thinking of adding a built-in sink which would also listen on a port where clients could GET the audio.

Optionally, that listening socket could be used to POST commands, like play/pause/stop/volume/next/previous. Could be a simple JSON payload or use an existing format like dmcp or something, I don't know. Maybe it already exists but I've missed it.

Would that be of any interest for the maintainers or shall I just keep that for myself?

[roderickvd]

Thanks for pinging back. Before entertaining this idea further, I believe it violates Spotify T&C’s 9.1 so it’s probably best not to support this.

[michaelherger]

In the Squeezebox environment players can stream from an http source. Such a sink would allow us to pipe the audio data directly to the player. It's definitely a technical intent, not malicious. But I do understand that the librespot project tries to protect itself from too easy abuse, which is absolutely ok.

[philippe44]

So you don't think that allowing only one connection and only a single playback is fitting in the T&C? Because it's definitively not broadcast. As soon as you consume some of it, the source goes away, you can't have multiple clients and you can't play it twice.

[roderickvd]

It's not up to me (I'm no maintainer). And while I understand your point, I'd advise that it's more about not drawing unwanted attention than being right or wrong. Onlookers may not dig that deep before passing judgement.

Also, there is more to trip over in the T&C's than just broadcasting, like transferring.

I am sorry if this curbs your enthusiasm, I don't intend to on your endeavors. I have no reason to doubt your honest intentions. Just advising caution to safeguard this project.

[philippe44]

understood

[philippe44]

So it's working now, in a purposely read-and-consume mode. At least it was a good Rust coding exercise