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

Support Invidious endpoints #111

Open
unixfox opened this issue Nov 5, 2023 · 1 comment · May be fixed by #257
Open

Support Invidious endpoints #111

unixfox opened this issue Nov 5, 2023 · 1 comment · May be fixed by #257

Comments

@unixfox
Copy link
Contributor

unixfox commented Nov 5, 2023

Invidious and Piped are two projects that share the same common purpose: an alternative frontend to YouTube.

Invidious is making tool that benefit piped users: https://github.com/iv-org/smart-ipv6-rotator and piped created tools that benefit Invidious users too: https://github.com/TeamPiped/http3-ytproxy

I would like to continue on this journey for sharing common tools that can benefit both sides.

That's why I would like to ask if it could be possible to make piped-proxy compatible with Invidious endpoints? Would that require a lot of effort?

Here are the endpoints of Invidious:

  • /videoplayback - currently supported in piped-proxy
  • /vi/ - not supported
  • /sb/ - not supported
  • /ggpht/ - not supported

Thank you.

@FireMasterK
Copy link
Member

Hi, this is something that I'm open to.

I initially didn't want to include support for Invidious as that causes a few unnecessary memory copies, and otherwise unnecessary checks for Piped instances which will increase CPU usage.

I'm open to adding support for invidious via a feature flag. We could then publish a new docker image/tag if necessary.

It's likely not a lot of effort to do this, but I'm unfortunately at a lack of manpower currently. I'd be happy to accept a PR or similar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants