starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-07-16 05:43:54 +03:00
Code Issues 822 Packages Projects Releases 17 Wiki Activity

[PR #3836] [MERGED] Remove rate limit from TMDb provider #9720

New Issue
Closed
opened 2026-02-07 06:07:18 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-07 06:07:18 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/jellyfin/jellyfin/pull/3836
Author: @cvium
Created: 8/7/2020
Status: ✅ Merged
Merged: 8/7/2020
Merged by: @Bond-009

Base: master ← Head: remove_tmdb_api_rate_limit

📝 Commits (1)

  • 268139c Remove rate limit from TMDb provider

📊 Changes

1 file changed (+0 additions, -15 deletions)

View changed files

📝 MediaBrowser.Providers/Plugins/Tmdb/Movies/TmdbMovieProvider.cs (+0 -15)

📄 Description

Changes

As of December 16, 2019, we have disabled the API rate limiting.

https://developers.themoviedb.org/3/getting-started/request-rate-limiting

We could keep it just to be nice, but I am assuming they will let us know if it becomes too much. They removed it for a reason, so why limit ourselves. It's unlikely we will do that many requests since we are still very limited by the speed of FFProbe.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/jellyfin/jellyfin/pull/3836 **Author:** [@cvium](https://github.com/cvium) **Created:** 8/7/2020 **Status:** ✅ Merged **Merged:** 8/7/2020 **Merged by:** [@Bond-009](https://github.com/Bond-009) **Base:** `master` ← **Head:** `remove_tmdb_api_rate_limit` --- ### 📝 Commits (1) - [`268139c`](https://github.com/jellyfin/jellyfin/commit/268139c435eab7c880d8d20069dadae043928013) Remove rate limit from TMDb provider ### 📊 Changes **1 file changed** (+0 additions, -15 deletions) <details> <summary>View changed files</summary> 📝 `MediaBrowser.Providers/Plugins/Tmdb/Movies/TmdbMovieProvider.cs` (+0 -15) </details> ### 📄 Description <!-- Ensure your title is short, descriptive, and in the imperative mood (Fix X, Change Y, instead of Fixed X, Changed Y). For a good inspiration of what to write in commit messages and PRs please review https://chris.beams.io/posts/git-commit/ and our documentation. --> **Changes** > As of December 16, 2019, we have disabled the API rate limiting. https://developers.themoviedb.org/3/getting-started/request-rate-limiting We could keep it just to be nice, but I am assuming they will let us know if it becomes too much. They removed it for a reason, so why limit ourselves. It's unlikely we will do that many requests since we are still very limited by the speed of FFProbe. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-07 06:07:18 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#9720
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?