After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 634596 - Add Grooveshark support
Add Grooveshark support
Status: RESOLVED OBSOLETE
Product: banshee
Classification: Other
Component: Internet Radio
1.9.0
Other Linux
: Normal enhancement
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-11-11 15:30 UTC by Dave
Modified: 2015-08-09 15:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dave 2010-11-11 15:30:08 UTC
The API for grooveshark can be obtained using tinysong. It uses the same database and appears to be affiliated. http://www.tinysong.com/api 

I have applied for the API for deezer. I will post when I have more information.
Comment 1 Michael Martin-Smucker 2010-11-11 20:06:18 UTC
Perhaps a duplicate of Bug 525869, unless someone is interested in taking on the project?
Comment 2 Guus 2011-06-15 13:42:03 UTC
they now have an official API http://www.grooveshark.com/api , I don't know but maybe someone could make an extension for it now. Would be awesome!
Comment 3 Samuel Gyger (IRC: thinkabout) 2012-03-14 22:29:49 UTC
I'm not yet sure how the handle it officialy. I wrote them a Mail to get more information, but they only allow Players for mobile platforms if you're a paid subscriber. I think it will be similar for Desktop Players. But no response yet. But definitely one would need to display advertisement in the content pane, and force it to stay visible.
Comment 4 Andrés G. Aragoneses (IRC: knocte) 2012-03-15 11:35:33 UTC
(In reply to comment #3)
> ... But definitely one would need to display advertisement in the content
> pane, and force it to stay visible.

In my opinion the requirement of having to display advertisement automatically makes open source players be out of the game.

Because, just think about it this way, imagine:
1) We agree to do an extension, with advertisement.
2) They test a preview-release with the extension, to see if it really includes the advertisement.
3) They accept it, so they accept the consumerKey for Banshee (they enable it). (I haven't checked, but normally when you use an API of a 3rd party you need to provide a consumerKey so they know where the requests come from.)
4) We release a version with the extension, apparently everyone is happy, but:
5) Some distro decides to remove the advertisement with a patch downstream (they can do this, remember, it is open source), or some guy forks banshee and removes the advertisement.

End result: API usage forging Banshee's consumer Key (because a fork of Banshee is not Banshee anymore). This seems legal according to Banshee's license but Grooveshark guys may not be happy about it (or more particularly, their Terms&Conditions may forbid this).

If anyone has a solution to this problem, I welcome them to write it here. Until then, doing a Grooveshark extension for Banshee IMO is wasted time and effort.
Comment 5 Andrés G. Aragoneses (IRC: knocte) 2012-03-15 11:37:41 UTC
Oh, forgot to say: if Grooveshark guys are not happy, they will disable the key so then Banshee's extension (and any forked extensions) would stop working.
Comment 6 Andrés G. Aragoneses (IRC: knocte) 2015-08-09 15:17:44 UTC
Grooveshark is no more.