UniversalMediaServer / UniversalMediaServer/api
TMDB
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12
- Forks
- 3
- Avg merge
- 16d 31m
- Merged PRs (30d)
- 6
Description
We can probably just remove OMDb. Unfortunately we found it before TMDB. If we had found TMDB first, we probably wouldn't have added OMDb.
And yes I agree it would be good to fix for entries without IMDb IDs.
If we get ride of OMDb, do we really need OpenSubtitles, as it is mainly used to find the imdb id ?
Maybe I'm wrong but, if we are using only TMDB, we can implement TMDB directly on java side.
On app, users can add a TMDB key on config (as it is easy/free to have key) or leave empty.
App show them an advice that having a key is quicker.
If key, the app use direct TMDB requests with their own API key.
If no key (default), the app ask the api server to request for them (like a relay with some security to prevent bad usage) ?
I think it's like other app do.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by mapping the existing OMDb and OpenSubtitles integrations and the Java-side metadata flow, then clarify whether the scope is removing those services, adding direct TMDB requests, or providing a relay; done requires an agreed implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, nodejs, typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100