-
-
Notifications
You must be signed in to change notification settings - Fork 5
New API: whoer.net
#98
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
Conversation
|
@sepandhaghighi, do you have any ideas about these API call failures? When I run the request locally, it consistently returns a 403. However, the same URL loads fine in my browser. |
|
Additionally, I’ve noticed that autopep8 is not handling some cases correctly in my local environment and keeps reporting formatting errors that need manual fixes. I’ll open a separate PR to address this and apply the fixes across all our repositories so that autopep8 can run seamlessly again. |
|
I test the API, and it appears that whoer.net uses TLS fingerprint checking for bot detection. Although we can bypass this issue with some tricks, it's not good for our library legally. So, I suggest closing this PR and ignoring this API. Because this behavior indicates that we do not want to use our API in a script and we respect that. |
Reference Issues/PRs
#65
What does this implement/fix? Explain your changes.
Any other comments?