IPv6 address rotation

[codenyte]

Describe the feature

A documentation page on docs.piped.video explaining how to set up Piped with IPv6 address rotation to avoid YouTube IP address blacklisting

Why would this be useful to add?

YouTube tries to ban all IP addresses of all Piped instances so they can force users to use the official website/app. IP rotation would avoid IP blocking and make Piped much more reliable. That would significantly improve the user experience. Good and reliable privacy front-ends like Piped are needed, especially now that Google wants to force everyone to watch their crappy ads. When I recommend Piped to other people, I often get complaints because videos aren't loading and the experience is bad, as mentioned before, IP rotation would address this issue.

Concept(s)

• Invidious has a guide that explains how to set this up: https://docs.invidious.io/ipv6-rotator/
  Piped should add something similar to their documentation.

• Create a fork Invidious' IPv6 rotator and adapt it to work with Piped

• The Piped instances API should also indicate whether an instance has IPv6 rotation enabled or not

• Make IPv6 rotation a part of the install guide (if applicable for the instance)

Additional context

Btw, I love Piped. You guys are doing great work!

Acknowledgements

• I have searched the existing issues and this is NOT a duplicate or related to another open issue.
• I have written a short but informative title.
• I filled out all of the requested information in this form.

[FarisZR]

Also, a way to force piped to use IPv6 would be great.
As I noticed that Piped seems to always use IPv4, even when the container has IPv6 connectivity.

Edit: It seems forcing Piped to use a specific subnet of 2001:db8 fixes it for some reason.

[Deon-Trevor]

I tried this fix on my instance. it worked perfectly for about 36 hours until YouTube somehow figured out my IPv6 range and blocked it. Now no matter what IP address I use it's to no avail. I've been migrating my server every 12 hours to run from YT but this is not sustainable.

Update:
I changed my servers' DNS resolvers to cloudflared ontop of using the IPv6 rotator, Cloudflare Proxy and CDN. So far this is the longest I've gone without migrating the servers to new IP addresses (18 hours). It might be worth looking into

Update 2:
I created a DNS server running DNS Over HTTPS and had the Piped box use it exclusively. I've been running smoothly for days now. Adding all these layers might be the solution

Update 3:
Each time i share how i’ve managed to get around this it always, somehow, leads to the ban 😩😩

[codenyte]

How did you set this up initially? Did you use the Invidious smart-ipv6-rotator?

[Deon-Trevor]

How did you set this up initially? Did you use the Invidious smart-ipv6-rotator?

Yes, had used the Invidious smart-ipv6-rotator, Cloudflare Proxy and CDN ONLY.

[codenyte]

Ok thanks, this looks interesting. I'm gonna have to look into that.