745
OpenSubtitles.org is shutting down it's previous API. Now only authenticated access allowed. (blog.opensubtitles.com)
submitted 2 years ago by [M] to c/piracy@lemmy.dbzer0.com
183 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[+] -34 points 2 years ago* (last edited 2 years ago) (7 children)

It doesn’t say any of that information about non-VIP accounts, go read it yourself, and the information you quoted about anonymous accounts is also wrong.

edit: I won’t be receiving any replies from this commenter. If anyone wants to say I’m wrong, feel free to provide a screenshot from the blogpost proving it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 28 points 2 years ago (4 children)

    Since you deleted the comment I replied to:

    There's six big ass bold numbered paragraphs detailing the differences between the 'VIP' (paid) users and 'non-VIP' (free) users.

    There's also a link to the REST API docs where the first thing it details is exactly how authentication is handled. Specifically: an application looking to interface with opensubtitles will have an api key embedded by its developer and without logging in further will have 5 free downloads/day, that can then be expanded by the end user logging in with their (free or VIP) account.

    That documentation lists anonymous accounts (not signed in as a specific user) as rated limited to 5/day. That doubles to 10 for signed in (but still free) users and grows further with VIP.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] [S] 2 points 2 years ago (3 children)

    You realize the developer key is still authentication, hmmm?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 5 points 2 years ago

    Not really, no. Those keys are more or less equivalent to a browser's user agent, difference is you don't choose your own but get them from OpenSubtitles. Motivation probably ranges from "that makes it easy to reject random crawlers" to "we'd like to know the people writing software against our API, or at least have a way to contact them".

    You'll also be able to find examples of such keys in repositories in the future in case you don't want to request one of your own but frankly speaking that's a dick move.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 2 years ago (1 child)

    To an extent, but it's only really relevant to developers. End users don't see or interact with this at all and aren't required to provide further info.

    For 99% of people, this change makes very little, if any, difference. The way it's been worded makes it seem like no one gets to use opensubtitles anymore unless they start shelling out cash.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 2 years ago* (1 child)

    The OP doesn't, but the REST API Docs say:

    Your consumer can query the API on its own, and download 5 subtitles per IP's per 24 hours, but a user must be authenticated to download more. Users will then be able to download as many subtitles as their ranks allows, from 10 as simple signed up user, to 1000 for VIP user.

    https://opensubtitles.stoplight.io/docs/opensubtitles-api/e3750fd63a100-getting-started

    Though that's not fully 'unauthenticated', as the above is discussing the use of a developer API key. Though that would be built into whatever app is being used.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 0 points 2 years ago* (last edited 2 years ago)

    Except the screencap I provided shows different information, and as you say it’s not in the OP, so there’s still no reason for that guy being a jackass about others being confused about the situation.

  • permalink
  • fedilink
  • source
  • parent