Skip to content
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

Support specifying poToken for WEB client. #43

Merged
merged 8 commits into from
Aug 14, 2024
Merged

Support specifying poToken for WEB client. #43

merged 8 commits into from
Aug 14, 2024

Conversation

devoxin
Copy link
Member

@devoxin devoxin commented Aug 14, 2024

This PR implements support for setting a poToken and accompanying visitorData values which currently apply to the WEB client. As of a recent change to YT's API, the WEB client may trigger 403 errors which can not be bypassed without specifying a poToken (proof-of-origin token).

On a longer timeline, I would like to make this an automatic process that is handled automatically by the source manager however due to the complexity of that, and with current time constraints, this should suffice.

From what I gather, this has been successfully used in production environments by a handful of users.
Token lifetime is currently unknown but seems to be quite a while. With that, the only real drawback to this feature is potentially having to periodically update tokens manually.

@devoxin devoxin merged commit 354d7fe into main Aug 14, 2024
2 checks passed
@devoxin devoxin deleted the feat/po-token branch August 14, 2024 13:09
@devoxin devoxin added the enhancement New feature or request label Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant