Saying Goodbye to OpenSubtitles.org API

Original Article ↗ Hacker News Discussion ↗

OpenSubtitles is shutting down its long‑running .org API and shifting to a new, rate‑limited REST API on OpenSubtitles.com, with higher limits reserved for paying “VIP” users. Commenters argue over whether this undermines the “open” promise of the service or is a reasonable way to cover infrastructure costs, especially since bulk access to the actual subtitle files is limited and the site already runs ads. The change also prompts broader debate about the legal status of fan-made subtitles, comparisons to other once‑free platforms that later monetized, and whether tools like Whisper or P2P systems could reduce dependence on centralized subtitle services.

Scope of the Change

  • Old OpenSubtitles.org API is being shut down after ~17 years; new REST API on OpenSubtitles.com is the replacement.
  • Core website remains accessible; main change is API access and pricing.
  • New limits: unauthenticated users get a small daily quota (e.g., ~5 downloads/IP); authenticated non‑paying users get more; VIP users get up to ~1000/day.
  • Thread summary notes: “nothing changes except API prices,” though others argue user experience and openness are meaningfully affected.
  • More ads (including already-present injected ads) are expected.

Impact on Users and Clients

  • Casual, manual users are mostly unaffected; downloading a few subtitles per day remains free.
  • Heavy/API users (media centers, scrapers, pirate streaming sites) are hit hardest by limits and required accounts or payments.
  • People mention broken integrations (e.g., VLC plugins) and uncertainty about how tools like Plex/Bazarr will adapt.

Debate Over “Open”

  • Many criticize the use of “Open” in the name while restricting free API access, comparing to OpenAI, OpenOffice, “open source” LLMs, IMDB, CDDB, Reddit, and other “enshittification” stories.
  • Others argue “open” should refer to licensing/redistribution rights, not free unlimited hosting or bandwidth.
  • Several say it’s reasonable to charge for the service layer while keeping data shareable.

Data Dumps and Openness

  • A “full dump” is linked, but it currently contains only metadata and URLs, not subtitle text.
  • Some initially claim this preserves openness; others note rate limits make crawling all ~6M subtitles via those URLs effectively impossible now.
  • Whether the subtitles themselves are openly licensed or rehostable is unclear from the site.

Sustainability vs. Betrayal

  • One camp views this as a necessary step to cover hosting and prevent abuse, not malice.
  • Another camp sees a familiar pattern: attract community contributions under an “open” banner, then monetize and restrict once network effects are achieved.

Legal and Ethical Issues

  • Long subthread on whether fan-made subtitles are derivative works or fair-use transcriptions.
  • Concerns that charging for access may make copyright enforcement more likely; others argue subs can increase legitimate sales or serve accessibility needs.
  • No consensus; legal status is described as tricky and jurisdiction-dependent.

Alternatives and Future

  • Several point to OpenAI Whisper/whisper.cpp and tools like Bazarr/MacWhisper as emerging ways to auto-generate subtitles, though:
    • Transcriptions ≠ high-quality subtitles (timing, editing, readability rules).
    • Non‑English quality and lack of speaker diarization are noted limits.
  • Suggestions to rebuild an “open” subtitle service using BitTorrent/IPFS; skepticism appears about who will do the work and handle legal risk.
  • Other subtitle sites (e.g., Addic7ed) and bundled subtitles in MKV releases are mentioned as existing alternatives.