-
Notifications
You must be signed in to change notification settings - Fork 425
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
Change UA to privacy.resistFingerprinting. #551
Conversation
FireMasterK
commented
Feb 19, 2021
- I carefully read the contribution guidelines and agree to them.
- Na - these are tests - I have tested the API against NewPipe.
- Na - these are tests - I agree to create a pull request for NewPipe as soon as possible to make it compatible with the changed API.
Please also update the user agent in YouTubeCommentsExtractor. |
18272ce
to
a6fa63d
Compare
Done. |
The comments extractor test seems to fail with the message I'm not sure what is to be done to fix this. |
@FireMasterK That means that the mocks responses can't be found. Which i guess, i should add to the error message. As for why it's not finding it. ill have to take a look |
@FireMasterK You'll have to regenerate the mocks for that specific tests, because the request contains the user agent. And every field of the request is used as key to identify which mock response should be given for a given request |
@XiangRongLin how would I do that? I'm not sure I understand how these mock tests are generated.. |
@FireMasterK Try starting from the doc of That doc is very "thrown" together |
Should be fixed now :D |
b665ad1
to
42bdd8a
Compare
Something that would need to be checked is whether the tests now fail against the real websites with the new user agent. since currently they are only running against the mock. I ran |
For me,
I've seen this exception in Piped too, which uses the same User-Agent, it doesn't happen all the time, see this paste for a similar trace.
|
|
for meta info / live stream, it also fails using the old user agent |
@FireMasterK could you explain why updating the user agent improves privacy and resists fingerprinting? |
Because we use a really outdated user agent. Thus this user agent is not that common anymore and allows to track users via IP and UA. |
Can you reproduce could not get trending name after #582? |
Nothing for the past few hours, so I think it has been resolved. |
Is it also possible to update the UA in the YouTubeCommentsExtractor? |
I have already done that, you requested that before in an earlier comment 🙃 |
Ups. I did not see that my local branch was not in sync with the upstream 😆 |