mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #82] Allow connections from different accounts? #72
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#72
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sashahilton00 on GitHub (Jan 29, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/82
Monday Aug 28, 2017 at 00:43 GMT
Originally opened as https://github.com/plietar/librespot/issues/240
Hi,
I'd like to create a small Spotify Connect daemon running on our HTPC, which allows any Spotify application in the network to control it (maybe secured by an account whitelist..?).
However, I just noticed that, when using a different account, the Spotify Web Player simply ignores librespot and the desktop client tells me that I have to buy premium, although I use librespot already with a premium account...
E.g. by simulating a standard web / desktop player?
@sashahilton00 commented on GitHub (Jan 29, 2018):
Monday Aug 28, 2017 at 02:13 GMT
Did you try using discovery mode? I believe that should allow different (albeit premium) accounts to control librespot (but I may be wrong - I have not tested this).
My understanding is that librespot is intentionally limited to premium accounts so as to not provoke the ire of Spotify. As such, I think librespot presents itself as a spirc device that requires a premium account (correct me if I'm wrong).
@sashahilton00 commented on GitHub (Jan 29, 2018):
Monday Aug 28, 2017 at 13:31 GMT
Yes, I understand the point with premium.
However, I already need a premium account to connect to Spotify.
My target would be to allow playing playlists from different accounts, especially because of the "discover weekly" lists of different music flavours for different accounts.
Of course I can let each guest export the playlist and play it directly from the premium account, but it would be cool if I could avoid that.
Not all people have bought Spotify premium and requiring premium for that small convenience is unreasonable.
Is there a way to change that "spirc" identity? Or does "spirc" directly refer to a certain protocol?
Using discovery mode causes Spotify to directly stream to librespot from the guest account I think..?
@sashahilton00 commented on GitHub (Jan 29, 2018):
@Hoeze in response to your questions:
Is there a way to allow different Spotify accounts to control the daemon?
Not easily. The protocol is designed such that the current play queue is tied to a specific account, and librespot is authenticated to a single account. There is no easy way to allow other accounts to see/update the queue. This could be done via a local API that feeds the commands to librespot though.
Is there a way to allow non-premium accounts to control the daemon?
See response above. There's no easy way to allow multiple accounts to create/view/update a shared play queue, hence everything would have to be done through some sort of API you'd implement to librespot. Thus Free or Premium doesn't come into it.