[jim_p]

Maybe it was "some sort of issue which was resolved" this time, making my rant unjustified. What you may not know is that it has shown a similar behavior at least once in the past (2+ years ago) with a 503 error and at that time the "regular" addon was working as it should. This led to patches and forks from volunteers, but the issue was not on the addon itself but on the opensubtitles api, as the dev (or whoever has the username "opensubtitles" on github) admitted.

This time however, there was no error and there has been no statement of any sort for the issue, at least until today. What would you think as a user, if you say that I am just ranting with no reason? After all, what fueled the comments and my rant here was not the issue itself but my statement on denying to make credentials.
The only good thing that all those comments brought is the proof that other apps and scripts do use the api without credentials, thus making any statement like "you need a username and a password because of X reasons" completely invalid.