-
Notifications
You must be signed in to change notification settings - Fork 103
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 the option to choose whether to add a random delay #40
Conversation
Also, one more thing, when you open up a PR fill the mandatory fields and all other fields that can be filled while others that are not necessary should be removed. This will allow us to better distinguish between spam PRs and legitimate PRs because most of the spam PRs never fill all the fields, I hope you got my point 😄 . |
I see :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok looks great!! 😄 , let's merge it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok looks great!! 😄 , let's merge it.
What does this PR do?
This pull request adds a new feature that allows users to choose whether or not to use websurfx in a production environment. With this update, you can set the
production_use
flag totrue
to introduce a random delay before sending requests to the search engine. Conversely, if you prefer to disable this functionality, you can simply change the option tofalse
, like so:Why is this change important?
This new feature provides users with greater flexibility and control over how they use the tool.