Page MenuHomePhabricator

Flow is vulnerable to mass vandalism lacking mass rollback function
Open, Needs TriagePublic

Description

In the following talk with Flow extension: https://he.wikipedia.org/wiki/%D7%A0%D7%95%D7%A9%D7%90:Thqsbpipewvklqkq

There is massive spaming from some IP. It is not possible to easily remove all the comments. Comparing to other wiki functions - it is usually possible to massive rollback from Contribs page or using Nuke.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

And PLEASE, start with, at least, oversighters.

Catrope renamed this task from Flow is vulenerable to mass vandalism lacking mass rollback function to Flow is vulnerable to mass vandalism lacking mass rollback function.Apr 5 2017, 6:22 PM
Catrope subscribed.

T115695: Add Flow support to Nuke implemented Nuke support, but it looks like that may only have addressed topic creation, not comment creation. We should have Nuke support all Flow actions/edits, not just topic creations.

The case happen over the week end on mediawiki.org. A spammer has created about 20 topics. I was not able to delete them en masse because some other users have preventively hidden the contents. No one has reply to those topics, the only actions were hide actions.

T115695: Add Flow support to Nuke works well for newly created topics, even if they are hidden. However, deal with a case like the following one is not possible and really missing:

Capture d’écran_2017-12-19_13-41-08.png (874×1 px, 105 KB)

A new request to have a feature to handle vandalism a better way.

The mandatory comment required for restoring hidden comments (for each one separately) is like a smack in the phase when cleaning up vandalism :(

kostajh edited projects, added patch-welcome; removed Collaboration-Team-Triage.
kostajh subscribed.

Volunteer contributions are very welcome for this. The Growth team won't have time to work on it in the short-to-medium term.