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
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
