-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use workaround for fetching streaming URLs #4037
Conversation
YouTube appears to be A/B testing some new integrity checks. Adding the parameter "CgIQBg" to InnerTube player requests appears to workaround the problem See TeamNewPipe/NewPipeExtractor#1084
@@ -55,8 +55,9 @@ def extract_video_info(video_id : String, proxy_region : String? = nil) | |||
client_config = YoutubeAPI::ClientConfig.new(proxy_region: proxy_region) | |||
|
|||
# Fetch data from the player endpoint | |||
# 8AEB param is used to fetch YouTube stories |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can safely remove the 8AEB
param since stories was entirely removed by YouTube back in late June
Is there a difference with and without the padding bytes (%3D in base64)? |
Nevermind, NP uses the non-padded version, let's use that too. |
For the record, I did integrate that change into the test instance the other day (before the weekend) and it sure does work. I was planning to make a PR, but thanks for doing it instead ^^ |
PR iv-org#4037 introduced a workaround around YouTube's new integrity checks on streaming URLs. However, the usage of this workaround prevents storyboard data from being returned by InnerTube. This commit fixes that by only using the workaround when calling try_fetch_streaming_data
PR iv-org#4037 introduced a workaround around YouTube's new integrity checks on streaming URLs. However, the usage of this workaround prevents storyboard data from being returned by InnerTube. This commit fixes that by only using the workaround when calling try_fetch_streaming_data
Closes #4027
YouTube appears to be A/B testing some new integrity checks. Adding the parameter "CgIQBg" to InnerTube player requests appears to workaround the problem
See TeamNewPipe/NewPipeExtractor#1084