-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Starring can be abused #3
Comments
Realistically, either we decide not to care about this or we remove processing of star/unstar events from the webhook handler. It's probably not an important thing to keep… Tentatively, let's remove that handler in 0.2.0. |
Originally said in IRC, but I figured I'd add it here for posterity:
It could just be configurable (setting on/off, instead of being removed. Is that what you mean by "Configurable push notifications" in #19? (at least partly, since obviously there are other events to configure as well) |
#19 refers specifically to events of the I think there's a fine line between keeping something and making it configurable because it's generally useful, and keeping something just because it's already in the code. Rarely do I see GitHub bots posting to IRC when the repo they monitor has been starred or unstarred—it's just not a particularly important thing to know about in a project's IRC channel. If the plugin sets up webhooks, also, it just requests |
😡 wrong place, sorry! |
Pushing to 0.5 along with #53; several issues can all benefit from a rewrite of the webhook handling. |
Repeatedly starring/unstarring projects monitored by sopel-github will cause spam.
The text was updated successfully, but these errors were encountered: