- Joined
- Dec 14, 2022
Okay thanks, that's good to know.Tried yt-dlp a few different videos always 403'ed. Maybe I'm retarded and missing something vital. None were age restricted.
Hopefully this isn't a region by region rollout. No problems with yt-dlp in North America so far.
@Null fyi
Update:
The various YouTube http 403 problems continue to persist in third-party apps that have not made codebase updates.
- SmartTube- was broken, now fixed for most users with version 22.38 or later
- The following is true for the v22.38 fix...
- Can't play vids above 1080p !
- Only the avc (h264) codec is available
- VP9 and AV1 codecs are mysteriously gone
- Why would purging visitor cookie(s) to fix a 403 error... deactivate two video codecs?
- NewPipe- still broken and no update has been pushed as of this writing
- True for version 0.27.0 on Android
- ReVanced
- continues to work properly
- Invidious
- continues to work properly
- Browser adblocking (Brave, uBlock, etc)
- continues to work properly
- yt-dlp
- continues to work properly
- There are some users with sporadic 403 issues that are possibly region or ip specific
- Some people think YouTube is doing a region specific rollout of yt-dlp blocking, but I am a little skeptical of that
- If you have 403 issues, upgrade to the latest version and make sure the vid is not age restricted.
- Try a different VPN endpoint because YouTube may be blocking your VPN exit IP
- If problems persist please post here and @ me
It's possible YouTube are using these visitor tracking cookie(s) to identify and freeze out third-party application users under the cover of deprecating poorly documented parts of the YouTube API. Or I suppose it could just be a big misunderstanding with the 'family' out in Mountain View.
The VISITOR_INFO1_LIVE cookie is one possible suspect, and officially it "may enable personalized recommendations on YouTube based on past views and searches". This cookie (or a similar cookie) might be involved in the 403 problem. Purging the app visitor cookies upon receipt of the 403 seemed to fix the problem.
That's all for now
