You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the user-agent tends to get banned, as you mentioned in the README troubleshooting section, wouldn't it be better to set a different user-agent every time (with an option) instead of hard-coding it ?
Maybe using Faker, I could try to do a PR in order to introduce this new option.
The text was updated successfully, but these errors were encountered:
AkechiShiro
changed the title
[Feature request] option to randomize user-agent using [Faker](https://faker.readthedocs.io/en/master/) or a random string
[Feature request] option to randomize user-agent using Faker or a random string
Oct 6, 2023
If the user-agent tends to get banned, as you mentioned in the README troubleshooting section, wouldn't it be better to set a different user-agent every time (with an option) instead of hard-coding it ?
Maybe using Faker, I could try to do a PR in order to introduce this new option.
Hi,
I'll add a user agent string, as I don't want to add too many libraries.
If you think you could help me doing it, I'll gladly appreciate it.
We can use pseudo random generation random in the standard lib, then or secrets which is better for more random security value generation.
Both do not need any new dependencies installed.
I don't think the user-agent should be generated using the secrets module, random should be enough, as it is not a sensible value as a secret and using random with a predefined seed, would allow to have deterministic user-agent in case debugging an issue/or leaving traceable logs is needed.
AkechiShiro
changed the title
[Feature request] option to randomize user-agent using Faker or a random string
[Feature request] option to randomize user-agent using random or a secrets standard lib modules
Oct 6, 2023
Hi @ajuelosemmanuel
If the
user-agent
tends to get banned, as you mentioned in the README troubleshooting section, wouldn't it be better to set a different user-agent every time (with an option) instead of hard-coding it ?Maybe using Faker, I could try to do a PR in order to introduce this new option.
The text was updated successfully, but these errors were encountered: