Max Semenik wrote:
On 25.11.2012, 22:22 Platonides wrote:
+1 I think MediaWiki should keep this simple
feature, without having to
write abuse filters or needing to install specific extensions.
+1 to me too. Infinite modularity is bad, and the feature is pretty
simple, probably less than 1 kilobyte of code without comments.
It'd be interesting if we could get some usage stats of this feature. I
don't imagine it's used very much outside of a few big wikis (and even then,
wikis such as Wikimedia Commons don't use it all currently). It's a pretty
obscure feature.
> Is it
possible to write AbuseFilter so that it is able to make use of both
> bad and good lists stored within the MW namespace? I especially like that
> if we are able to utilise that in the global space. We have had global
> vandals come along and start spamming or vandalising by the addition of an
> image, or a singular image with coding. To be able to slow down that
> process with a global filter, would be excellent.
AbuseFilter is completely unrelated to this: AF blocks _edits_ while
bad images list blocks _content_.
AbuseFilter works on more than just edits.
And the behavior here is wrong: allowing submission of an edit that contains
a disallowed image without any warning or notice is wrong behavior. As I
recall, the behavior used to be that it would still include an inline link
to the image if the image were listed on the bad image list. Nowadays, it
seems to just ignore the image altogether (not outputting a link or
anything). No information to the user about why the image they specified
isn't displaying. Not even a link to the image. The image just gets silently
swallowed after the edit successfully saves. This is bizarre and wrong.
MZMcBride