-
Notifications
You must be signed in to change notification settings - Fork 397
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
Is it possible to send a message without being replied to first? #92
Comments
I have this kind of behavior in AtlassianBot. You can take a look on JiraNotifierBot in https://github.com/gpailler/AtlassianBot/blob/master/plugins/jira.py#L149 |
The approach is to use an idle handler, which gets called whenever something else hasn't already happened, or once per second. This should help reduce rate limiting. Functional testing has been added. Updated README.md with how to use the new functionality. Resolves scrapinghub#92.
The approach is to use an idle handler, which gets called whenever something else hasn't already happened, or once per second. This should help reduce rate limiting. Functional testing has been added. Updated README.md with how to use the new functionality. Resolves scrapinghub#92.
Probably you are looking for |
That's for the bot to send a message to a channel. Unless I'm wrong I don't see how it is that related with this issue. |
I implemented it thusly:
|
I think @lincolnlorscheider answers this question, so this can be closed. |
The approach is to use an idle handler, which gets called whenever something else hasn't already happened, or once per second. This should help reduce rate limiting. Functional testing has been added. Updated README.md with how to use the new functionality. Resolves scrapinghub#92.
The approach is to use an idle handler, which gets called whenever something else hasn't already happened, or once per second. This should help reduce rate limiting. Functional testing has been added. Updated README.md with how to use the new functionality. Resolves scrapinghub#92.
The approach is to use an idle handler, which gets called whenever something else hasn't already happened, or once per second. This should help reduce rate limiting. Functional testing has been added. Updated README.md with how to use the new functionality. Resolves scrapinghub#92.
The approach is to use an idle handler, which gets called whenever something else hasn't already happened, or once per second. This should help reduce rate limiting. Functional testing has been added. Updated README.md with how to use the new functionality. Resolves scrapinghub#92.
The approach is to use an idle handler, which gets called whenever something else hasn't already happened, or once per second. This should help reduce rate limiting. Functional testing has been added. Updated README.md with how to use the new functionality. Resolves scrapinghub#92.
The approach is to use an idle handler, which gets called whenever something else hasn't already happened, or once per second. This should help reduce rate limiting. Functional testing has been added. Updated README.md with how to use the new functionality. Resolves scrapinghub#92.
Is there any way with the current API to send a message without responding?
If so, how would I do it, and can I request the documentation be updated? (I may update it myself and submit a PR if I figure out how.)
The text was updated successfully, but these errors were encountered: