Heads-up for the #PeerTube community, it appears Google has been blocking many tools/IP ranges that try to synchronize with YouTube. At least for the creators on #tilvids this is a massive challenge, because they can no longer sync THEIR content on multiple platforms, requiring them to manually upload to both TILvids AND #youtube We appreciate our creators going the extra mile, and please remember this is why it's so important to support alternative platforms.
https://github.com/Chocobozzz/PeerTube/issues/6522
#tech
Invidious and YouTube piped (and LibreTube) by default load the videos server-side, as opposed to GrayJay, NewPipe or Smarttube.
It has advantages (mostly that your IP address is not shared with YouTube, and it allows users from countries where YouTube is blocked to still access it) and inconvenients (much harder to keep up when YouTube actively seeks to block them).
Fair enough, that’s interesting. I assume this only applies to the non-web clients. On the web, it would not be possible.
You can verify by looking at the outgoing network requests on this random video for example: https://invidious.privacyredirect.com/watch?v=qKMcKQCQxxI
Because of the CORS settings on Google’s servers would tell your browser to not go forward with the request.
There are two ways it could eventually be possible:
By opening the video in a new page/tab that only contains the video, with the YouTube player, which defeats the purpose a bit.
deleted by creator
Invidious and YouTube piped (and LibreTube) by default load the videos server-side, as opposed to GrayJay, NewPipe or Smarttube.
It has advantages (mostly that your IP address is not shared with YouTube, and it allows users from countries where YouTube is blocked to still access it) and inconvenients (much harder to keep up when YouTube actively seeks to block them).
Invidious shares your IP with google, it does not act as a proxy
I guess this reply lost its “by default” part on the way 🤔
I’m pretty confident that you are wrong.
https://docs.invidious.io/faq/#q-what-data-is-shared-with-youtube
Fair enough, that’s interesting. I assume this only applies to the non-web clients. On the web, it would not be possible. You can verify by looking at the outgoing network requests on this random video for example: https://invidious.privacyredirect.com/watch?v=qKMcKQCQxxI
Why not?
Because of the CORS settings on Google’s servers would tell your browser to not go forward with the request. There are two ways it could eventually be possible:
I haven’t checked the CORS headers for YouTube videos but wouldn’t access have to be fairly open to allow embedded videos to work?