Implement content and session PO tokens

[absidue]

Implement content and session PO tokens

Pull Request Type

• Bugfix

Related issue

Will link it after other devs have confirmed that it solves the issue for them too.

Description

YouTube has switched from just using session based PO tokens that are added to the streaming URLs, which is what we are currently doing, to also introducing content PO tokens which are tied to the video ID added to the /player request. This pull request implements that new PO token. Challenges are now fetched from the https://www.youtube.com/api/jnn which is a proxy for jnn-pa.googleapis.com instead of fetching it directly from the latter URL, which should hopefully help with people's misconfiguring their ad-blocker to block jnn-pa.googleapis.com.

This will definitely have code conflicts with the potoken proxy pull request, I will resolve the code conflicts in whichever pull request is merged later.

Testing

Open various videos and check that you don't get any 403s or Error: Error invoking remote method 'generate-po-token' errors.

Desktop

• OS: Windows
• OS Version: 10
• FreeTube version: e4092aa

[PikachuEXE]

Putting into custom build to test for 1 week+

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[github-actions]

Conflicts have been resolved. A maintainer will review the pull request shortly.

[kommunarr]

I don't experience this bug in my regular usage but will start testing this build.

[absidue]

@ArthurKun21 That build is based on the older commits that were using a hardcoded timeout which is no longer present in the latest commits. If you want to help test PRs, please make sure you are actually using the latest changes next time before commenting that something doesn't work for you.

[PikachuEXE]

Tested > 1 week

[efb4f5ff-1298-471a-8973-3d47447115dc]

Got a 403 on the first video i tried to watch. Didnt happen on my nightly build so i think its related to the PR but weirdly enough all videos after that did play fine though

[efb4f5ff-1298-471a-8973-3d47447115dc]

2nd 403 in a short period of testing and i cant replicate this behavior at all on the nightly build which im almost using daily

[PikachuEXE]

I got several 403 but not frequently and I did not use normal build for a while so no idea if YT doing stuff or this PR causing it