Closed GoogleCodeExporter closed 9 years ago
More things are not working anymore.
Original comment by nettunin...@gmail.com
on 6 Mar 2012 at 10:48
First of all, AutoSub is broken, because the API key is blocked.
Second, AutoSub reads your namemapping from the config file and reads them in
the memory. When it read them into the memory it changes it to lowercase.
Because if you try to match a showname with a showid you need the same case.
Csi =/= csi in python
So we convert everything to lowercase.
Like I said. AutoSub is not working anymore because the API-key is blocked.
Hold on tight till we have a permanent fix for everything (bierdopje.com
requires me to make a lot of changes to the code). Read the forum on
bierdopje.com for more information.
Original comment by romke.va...@gmail.com
on 6 Mar 2012 at 10:53
Okay thanx for the info. Tho i think bierdopje is nagging. They have much much
more "traffic" on web visitors then api calls... They could easy can get a
sponsored webserver for like api.bierdopje.com for api only calls :) Its not
you Romke just bierdopje is nagging :) Anyway i wait for a new version. I just
installed it 2 weeks ago and i liked it :) just one process left to do. spotweb
auto-downloading tv series :) You should make a virtual application with all
three tools combined spotweb+nzbserver+autosub :)
Anyway have a nice day.
Original comment by nettunin...@gmail.com
on 6 Mar 2012 at 11:03
@bierdopjenagging
Yes and No
No, one user was doing 1.5MIL API hits in one week. Like 1.3MIL of those hits
were downloading the same subtitle files. Lets say a subtitle is 50KB 1.3MIL *
50KB. lets say that is rougly 65GB of data. How this was caused is unknown.
Bierdopje.com will not contact the user or provider me with contact
information. The API hammering, may be cause by a user using my API-key in his
own application. Or (what I suspect) running an old version containing some old
bugs. I agree with bierdopje that I should fix this, prevent such things from
happening.
Yes, bierdopje is nagging. Lets say, I don't like another application (lets
call it X). X downloads subtitle and is a competitor to me. I don't like them,
because they 'steal' users away. Now, because bierdopje doesn't require
user-api keys. I can just sniffer their key out of the network stream. Now I
can create a script which calls 6.5mil the same request to the server.
Bierdopje.com now blocks their key. I think they should block users and only
block dev keys if they really are doing something wrong.
The fix in my eyes is very simple. Either user api-keys or limit the API calls
for each api key. Why the last option? It force developers to make their
program as efficient as possible, you should also provide the option to extent
the limit of course if the application gets more users. Be happy that a dev
choices your website, not the other way around. Also I requested a new feature,
I want to be able to get a WIPStaus from the API.
If this will not be enough and my API key is blocked again (or they don't
accept my request for a new key). Either two things will happen:
- I will create my own proxy, every user who want to use my application have to connect to my server. My server caches a lot for the request. New request will be redirected to bierdopje. This way the use will never have our API-key. But! This will cost money, so I will ask every to make account on my proxy server and pay a small fee (like buying an application on the AppStore (0,99 cents or something)).
- Or I stop working on a bierdopje application and move to another site.
I hope neither will ever happen, but you never know.
Enough of nagging from my side, back to work :)
Original comment by romke.va...@gmail.com
on 6 Mar 2012 at 12:14
Original issue reported on code.google.com by
nettunin...@gmail.com
on 6 Mar 2012 at 10:41