This new MediaWiki feature has become available on all wikis, but it is unlikely that "normal users" using it. Pleas restrict the use on commons to sysop and bots.
I think that no local RFC is needed because this feature has been implanted without. I have prepared a JS hack to hide the the tools for all non sysops/bots, but js is bad for hiding such things, therefore i prefer a fix in the software directly.
Thanks in advice.
--Steinsplitter
I beg to differ, this feature is especially useful on Wikimedia Commons, where there are several user gadgets performing actions through API: rename requests, PotY votes, visual batch editor, etc.
Please open a discussion on Wikimedia Commons on this issue.
When I've just offered to differ the change restricting this for every wiki I had the Commons example in thought for the especially interesting of this tagging feature.
I will disable it with JS if you refuse to to do it server side.
The feature was enabled without consensus, so i need to consensus to switch it off...
Those gadgets will most likely use API action=edit&tags=... which does not require the changetags right (it is governed by a separate right applychangetags).
.mw-log-editchangetags-button, .mw-history-editchangetags-button { display: none; }in MediaWiki:Common.css would probably do the job.
I just wonder why a user would want to add/remove a tag? Is this the same as the tags that are automatically set through AbuseFilter? Is that at all desired? /confused
Disabling it in JS or CSS is useless, the server will still allow clients to do it. Clients can just block such resources or otherwise refuse to run them.
One confusing button less: Obviously there were no user-configurable tags, so the button invoked a page where the user could do just nothing...