I understand that Infuse currently uses TMDB as its metadata provider, and it may not be feasible to offer both TVDB and TMDB as metadata sources due to the significant differences between their datasets and potential inconsistencies in their API implementations.
That said, would it be possible to allow users to specify a custom TMDB API endpoint?
This would enable advanced users to set up their own TMDB API proxy. For the majority of metadata requests, this proxy could simply forward the requests to the official TMDB API. However, for specific cases where the official TMDB metadata does not meet the user’s needs, the proxy could intercept and return customized metadata responses—so long as they follow the same structure and format as TMDB’s API.
This approach would require only a single configuration option in Infuse: a custom API hostname. With that in place, users could have complete control over the metadata without requiring Infuse to support multiple metadata providers or formats directly.
Would this be something the team might consider?