https://bugzilla.wikimedia.org/show_bug.cgi?id=42064
--- Comment #15 from Chris Steipp <cste...@wikimedia.org> --- I began sketching out how I think this could be implemented over the weekend. It would be great if all of the logic could be done in the existing hooks, since that is how AF expects for the filter to be extended. To take Matt's example on wikitech-l, I'm pretty sure you could implement Bayesian filtering using the existing hooks. But, as pointed out, Wikidata doesn't operate on an EditPage, which the current hook handler uses to get information for the rules (title, previous revisions, etc), and also to re-show the edit page if the filter rejects the change. So AF does need a new hook handler for doing its work without the EditPage. How about AbuseFilter defines an interface for objects it can filter, and Wikibase can make any objects that need to be filtered implement that interface (either formally or informally), so AbuseFilter does the work, but the knowledge it needs about Wikibase can be generalized to other projects as well? -- You are receiving this mail because: You are on the CC list for the bug. You are watching all bug changes. _______________________________________________ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
