Hello.
Today, after quite a while, I have used the API to get subs for the past two weeks of episodes. The results were VERY weird:
http://grab.by/6NaG
As you can see, it's returning all sorts of incorrect movies matched against the hash/bytesize.
I went to see the subtitle pages and they are, indeed, mismatched, for example:
http://www.opensubtitles.org/en/subtitl ... -dragon-en
http://www.opensubtitles.org/en/subtitl ... rd-kind-es
http://www.opensubtitles.org/en/subtitl ... -dragon-es
http://www.opensubtitles.org/en/subtitl ... e-neige-en
In all these cases it seems like the original subtitle mapping is correct (the movie is for the subtitle) but that someone has uploaded a match against a hash that is incorrect. This means this situation affects only the API users (rendering all API clients virtually useless) but doesn't affect the Web users.
Further, since a hash match is viral, once these incorrect matches are made other clients propagate them to their own subtitles and subtitle names, so we get dozens of subs and sub names mismatched against the incorrect movie.
Is there any way to check if these mismatches all belong to the same user(s)/client(s)? They may be a programming error from a player or a plugin somewhere that uploads all subs in a folder as matching a movie in that folder, even if they shouldn't match.
One way to filter all these would be to check against the IMDB-IDs of the subs and see if any given sub is assigned to two different IMDB IDs (it could be assigned to different movie names and different movie hashes, obviously, but never two different IMDB IDs), but clients can't do it as since there's no TV support there's no way to check the ID against the episode's ID.
Any ideas? It may be controllable server side, but I don't know the extents of the infection(*)
(*)"Infection" as in "it's an error that's propagating rapidly". Not because it's related to a virus, worm or anything like it.