mherger wrote: > > I not only have many playlists over 200, but also have more than 200 > > playlists so I am limited there as well. This limit is what is > keeping > > me using triode spotify until the last possible minute. > > It's getting closely quickly... :-/ > > How many playlists would you have? And how many would be over 500 tracks > > long? > > > I have an api key. Would it be possible to add something so I can > enter > > and use my own key, removing the rate limit issue for your key? > > You can't remove the rate limit. It's something Spotify imposes on their > > end: you can send as many requests as you want. But at some point > they'll return with an error 429. > > But to have your own key would certainly help. Check the settings page: > > there's an input field at the bottom which is exactly for this use > case. > > > I had > > written functionality that automates the lookup and creation of > Spotify > > playlists from LastFM libraries, and I typically process nearly 4000 > > transactions per minute without rate limiting. > > With Spotify's web API? That's not my experience. A few weeks back I > managed to be sent back with a 429 after only 1-200 queries (quickly > fired, though). I think it depends on the request, too: the more > "expensive" a call (eg. a list of albums with artist and track > information vs. a single track lookup), the quicker you're being > blocked. Might be the reason why they don't give hard numbers. > > > If using other keys is possible, could you potentially remove the 200 > > limits? With my own key, this would eliminate any rate limiting risk > > with your common api key. > > It's actually a good idea to have an option to lift the limitations. If > > there is a custom client-id, then grab more data... I'll see what I can > do. > > I've already increased the number for "personal" items, like albums and > > artists. But I hadn't implemented the same for playlists. Will do for > the next release. > > -- > > Michael
Hi Michael. Thanks for your reply. Yes, I understand, you cannot remove the rate limit. What I meant was, the rate limit is applied per client key, so Spotify would see many less transactions from your api key if some were coming from mine. Yes, I use Spotify WebAPI. And you are correct, it depends on how expensive the transaction is. My typical transaction is a track search which is not expensive. I have tweaked my calls to be on the edge of rate limiting, so I get nearly 4000 track searches per minute. I do this by simply delaying between each call (currently 15 ms, configurable). Not a very technical solution, hard-coding a delay between each call, but this was actually the most reliable. Rapid fire consecutive calls without a delay seems to return the 429 consistently. I currently have between 300 and 400 playlists. The playlist length varies, some small, some a few hundred, some 2,000 to 5,000, and 4 up to the Spotify playlist length maximum of 10,000 tracks. I am happy to help with testing if needed. 'LastFM' (http://www.last.fm/user/waynefullerton/) ------------------------------------------------------------------------ wpf7's Profile: http://forums.slimdevices.com/member.php?userid=33170 View this thread: http://forums.slimdevices.com/showthread.php?t=107615 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
