FireMasterK
commented
12 months ago 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.
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:
Thank you.