I began using invidious after every piped instances refused to play videos lately. But what I read from their docs is that my IP might get exposed to google servers while loading videos from invidious. I use rethink DNS app and in that I can see all the domains that are getting called by my browser.
I tested about five instances and none are calling googlevideo domain as mentioned in the doc. Are they proxying my requests by default or am I missing something?
No, I don’t have the option proxy video turned on. I use yewtu.be as my main invidious instance.
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn’t great, if contents of the website are behind a paywall maybe copy them into the post
- Don’t promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
- 0 users online
- 57 users / day
- 383 users / week
- 1.5K users / month
- 5.7K users / 6 months
- 1 subscriber
- 2.97K Posts
- 74.6K Comments
- Modlog
by default it doesn’t proxy the video stream you are getting from YouTube. it just extract the link to that stream and sent it to your browser and then you browser plays that stream URL which points to google’s server so google is able to see your IP address.
however there is an option called “DASH” if you enable this option the stream would be proxied by your invidious instances. this options is disabled on most of the public instances because of high bandwidth usage.
Ah I see! Thanks for the explainer, I see where I misunderstood it.
I thought invidious got the entire video stream and streamed it back to the viewer - not just the link to it. So even if YouTube sees the invidious instance ip as the one grabbing the link, it would still see your ip as the one actually watching the stream.
I guess the bot related error I mentioned comes from when the server tries to get the stream link.