Thread:Talk:Flow Portal/Warning levels detection/reply

So, this is a perfect example of something that Flow will handle and make better. You're describing a "warning" workflow. In this scenario (and I'm throwing cheese around; pseudo-code), a user would initiate a "Vandal" workflow on the user. That workflow would then remain active until manually closed by a privileged user (or maybe expired via time, depending on the level).

Once that workflow was enabled, it wouldn't be able to be "deleted". Bots or other users wouldn't have to search histories or hidden text; they could just query the user's Board for specific workflows (tags) and they'd appear. Additional attempts to initiate the same workflow would bring the existing, working one to the front, and automatically escalate it.

We could even do things like require that the user acknowledge the warnings before they are permitted to continue editing (though that could lead to denial of service attacks).