-
Notifications
You must be signed in to change notification settings - Fork 43
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
New required parameter for ANDROID client #3
Comments
{
"contentCheckOk": True,
"context": {
"client": {
"androidSdkVersion": 31,
"clientName": "ANDROID",
"clientVersion": "17.31.35",
"gl": "US",
"hl": "en-GB",
"osName": "Android",
"osVersion": "12",
"platform": "MOBILE"
},
"user": {
"lockedSafetyMode": False
}
},
"racyCheckOk": True,
"videoId": video_id
} You need to send |
I meant to say that YouTube servers is A/B testing this new requirement. You may not have any issue on your IP address, but some do, see the first comments on this issue: iv-org/invidious#3230 |
When I have time I will run the scripts again to update the version numbers as well. |
Youtube sometimes rolls out updates only for certain users or regions. This makes it difficult to reproduce such things. I believe that is the case here. |
You can easily reproduce this issue on UK IPv4 public addresses, that's why I asked the country here: iv-org/invidious#3230 (comment). I've successfully reproduced the issue on digitalocean droplets hosted in UK. Here is a script that try to reproduce the issue: https://gist.github.com/coletdjnz/cc0cbce42067b77c628d68c7b10a96c5/c495de26e470e20e7bf082f7d1e3716972106d8c It's not the latest revision of the script because the latest revision test the unavailability when the user-agent header is incorrect. In this case, take the latest revision. Anyway, you guys can believe or do anything you want, I'm just sharing the fact that this issue has been reported multiple times on popular projects:
And these popular projects have pushed multiple fixes for that, just an extract of them:
I'm not here to spread disinformation nor to be belittled by others in the community. |
You have to do multiple requests until the issue appears. Please use the script I sent in my previous message. |
For demonstration and testing purposes, the script is sufficient. I have no doubt that the |
It appears that you have not looked at the issue at all.
In the Python test script this video-id check is already present. pr_video_id = data['videoDetails']['videoId']
if video_id != pr_video_id:
# print(f"{t_name} Video id {video_id} does not match {pr_video_id}") |
youtube doesn't care with innertube. thats the single threaded version anyways, which takes forever to reproduce. |
I feel like this discussion leads to nowhere. What I propose in order to satisfy everyone, is to have a new column for each client with the recommended parameters to send to YouTube servers, like This way at least when someone will read the documentation, whenever they are doing extreme API load or not, they will be aware of these potential parameters that may or may not apply to their use case. The ideal case would be to show an example request with all the recommended parameters for each client (see here: https://github.com/TeamNewPipe/NewPipeExtractor/blob/943b7c033bb9d07ead63ddab4441c287653e4384/extractor/src/main/java/org/schabi/newpipe/extractor/services/youtube/YoutubeParsingHelper.java#L1174), but that may be out of scope of this repository. |
Suggestions for improvement are welcome. |
well, |
It was discovered that the ANDROID client will require a new parameter in order to return correct streams URLs, see: TeamNewPipe/NewPipe#8713
Should we add that parameter in the results of the README: https://github.com/zerodytrash/YouTube-Internal-Clients#results?
The text was updated successfully, but these errors were encountered: