Language is hackable via JS but settings like 'set timezone to blah blah, disable VE if it's enabled, disable compact language if enabled, set email to plaintext only, disable xwiki notification, ...' can't be done via JS hack, which is unfortunate. -- Yongmin Sent from my iPhone https://wp.revi.blog Please note that this address is list-only address and any non-mailing list mails will be treated as spam. Please use https://encrypt.to/0x947f156f16250de39788c3c35b625da5beff197a. 2017. 5. 10. 16:26 Martin Urbanec <martin.urbanec(a)wikimedia.cz> 작성:

I understand that there exist some JS hacks, but I doubt that is what average user can live with. I think we should make these options available for general public, in a user-friendly manner and not only to few people with knowledge that enables them to hack mediawiki interface so that it works well enough for them. On Wed, May 10, 2017 at 1:42 PM, Johan Jönsson <jjonsson(a)wikimedia.org> wrote:

We had some discussions about this at the devsummit, since it was on one of the wish lists.. https://phabricator.wikimedia.org/T16950 At that time I suggested it would probably be easier and less risky, to start of with a tools project, that allows you to apply a setting to all our properties. Saves you a lot of the effort of figuring out how to 'position' this in the UI, and what to do when people want exceptions to global defaults etc.. DJ On Wed, May 10, 2017 at 5:16 PM, Brad Jorsch (Anomie) <bjorsch(a)wikimedia.org > On Wed, May 10, 2017 at 3:48 AM, Yongmin H. <lists(a)revi.pe.kr> > > Language is hackable via JS but settings like 'set timezone to blah blah, > > disable VE if it's enabled, disable compact language if enabled, set > email > > to plaintext only, disable xwiki notification, ...' can't be done via JS > > hack, which is unfortunate. > > > > It probably can, almost[1] anything you can change in Special:Preferences > could be changed via something in your global user JS calling the action > API's action=options. > > The main drawback is that it wouldn't take effect on a wiki until after the > first time you visit a page there that loads your global user JS. > > > [1]: There are a few things like 'realname' and 'emailaddress' that can't > be set that way. > > -- > Brad Jorsch (Anomie) > Senior Software Engineer > Wikimedia Foundation > _______________________________________________ > Wikitech-l mailing list > Wikitech-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l >

Bryan Davis wrote: Why? Do you really believe that setting global user preferences should require a third-party Python Flask tool that relies on JavaScript and OAuth to set a user preference on every wiki? How is duplicating a default value to hundreds of wikis, in a separate code base with its own user interface, a sane or desirable architecture? MZMcBride

2017-05-11 17:16 GMT+03:00 Brad Jorsch (Anomie) <bjorsch(a)wikimedia.org>rg>: My understanding is that the code is kind of there already, but it would have to be deployed, and before deployment it would have to be reviewed. So the manager to convince would be the manager of the team that needs to review and deploy it. Being the PM of the Language team, I couldn't support global preferences (and lots of other global things) any more strongly, as they would be clearly beneficial to the users of multiple wikis. But in the current organizational structure, the implementation and the deployment of global preferences is much closer to the realm of the MediaWiki Platform team. -- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com ‪“We're living in pieces, I want to live in peace.” – T. Moore‬

Brad Jorsch (Anomie) wrote: Yes, but that's not so bad. After someone deleted a ton of skin user preferences, I added this snippet to my "global.js" subpage on Meta-Wiki, with Legoktm's help: /* Set skin to MonoBook */ mw.loader.using("mediawiki.user", function() { if ( mw.user.options.get('skin') !== 'monobook' ) { mw.loader.load("mediawiki.notify"); ( new mw.Api() ).postWithToken( 'options', { action: "options", change: "skin=monobook" } ).done( function() { mw.loader.using("mediawiki.notify", function(){ mw.notify( "Skin has been changed to MonoBook. Please refresh the page." ); } ); } ); } } ); It works pretty well. It's certainly easier than going to Special:Preferences on each wiki. Some links: * https://phabricator.wikimedia.org/T16950#2185759 (April 2016) * https://phabricator.wikimedia.org/T154956#2929966 (January 2017) MZMcBride