Closed GoogleCodeExporter closed 9 years ago
No error is generated too, might be a nice "feature" to see when the key is
disabled (or any other errors).
Original comment by ppeckha...@gmail.com
on 22 Sep 2011 at 8:49
Same problem here with the SVN version. a curl on the url periscope tries to
save gives :
curl http://api.bierdopje.com/112C8204D6754A2A/GetAllSubsFor/13018/1/1/nl
<?xml version="1.0"?>
<bierdopje>
<response>
<error_code>3</error_code>
<error_msg>This developer key has been disabled</error_msg>
</response>
</bierdopje>
Original comment by Gerrit...@gmail.com
on 26 Sep 2011 at 12:02
I'll try to add a error message. But in the end, I think the only viable
solution would be that every person heavily using periscope as a tool for
downloading subtitles from Bierdopje should request their own API-key.
I can't control how often people are querying their servers and if we all share
the same API-key, one bad apple will prevent all the other users from
downloading subtitles.
Original comment by patrick....@gmail.com
on 26 Sep 2011 at 12:05
Bierdopje.com doesn't allow an API for every single user to use with someone
else his/her app (periscope). This renders Bierdopje.com pretty much useless
for Periscope users.
Original comment by buur...@gmail.com
on 26 Sep 2011 at 12:09
Issue 123 has been merged into this issue.
Original comment by patrick....@gmail.com
on 13 Jan 2012 at 11:04
Has a new API key been issued by Bierdopje yet ? Downloading files manually for
an entire season is becoming quite a hassle.
Original comment by ralf.van...@gmail.com
on 11 Dec 2012 at 4:26
No. Update to the latest version of the code and then you should request a key
on their forum for your private use. You'll then be able to add it to the
periscope config.
This way, you won't have it blocked (unless you're abusing yourself), but with
thousands of users and an open source python module that has a very modular
usage and a private key that is actually public (as the key can be viewed by
anyone browsing the code), it's impossible to not have it blocked :(
Original comment by patrick....@gmail.com
on 11 Dec 2012 at 4:29
Original comment by patrick....@gmail.com
on 24 Feb 2013 at 12:12
Original issue reported on code.google.com by
buur...@gmail.com
on 17 Sep 2011 at 5:45