Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Enhancement] Include author thumbnails and number of subscribers in /subscriptions API #5160

Closed
blacklight opened this issue Jan 27, 2025 · 1 comment
Labels
enhancement Improvement of an existing feature

Comments

@blacklight
Copy link

Is your enhancement request related to a problem? Please describe.

I'm working on pulling Invidious subscriptions and playlists into my UI, and I'd like to render more information about the channels in the list.

Namely, currently the results only include entries in the following format:

{"author": "xkcd's What If?", "authorId": "UC6IxnFzHofFJ5X2PycSMsww"}

Describe the solution you'd like

A consistent response format on all the endpoints that return channels (probably this also means including authorThumbnails on video results).

I wouldn't go as far as including the full list of videos (there are dedicated endpoints for those already), but at least the metadata that is provided on /api/v1/channels/:id should be the same one also provided on /api/v1/auth/[notifications|subscriptions].

This is similar to what the Piped API already does. The fact that this metadata isn't provided on the Invidious API instead means that my UI won't show channel images or list of subscribers in the feed tab, nor in playlist views.

Describe alternatives you've considered

The obvious workaround would be to run a bunch of workers to fetch /api/v1/channels/:id whenever the user accesses the feed/playlist view in my UI, and maybe add some caching on top. But it would be obviously slow, harder to maintain, and the caching logic can easily be error-prone without the backend informing me whether a channel's metadata has changed.

Additional context

N/A

@blacklight blacklight added the enhancement Improvement of an existing feature label Jan 27, 2025
@absidue
Copy link
Contributor

absidue commented Jan 29, 2025

Invidious provides different information on different endpoints, because YouTube does. To be able to provide the extra information Invidious would have to make a lot more API requests, the requests that you said you don't want to do, which will just result in Invidious instances having even more problems with YouTube blocking them than they already do.

@unixfox unixfox closed this as not planned Won't fix, can't repro, duplicate, stale Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement of an existing feature
Projects
None yet
Development

No branches or pull requests

3 participants