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.

  • jay@mbin.zerojay.com
    3·
    4 months ago

    I cannot tell you about the public invidious instances but running my own privately does not proxy requests by default.

  • glorious_goldfish@lemmy.blahaj.zoneEnglish
    3·
    4 months ago

    I’m still quite new to this but it is my understanding that invidious does serve as a proxy IF you are using a public instance. This is, I believe, why many instances get hit by the “sign in to confirm you’re not a bot, this helps protect our community” error due to so much traffic from the instance IP.

    If you’re hosting your own instance YouTube will be able to see your IP. Since while it’s technically proxying your video requests, it’s still on your network.

    I’m new to invidious and networking stuff in general so if I’m wrong please correct me.

    • whoareu@lemmy.ca
      6·
      4 months ago

      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.

      • glorious_goldfish@lemmy.blahaj.zoneEnglish
        4·
        4 months ago

        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.