It'd be useful if the Nuke extension could mass delete all topics/posts created by a spammer
See also T116211: Improve/investigate solutions for the Flow botspam.
It'd be useful if the Nuke extension could mass delete all topics/posts created by a spammer
See also T116211: Improve/investigate solutions for the Flow botspam.
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | SBisson | T115695 Add Flow support to Nuke | |||
Resolved | SBisson | T121828 Fix Flow Nuke support for dedicated Flow DB | |||
Resolved | SBisson | T121827 Use dedicated $wgFlowCluster and $wgFlowDefaultWikiDb in MediaWiki-Vagrant | |||
Resolved | • Mattflaschen-WMF | T86373 MediaWiki should not connect as root database user on MediaWiki-Vagrant |
Change 255981 had a related patch set uploaded (by Sbisson):
[WIP] Hooks to extend pages retrieval and deletion
Change 256448 had a related patch set uploaded (by Sbisson):
[WIP] Include Flow topics in Nuke
Change 259891 had a related patch set uploaded (by Mattflaschen):
Hooks to extend pages retrieval and deletion
Change 259892 had a related patch set uploaded (by Mattflaschen):
Include Flow topics in Nuke
Change 259924 had a related patch set uploaded (by Mattflaschen):
Fix a database connection that was not cluster-aware in Nuke hook
Change 259946 had a related patch set uploaded (by Catrope):
Fix a database connection that was not cluster-aware in Nuke hook
Change 259946 merged by Catrope:
Fix a database connection that was not cluster-aware in Nuke hook
Change 259924 merged by jenkins-bot:
Fix a database connection that was not cluster-aware in Nuke hook
Tested in betalabs
Notes:
These things were out of scope based on conversations I had with @Quiddity. It should have been documented in the ticket, my bad.
I propose we remove the blocking tasks dependencies, move this ticket to "product review" and let the other tickets be discussed and prioritized independently.