Hi.
The German Wikipedia has evaluated and decided against the default use of MediaViewer on its project (preferring opt-in, rather than opt-out). Erik has made it his mission to impose MediaViewer on the German Wikipedia using Wikimedia Foundation staff coercion (cf. https://gerrit.wikimedia.org/r/153302 and https://gerrit.wikimedia.org/r/153345). Both changes have been pushed through hastily and have had negative repercussions as a result (missing translations, disrupted workflows, etc.). From a recent Bugzilla comment about the latter change, "it's clear this change was a kneejerk reaction without a lot of thought as to the effects."
The security of the entire MediaWiki infrastructure, which in turn is the security of a large portion of Wikimedia wikis, heavily relies on the idea that local administrators can be trusted. With his provocative actions, Erik has declared war on the German Wikipedia.
Given this, there are options for the German Wikipedians. This is a non-exhaustive list and may not reflect the latest waste of developer and system administrator resources coerced by Erik.
* Local disruptive accounts (such as "User:Eloquence" and "User:JEissfeldt (WMF)") can be locally blocked by German Wikipedia administrators for conduct unbecoming.
* Global accounts can have their privileges removed by stewards, who are intended to serve as the "root" users of Wikimedia wikis.
* While the German Wikipedia's "MediaWiki:Common.js" has been super-protected, there are other pages such as "MediaWiki:Vector.js", "MediaWiki:Monobook.js", and "MediaWiki:Group-user.js" that can probably be used to achieve the same effect.
* Importing edits on top of an existing page should replace the content and bypass any protection, though this theory needs additional testing.
* Certain pages in the MediaWiki namespace such as "MediaWiki:Copyright" still allow raw HTML, which can be used for a direct "<script>" insertion.
* JavaScript gadgets can be enabled by default across a wiki.
* CentralNotice from Meta-Wiki can be used to deploy JavaScript to the German Wikipedia.
There are also more extreme options available.
* Using per-user CSS or JavaScript to forcibly hijack Erik's or another staff member's account. This can be done locally on any wiki, including sites such as Meta-Wiki.
* Disabling editing and/or reading of the German Wikipedia, using a variety of tools. Erik's declaration of war makes this option viable, but it should likely be used only as a measure of last resort. If Erik is truly hell-bent on damaging or destroying the wiki model, perhaps the wiki should simply cease to be. Using the title blacklist, the AbuseFilter extension, site-wide JavaScript and CSS, and other techniques, it's possible to fully disable reading and/or editing of the German Wikipedia until an amicable solution can be found.
* A Wikimedia-wide vote of no confidence for Erik. Again, this is an extreme option, but given Erik's behavior over the past few weeks (including his actions on the English Wikipedia, which resulted in an arbitration case involving him), beginning a vote of no confidence is an idea worthy of consideration.
There are also alternate options.
* Disabling the MediaViewer extension by default on the German Wikipedia, as requested by the German Wikipedia community.
* Accepting Erik's authority over the technical infrastructure of Wikimedia wikis and allowing him to rule as a technical autocrat.
I'm interested to read others' views about options and ways forward here.
MZMcBride
One more option: wait for WMF to make wiki unbreakable and scriptable *properly*, using something like Firefox's jetpack (which is fool proof)
On Mon, 11 Aug 2014, at 12:12, MZMcBride wrote:
Hi.
The German Wikipedia has evaluated and decided against the default use of MediaViewer on its project (preferring opt-in, rather than opt-out). Erik has made it his mission to impose MediaViewer on the German Wikipedia using Wikimedia Foundation staff coercion (cf. https://gerrit.wikimedia.org/r/153302 and https://gerrit.wikimedia.org/r/153345). Both changes have been pushed through hastily and have had negative repercussions as a result (missing translations, disrupted workflows, etc.). From a recent Bugzilla comment about the latter change, "it's clear this change was a kneejerk reaction without a lot of thought as to the effects."
The security of the entire MediaWiki infrastructure, which in turn is the security of a large portion of Wikimedia wikis, heavily relies on the idea that local administrators can be trusted. With his provocative actions, Erik has declared war on the German Wikipedia.
Given this, there are options for the German Wikipedians. This is a non-exhaustive list and may not reflect the latest waste of developer and system administrator resources coerced by Erik.
Write an extension which removes superprotect from the wiki. Get local consencus on installing that.
svetlana
BTW you should all love this idea: https://meta.wikimedia.org/wiki/Community_Engagement_%28Product%29/Process_i...
svetlana
The page is already overly long and in places impenetrable, and I speak as a systems analyst with Agile development experience. A shift to plain English might be useful and more care to avoid dropping in fringe jargon like "Wiki markup is not Turing complete". On 22 Aug 2014 01:39, "svetlana" svetlana@fastmail.com.au wrote:
BTW you should all love this idea:
https://meta.wikimedia.org/wiki/Community_Engagement_%28Product%29/Process_i...
svetlana
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe
wikimedia-l@lists.wikimedia.org