@wikibugs-l-list is still subscribed to many many tasks... We should remove these as post BZ cleanup
Description
Related Objects
Event Timeline
I still don't think that the (un)defined "problem" here justifies the notification spam... Anyway. :)
Yeah, we should discuss if we want to continue that... wikibugs left the channels ten times... I don't want to annoy people with flooding bots... :(. It may be useful to ask upstream for a possilbility to pause or abort bulk edits.... once submited this is a problem, you can't do anything....
The removal of wikibugs-l causes Herald to add projects, which are then dutifully reported by Wikibugs.
In a way, this was nice to happen for the herlad rules.
Herald doesn't act on a task until something/someone else does (it only works on transactions, it's not a db query). So a bunch of tasks met the criteria of some Herald rules but never were acted upon because they haven't seen activity since the rule was created.
Today we got that "free" activity :)
From one email notification I received:
Luke081515 removed a subscriber: wikibugs-l-list. Herald added a project: Discovery.
That's why wikibugs was so chattery.
If this is going to be done on mass It might be nice to kill wikibugs while it happens ;)
Please find a way to mass remove wikibugs-l that does not trigger notifications. I am subscribed to properly thousand of tasks and that is going to fill my inbox :-/ I even suspect my mail provider to throttle/delay an emitter pass some threshold.
Would it be conceivable to remove straight in the database?
Is it technically possible to add a global Herald rule that removes a subscriber from all tasks? That would only trigger notifications when there are other changes to a task.
I can create it. The disadvantage: If a task is not edited, the wikibugs user would not removed.
Could we just disable the user accounts so it doesn't email? thoughts @demon? or does that account get used for something else?
It doesn't.
Disabling wikibugs-l would keep it from getting notifications about it being removed, but since that list is already dead who cares? It wouldn't prevent mailspam to other users affected by mass task changes. I don't think the gain here justifies the spam so I'm declining mass removal of the subscriber. I did go ahead and disable the account anyway though so it's greyed out and people will maybe notice/care less :p
Triggering herald rules for old bugs is a nice idea, but not really what was being asked here, that should be investigated as its own task.
Just out of interest: Do we know how many tasks is @wikibugs-l-list currently subscribed to?