-
Notifications
You must be signed in to change notification settings - Fork 30
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
Comments
Hi Max, today is the scheduled sunset day. We shall be going forward with On Mon, Jan 5, 2015 at 11:23 AM, 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 :) |
Hey Max ... there is an effort by some 3rd party developers to keep it all On Mon, Jan 5, 2015 at 2:52 PM, Max Woolf [email protected] wrote:
|
Whoops ... See; P On Mon, Jan 5, 2015 at 3:03 PM, Paul Lamere [email protected] wrote:
|
Looks interesting, maybe instead of removing it from this gem, i'll point it to that since it appears to be compatible :) |
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 |
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?
The text was updated successfully, but these errors were encountered: