You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to deploy a youtube frontend and possibly make it open to the public. Does viewtube support connecting to youtube exclusive by ipv6 with a ipv6 rotator solution like invidious? If it doesn't, this makes it a no go for me. With google cracking down on privacy harder ever, running a public youtube frontend will only get many ipv4 addresses banned.
This function should now be considered essential for all frontend developers.
The text was updated successfully, but these errors were encountered:
I think using an ipv6 proxy or similar should be possible. ViewTube uses undici internally for requests.
Putting the system behind a proxy would work or using the environment variable VIEWTUBE_PROXY_URL, you can specify a proxy for it to use: https://viewtube.wiki/configuration/advanced#proxy.
I haven't tested any of this with ipv6 tho, so please let me know if it doesn't work.
I'll have look into doing a forward proxy later. A quick peek a squid docs shows it supports ipv6 but didn't immediately see a documented way to ensure it only operated in ipv6.
If someone knows how to setup a simple forwarding proxy that only use ipv6, it would be helpful to point to an online guide.
I want to deploy a youtube frontend and possibly make it open to the public. Does viewtube support connecting to youtube exclusive by ipv6 with a ipv6 rotator solution like invidious? If it doesn't, this makes it a no go for me. With google cracking down on privacy harder ever, running a public youtube frontend will only get many ipv4 addresses banned.
This function should now be considered essential for all frontend developers.
The text was updated successfully, but these errors were encountered: