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

Add ability to supply own PO tokens #46

Merged
merged 1 commit into from
Oct 7, 2024

Conversation

nick42d
Copy link
Contributor

@nick42d nick42d commented Oct 7, 2024

This partially resolves #43.
Added new request_option to supply PO token. I have tested this with a PO token from my browser and confirmed that this resolves #44 when a correct token is supplied.

In a future PR I'd like to add the ability to supply own visitor data as well, but that will require a little more refactoring. @clytras it seems the PO token by itself is sufficient - if possible could you please explain why we might need visitor data as well?

@Mithronn Mithronn merged commit af7e85e into Mithronn:main Oct 7, 2024
1 of 4 checks passed
@clytras
Copy link

clytras commented Oct 8, 2024

@nick42d thank you for adding the PO token support. I am not sure why would we need Visitor Data, maybe it could increase some kind of "trust" score that the request comes from a real browser but that is just a guess, I believe just PO token is enough for now.

nick42d added a commit to nick42d/rusty_ytdl that referenced this pull request Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error 403 forbidden on stream.chunk() Apply PO token and Visitor data
3 participants