Wouldn't it be useful to allow specifying values for this global in extension.json directly?
Sun, Jul 15
Wouldn't it be much easier to provide an universal way to read effective preferences? It seems useful to allow extensions to modify the way preferences are read. possibly by injecting another method of reading them out of the database.
Thu, Jul 5
But please make clear that a talk page isn't a online comment section…
Fri, Jun 22
@Legoktm Will you have time to review this patch soon?
Jun 13 2018
Furthermore, I don't think FzW is a sufficient platform for a community consencus to topics like that, as this really affects many users and isn't just a little technical detail. Furthermore, the whole discussion seems quite biased to me.
Shouldn't this be resolved?
Jun 10 2018
Just to point this out, https://dewp.org is owned by the German Wikimedia chapter (WMDE), so there shouldn't be any security problems with this one.
Jun 4 2018
1600px seems a bit much as breakpoint for the right sidebar. (Personally, I'm kind of fond of the idea to maybe move parts of article content there in the long term, for example infoboxes, references or images maybe.) Is it possible to try the proposed settings somehow?
I would really like this addition with its own log action.
Jun 3 2018
Are there any plans to activate page creation logs on wmf servers? I would really appreciate it.
Jun 2 2018
Am I allowed to change the name from wgPrefix to allowedPrefix? This would be a breaking change, but seems appropiate to me.
May 31 2018
Should I catch the case that someone explicitly set an empty array for the new setting? How would I do that?
May 22 2018
I can work on this (and will do it at some point), however it might take some weeks. If someone else wants to do it, please do!
The patch is actually done, but there are three different issues handled by it.
- I put the methods into a class so they could be autoloaded by extension.json.
- I implemented a better and more versatile settings architecture because the old one didn't work really well with extension.json.
- I actually converted the whole thing to extension.json
There were some wishes to split the patch up, so I did that. At the moment, I'm awaiting review for the first one.
May 13 2018
I think that can be done analogous to the implementation of the $wgAutopromoteOnceLogInRC configuration setting.
Looks like a nice easter egg to me. (What makes it even funnier for me: The contrast is that low that I'm unable to see it unless I look at my screen at an angle.
May 8 2018
This needs to be backported into MW 1.31 after being merged, as the removal of autopatrol log entries happened before the branch point (assuming autopatrol entries are cleared during the update?)
I think this subtype should be deactivated to prevent this query to be run. It is of no use at all now.
Apr 30 2018
Oh, even six years later I want to note that Variables can double parsing speed.
Apr 29 2018
Apr 27 2018
Apr 26 2018
First patch has still issues, if you look for Umherirrenders comment.
Apr 25 2018
Apr 21 2018
Apr 19 2018
Is there a date set when to do this? I assumed HHVM compatibility would cover our needs.
What exactly is blocking master to require PHP 7, if even 1.31 is already requiring it?
Apr 15 2018
Apr 11 2018
I just retested it, the behavior hasn't been fixed at all. This isn't happening on normal view, so it's definitely an Android app issue.
Apr 9 2018
Apr 8 2018
The method in question was removed in https://gerrit.wikimedia.org/r/#/c/386639/ after it has been deprecated since 1.24. Just replace it with WikiPage::onArticleCreate().
Apr 7 2018
Are there any plans to move forward with this?
Apr 6 2018
Note that this task wasn't fixed as proposed in the task description, but by adding a option in the parser to mark tags that are problematic in this way.
Apr 5 2018
Why shouldn't you block IP ranges like that? It's happening all the time that given IPs troll at one specific page…
To maintain backwards compatibility, it should be possible to turn off the new behavior, although it should be expected.
Mar 30 2018
As user agent based blocking is only allowed in combination with ip r(ange) blocking, the collateral damage shouldn't be really large.
I propose the pages associated with Q4580256 for a mass message or something like that.
Mar 14 2018
If you just change one of these many parameters, the block isn't triggered anymore as the resulting hash is different. The more different parameters we're hashing, the easiert it gets to find some to easily change to do this.
Ideally we will use enough parameters to create very unique fingerprints making it harder to "brute force" the hash
including all patrol actions prior to April 2016
I don't think this is the right approach for removal of autopatrols out of the logging table. Autopatrols before April 2016 are distinguishable, even if not by log_action, and by doing this we would lose a lot of actual data in contrast to removing only autopattrol actions.
Mar 11 2018
I think this might be problematic because transcluding changes the apperance of many templates especially if additional parameters have been specified.
Mar 9 2018
@Huji: Thank you very much!
Mar 7 2018
I agree with @stjn. This change has nothing to do with the community wishlist proposal (which isn't consensus anyway). Non-latin languages have their problems solved already if we move to 255 characters instead of bytes.
Just a( (late) idea: Maybe we could just suppress summary notifications on minor edits? This would be similar to how nominornewtalk works.
This reduction would be a helpful partial fix in any case.
Mar 4 2018
Mar 3 2018
Of course my concern isn't the backend possibility to store longer comments, but that it's possible right now to actually enter any text up to 1000 bytes at the ui.
On the one hand, this isn't an enwiki issue, on the other hand, in my opinion there isn't any need to community discussion reverting problematic changes, this can be done afterwards. If there's a problem, just rest it to the status quo and deal with it afterwards.
Mar 2 2018
Just use MediaWiki system messages for these things, as we always do it this way.
In my opinion, this needs to be reverted as soon as possible, as there is no frontend adjustement for this change whatsoever.
Feb 28 2018
Nevertheless, this task can't be done until T184791 is done.
Feb 26 2018
While I'm certain we won't start evaluating templates in edit summaries just to do this, pipes should definitely be supported. I stated this before at T186655#3954502, getting universal acclaim (including you, @TBolliger ?). However, I'm unsure if this is already incorporated in the merged patch. @Catrope @MaxSem: Is it?
Feb 25 2018
This can't be done easily as custom signatures contain text in nearly all cases. This text would need to be localized.