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

Remove identification capability #41

Open
maxehmookau opened this issue Jan 5, 2015 · 6 comments
Open

Remove identification capability #41

maxehmookau opened this issue Jan 5, 2015 · 6 comments

Comments

@maxehmookau
Copy link
Owner

Looks like echonest are removing their identify API. Guess we better remove it from this wrapper at some point.

@plamere any chance of reversing this decision or giving some detail as to why it's being removed?

@plamere
Copy link

plamere commented Jan 5, 2015

Hi Max, today is the scheduled sunset day. We shall be going forward with
the song/identify shutdown. We've made the source open source so anyone can
stand up a look up server if they are so inclined. It is a service that is
used by only a few folks, and it is rather expensive in terms of
engineering resources to keep running. -- P

On Mon, Jan 5, 2015 at 11:23 AM, Max Woolf [email protected] wrote:

Looks like echonest are removing their identify API. Guess we better
remove it from this wrapper at some point.

@plamere https://github.com/plamere any chance of reversing this
decision or giving some detail as to why it's being removed?


Reply to this email directly or view it on GitHub
#41.

@maxehmookau
Copy link
Owner Author

That's a shame, it was a fun project that I made use of in my final year dissertation at university. I would've thought with Spotify's acquisition of echo nest that there should be plenty of engineering resources. That said, thanks for your quick explanation :)
Max

@plamere
Copy link

plamere commented Jan 5, 2015

Hey Max ... there is an effort by some 3rd party developers to keep it all
going. See:

On Mon, Jan 5, 2015 at 2:52 PM, Max Woolf [email protected] wrote:

That's a shame, it was a fun project that I made use of in my final year
dissertation at university. I would've thought with Spotify's acquisition
of echo nest that there should be plenty of engineering resources. That
said, thanks for your quick explanation :)
Max


Reply to this email directly or view it on GitHub
#41 (comment)
.

@plamere
Copy link

plamere commented Jan 5, 2015

Whoops ...

See;

http://mooma.sh/api.html

P

On Mon, Jan 5, 2015 at 3:03 PM, Paul Lamere [email protected] wrote:

Hey Max ... there is an effort by some 3rd party developers to keep it all
going. See:

On Mon, Jan 5, 2015 at 2:52 PM, Max Woolf [email protected]
wrote:

That's a shame, it was a fun project that I made use of in my final year
dissertation at university. I would've thought with Spotify's acquisition
of echo nest that there should be plenty of engineering resources. That
said, thanks for your quick explanation :)
Max


Reply to this email directly or view it on GitHub
#41 (comment)
.

@maxehmookau
Copy link
Owner Author

Looks interesting, maybe instead of removing it from this gem, i'll point it to that since it appears to be compatible :)

@cmcollin41
Copy link

Hey guys! Awesome gem. It has saved me a lot of headache. Quick question, is there anyway to search artists by location thru this gem? I've tried doing
@artist = Echonest::Artist.search('KEY', artist_location: 'australia') but it tells me there is no search method for artist? Thanks for the help!

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

No branches or pull requests

3 participants