It would be a great idea to enable Huggle on Commons. Although Commons is not hit much by vandalism unlike in enwiki, it would be better to have a powerful countervandalism on Commons. This would be very helpful for patrollers and rollbackers like me. Not only it is efficient in reverting vandalism and identifying good edits, but it also warns users automatically about their reverted edit (most of us Commons rollbackers don't warn users about their reverted edit, mainly because it is tedious to warn every reverted edit).
Yep, please see https://commons.wikimedia.org/wiki/Commons:Message_templates#Vandalism for vandalism, and https://commons.wikimedia.org/wiki/Template:No_advertising for spam. There are also other warnings at https://commons.wikimedia.org/wiki/Commons:Message_templates.
I don't remember, but it's possible, however I fairly sure the configuration wasn't finished otherwise this task wouldn't be still open. I think that warning templates and commons specific configuration is missing.
So I replaced the old config with new one which is documented pretty well.
Can someone tell me how vandalism is normally dealt with on commons? How many warning levels? Where are vandals being reported to?
Revert & block. See also https://commons.wikimedia.org/wiki/Commons:Vandalism
How many warning levels?
There are, but not often used AFAIK:
Where are vandals being reported to?
wow, these templates auto-translate, so there isn't really easy way for Huggle to determine which warning level they represent... maybe by icon? It would be nice if there was some invisible magic like it's on enwiki, for example: <!-- vandalism-lvl1 -->
the problem right now is with template parser, commons is only wiki that uses auto translating templates which don't contain any unique strings that could be used for identification of warning level they represent. Solution would be to add some "magic" like invisible comments similar to what we have on English wikipedia, for example <!-- uw-test1 --> etc so that Huggle would know which warning level it is. Without this it's not easy to enable Huggle in write mode as it wouldn't be able to recognize last warning level of template on vandal page.
Example of solution: