This may need #3 to be done so that messages count is already reduced
[08:06:16] <samueldr> uhm, so I can assume that nix and nixos not being reported by {^_^} is by design?
[08:06:46] <gchristensen> no
[08:06:58] <LnL> I think gchristensen disabled it because somebody was being too productive :)
[08:07:01] <gchristensen> yeah
[08:07:09] <samueldr> ah, so yeah, by design :)
[08:07:19] <gchristensen> well I disabled the whole thing
[08:07:27] <gchristensen> and forgot to turn it on
[08:07:32] <samueldr> good, I was wondering if I did something wrong
[08:07:54] <gchristensen> ah:)
[08:08:05] <samueldr> do you remember the productive someone, and how it caused issue, maybe it's possible to do something with heuristics?
[08:08:18] <gchristensen> joachifm merged 25 PRs
[08:09:13] <samueldr> maybe coalescing events per-user in a pre-determined timespan could help
[08:09:34] <samueldr> e.g. wait 1 or 2 minutes before sending events, and over X events, create a markdown gist listing them?
[08:09:50] <gchristensen> or maybe calculate the rate of messages you're wanting to send, and if over Nps don't send them?
[08:10:06] <samueldr> also
[08:10:14] <gchristensen> Npm* probably better
[08:10:48] <gchristensen> lol
[08:10:49] <samueldr> it could probably be both, chances are "spam" will be one productive individual, well, up to now it is
[08:10:51] <gchristensen> except to #nixos-bots... :P
[08:11:25] <samueldr> but in the event a sprint is occuring, it would be great to reduce spam and limit messages
[08:11:31] <gchristensen> agreed
[08:11:37] <gchristensen> however that is done would be great
This may need #3 to be done so that messages count is already reduced
https://logs.nix.samueldr.com/nixos-bots/2018-03-14#1521055382-1521056254;