Love/ban tracks - Githubissues

mymikemiller / a-simple-lastfm-scrobbler

Automatically exported from code.google.com/p/a-simple-lastfm-scrobbler

GNU General Public License v3.0

0 stars 0 forks source link

Love/ban tracks #15

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

Would also be nice

Original issue reported on code.google.com by tgwizard on 3 Oct 2009 at 11:49

GoogleCodeExporter commented 9 years ago

After reading the Last.fm API documentation more closely, I'd have to implement 
the
entire webservice workflow for loving/banning to work, not just the submissions 
protocol.

I might still do it, but it'd require a lot more work.

Original comment by tgwizard on 6 Mar 2010 at 3:24

GoogleCodeExporter commented 9 years ago

With the new Scrobble API coming out, this will be easier.

The new API-proposal is presented here:
http://blog.last.fm/2010/03/19/but-does-it-scrobble

Original comment by tgwizard on 28 Mar 2010 at 11:32

GoogleCodeExporter commented 9 years ago

Original comment by tgwizard on 27 Apr 2010 at 7:41

Added labels: Type-Feature
Removed labels: Type-Enhancement

GoogleCodeExporter commented 9 years ago

It'd be good to publish "MarkCurrentTrackAsLoved()" to the API so third-party 
apps/widgets can use that (e.g. see issue 73)

Original comment by timurrrr on 30 Dec 2010 at 9:31

GoogleCodeExporter commented 9 years ago

I'd love to have this feature. If you have that, the music players could access 
that via the API or users can trigger this manually with a widget on the home 
screen perhaps.

Original comment by kachauno...@gmail.com on 17 Mar 2011 at 12:45