\multirow{7}{*}{Properties}& based on REGEXes & rule/ML based & rule/ML based & ML framework \\
& part of the "software" (MediaWiki plugin) & run on user's infrastructure ("bespoke code") & extra infrastructure & not used directly, can be incorporated in other tools \\
& extension is open source & no requirement for code to be public & heuristics obfuscated by the interface & open source \\
& public filters directly visible for anyone interested &&&\\
& trigger \emph{before} an edit is published & trigger after an edit is published & trigger after an edit is published &\\
& zero latency, trigger immediately & latency varies & generally higher latency than bots &\\
& collaborative effort & mostly single dev/operator (recently: bot frameworks) & few devs & few devs \\
\hline
\multirow{2}{*}{People involved}& edit filter managers (EN Wiki) & no special rights needed (except for admin bots) &\emph{rollback} permission needed & mostly Scoring Platform team \\
&& bot gets a ``bot flag'' &&\\
\hline
\multirow{2}{*}{Hurdles to participate}& gain community trust to become an edit filter manager & get approval from the BAG & get a \emph{rollback} permission&\\
& understand REGEXes & programming knowledge, understand APIs, ... & get familiar with the tool & understand ML \\
\hline
\multirow{2}{*}{Concerns}& censorship infrastructure & ``botophobia'' & gamification & general ML concerns: hard to understand \\
& powerful, can in theory block editors based on (hidden) filters &&&\\
\hline
Areas of application &&&&\\
\hline
\end{longtable}
\end{comment}
\end{landscape}
Following table summarises the aspects of Wikipedia's various algorithmic quality control mechanisms:
