Add handing for N-parameter in URLs

[omansak]

More info :
https://code.videolan.org/videolan/vlc/-/issues/26174#note_286445
ytdl-org/youtube-dl#29326

[Tyrrrz]

Thanks!
Am I right to assume it closes #599?

[Tyrrrz]

Your first link also mentions that this can be avoided altogether by masking requests as Android. Can we just do that? It seems like a way simpler solution.

curl --request POST \
  --url 'https://www.youtube.com/youtubei/v1/player?key=AIzaSyAO_FJ2SlqU8Q4STEHLGCilw_Y9_11qcW8' \
  --header 'Content-Type: application/json' \
  --header 'Origin: https://www.youtube.com' \
  --header 'X-YouTube-Client-Name: 3' \
  --header 'X-YouTube-Client-Version: 16.20' \
  --data '{
	"context": {
		"client": {
			"clientName": "ANDROID",
			"clientVersion": "16.20",
			"hl": "en"
		}
	},
	"videoId": "dQw4w9WgXcQ",
}'

[omansak]

Thanks! Am I right to assume it closes #599?

also #573

[omansak]

Your first link also mentions that this can be avoided altogether by masking requests as Android. Can we just do that? It seems like a way simpler solution.

curl --request POST \
  --url 'https://www.youtube.com/youtubei/v1/player?key=AIzaSyAO_FJ2SlqU8Q4STEHLGCilw_Y9_11qcW8' \
  --header 'Content-Type: application/json' \
  --header 'Origin: https://www.youtube.com' \
  --header 'X-YouTube-Client-Name: 3' \
  --header 'X-YouTube-Client-Version: 16.20' \
  --data '{
	"context": {
		"client": {
			"clientName": "ANDROID",
			"clientVersion": "16.20",
			"hl": "en"
		}
	},
	"videoId": "dQw4w9WgXcQ",
}'

Probably, slow bitrate problem will be solved with ANDROID client name but I chose definitive solution for WEB clients.

[Tyrrrz]

Your first link also mentions that this can be avoided altogether by masking requests as Android. Can we just do that? It seems like a way simpler solution.

curl --request POST \
  --url 'https://www.youtube.com/youtubei/v1/player?key=AIzaSyAO_FJ2SlqU8Q4STEHLGCilw_Y9_11qcW8' \
  --header 'Content-Type: application/json' \
  --header 'Origin: https://www.youtube.com' \
  --header 'X-YouTube-Client-Name: 3' \
  --header 'X-YouTube-Client-Version: 16.20' \
  --data '{
	"context": {
		"client": {
			"clientName": "ANDROID",
			"clientVersion": "16.20",
			"hl": "en"
		}
	},
	"videoId": "dQw4w9WgXcQ",
}'

Probably, slow bitrate problem will be solved with ANDROID client name but I chose definitive solution for WEB clients.

Let's start with Android solution for now in a different PR and keep this one around for later, in case YouTube breaks that one too. Would you create a PR for that?

[omansak]

I looked again and we cant this. Because https://www.youtube.com/youtubei/v1/player the request gives all information for video. Just look this https://reqbin.com/c-7zqbnajr . We must to parse response and get the Video HTML5 URL which URLs does not need any process, URL's works perfectly. I didn't like this method for YoutubeExplode.

[Tyrrrz]

Can we do this without interpreting JS somehow?

[MihaZupan]

We must to parse response and get the Video HTML5 URL which URLs does not need any process, URL's works perfectly. I didn't like this method for YoutubeExplode.

@omansak can you elaborate on why the Android approach can't be used in this library?

[FrostySo]

@omansak can you elaborate on why the Android approach can't be used in this library?

"Probably, slow bitrate problem will be solved with ANDROID client name but I chose definitive solution for WEB clients."

Which I find absurd because the first solution is more likely to cause issues than the second. The solution for android will always exist because how else will Youtube operate for non js platforms?

[Tyrrrz]

For now went with the Android solution, let's see how long it lasts. All things considered, it's definitely simpler than the alternative.

[Tyrrrz]

Going to close for now since we went with the Android solution.