Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed import error #15

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fixed import error #15

wants to merge 1 commit into from

Conversation

en0
Copy link

@en0 en0 commented Oct 15, 2020

No description provided.

@jodal
Copy link

jodal commented Oct 15, 2020

There should no longer be any need for this extension, as Mopidy-Spotify has had support for browsing through the Spotify Web API for a while now.

It might be worth adding a note to the readme stating this and archiving this repository.

@evertdhont
Copy link

Hi all, I have come across this exact problem that is fixed in this merge request.

@jodal what do you mean by "Mopidy-Spotify has had support for browsing through the Spotify Web API for a while now"? Can we access a web client on the mopidy server when the Mopidy-Spotify extention is installed and enabled?

If such documentation exists, it should indeed be handy to archive this repo and link the new documentation so that new people don't have to get confused and frustrated while trying to get this old client to work...

@jodal
Copy link

jodal commented Jan 13, 2021

This extension isn't a web client. It is a backend that provides access to browse some additional Spotify directories that previously was not supported by Mopidy-Spotify itself. Since support for those directories where added to Mopidy-Spotify more than a year ago, this extension has been redundant.

The -web suffix in this extension's name comes from the fact that the extension makes use of Spotify's "Web API" to do so.

I can see that this is confusing, thus I'd very much like for the author of this extension to put a short explanation in the top of the project readme and archive the repo.

@evertdhont
Copy link

Thanks for the explanation, @jodal! That clarified a lot. Maybe by tagging @lfcabend, this person sees our request to change the readme...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants