On 12/05/2012 06:34 AM, Daniel Kinzler wrote:
I think that
makes sense. The spam filters will work best if they are
aware of how wikidata works, and have access to the full JSON
information of the change.
You really want the spam filter extensions to have internal knowledge of
Wikibase? That seems like a nasty cross-dependency, and goes directly against
the idea of modularization and separation of concerns...
I agree it should not have internal implementation knowledge. I meant
how it works in a different sense.
More specifically, what if Wikidata exposed a JSON object representing
an external version of each change (essentially a data API).
It could allow hooks to register for this (I think is similar to the