Sat, May 18
List users does it as well, for example: https://en.wikipedia.org/wiki/Special:ListUsers?username=DoRD&group=checkuser&wpsubmit=&wpFormIdentifier=mw-listusers-form&limit=1
Thu, May 16
Thu, Apr 25
@Pppery note, mediawiki in general supports most anything in display title if you enable displaytitle, if you do then you can also optionally lock it down - this ticket is only about locking it down. Individual WMF projects can certainly pick to enable or not enable lockdown. Perhaps a tangential task would be for something like a parameter to enforce in , or exempt in certain namespaces (if you'd want to go that route please open a different task though).
@Izno by default this isn't applied, only for projects that configure $wgRestrictDisplayTitle to be true
Apr 22 2019
Well it should be to "a permission" that certainly stewards could have, though the meta-wiki oversighters may be able to handle these a well (need a community discussion first since this went live prior to getting one made)
Apr 19 2019
I'm sure some of these tags are wrong, but this is just being ignored after recently being broken and I'm trying to get someone's attention.
Apr 17 2019
Just wondering - is anyone working on this? Has anyone been able to validate what the breaking change was?
Apr 16 2019
@MarcoAurelio I think this has been resolved, see example:
Regarding the URI PATH component there seems to be a legit use case for allowing arbitrary pages here such as "Hey friend, when you are ready create that page here: https://w.wiki/32m"
Apr 14 2019
In case anyone was looking for anything on this, note that accounts created via outreachdashboard.wmflabs.org have effectively been made throttle exempt
Apr 13 2019
Notes from enwiki discussion:
As was noted in T220885 some special pages (e.g. https://test.wikipedia.org/wiki/Special:RecentChanges) are still using the separators.
Notes from T220885
The following separators appear to be missing throughout the output:
Apr 10 2019
If this becomes a 'This accounts meets the minimum standards for Account security' checker, then perhaps it should also have an expanded output if run on 'self' - declaring what components you are missing so you know what you need to remediate?
@Volker_E almost all of the feedback is that there is much wasted horizontal space. The collapsing may be nice as well, but why the insistence on making this such a long vertical form when there is screen real estate available?
Apr 9 2019
@Dinoguy1000 we certainly can trim the enwiki css if it's useless - is there an example that can demonstrate this issue to verify?
Apr 8 2019
@Jdlrobson for mobile touch friendly - sure, use it when someone is in mobile mode - not in keyboard and mouse mode.
All that wasted horizontal area, combined with the much longer vertical usage seems to be the main complaint here, not so much the box decorations, if space is limited sure let it scroll to multiple lines, but when there is plenty of space to the right, use it. I'm certainly not looking forward this this same design layout coming to watchlists either.
Note, I'm not the one who said it was 50%, it appears to be about a third of the content area.
Yes, it was the "prior" but moving to OOUI forms certainly could have been used while maintaining the layout right?
Regarding the "form experience" - yuck. See also https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Hideous_history_page.
The example in the description showed all elements side by side, now there are huge gaps and the vertical layout makes this take up about a third of the screen.
Apr 6 2019
Apr 2 2019
I was able to reproduce this with a normal protected page, but then I it appeared to fix after a page purge - is consistently breaking with pages that are cascade protected though.
Reported on enwiki by Jmar67 in https://en.wikipedia.org/w/index.php?title=Talk:Main_Page&oldid=890569090#Editable_entries
Mar 29 2019
Mar 19 2019
Thanks for the update @jrbs so for those of us that give out int-admin locally, we'll just keep saying "you better do this" and leave it up to WMF to enforces the 2FA rules.
Breaking the redirect on the remote shared repository page (such as in https://commons.wikimedia.org/w/index.php?title=File:Lee_Dixon.jpg&oldid=343164913 ) restores the local projects access.
Mar 15 2019
@jrbs this specific task is only about the "allowing the community to check that an account really has enabled 2FA before granting it additional rights within the regular community process" part - so from a T&S point of view can it proceed (while not stopping any other types of improvement processes)?
Mar 13 2019
Emailed T&S asking for any update.
Mar 4 2019
Cancelling this, was updated in fc9efe67d599
I didn't protect as a security issue since it is failing safer.
Mar 3 2019
Mar 1 2019
@Urbanecm - also it only is used when the only reason for account creation fail is rate limit (see examples here: https://en.wikipedia.org/wiki/Special:Log/OutreachDashboardBot)
@Urbanecm the outreach dashboard creates all accounts via enwiki (which then due to SUL get autocreated anywhere when logged in) - and this exemption is allowed via a service account between the dashbaord and enwiki (https://en.wikipedia.org/wiki/User:OutreachDashboardBot).
For what it's worth, we have recently put in an process for account creation via outreachdashboard.wmflabs.org , the throttle is bypassed if the creation is made via an event on the dashboard. This certainly doesn't solve the core complaint, but may help with anyone running an event.
Feb 22 2019
I'd like to see this information in AF variables, no opinion as to the best way to accomplish it (including if a different variable should be used). A related item may be for edits that are protected by other means as well (such as a namespace protection, or a page type protection).
Feb 16 2019
Feb 13 2019
Jan 29 2019
I may have misstated the name of the permission - but the overall concept has not changed - just looking for a way to determine a yes-no on a project as stop-gap while T150562 is being worked on. If I recall correctly the current workflow is:
Jan 25 2019
In general, it's fine to add TimedMediaHandler.
Jan 23 2019
Jan 15 2019
Jan 14 2019
This appears to be a bypass for T204016
Jan 12 2019
@Iniquity I don't think anything was actually done here - some related discussion would be to make use of TAGS
Jan 11 2019
If you hit up arrow, or down arrow, you are back at 'letter 1' and can type a new first letter in
This appears to be working correctly, it is still collecting additional characters to resolve mutli-letter conflicts.
@Anomie that bot (https://en.wikipedia.org/wiki/Special:Log/TheSandBot) hasn't made any moves in a month.
Just got again on enwiki when trying to delete as part of this move: (https://en.wikipedia.org/w/index.php?title=MediaWiki:Gadget-defaultsummaries.js&diff=prev&oldid=877868868) , was able to manually delete the target and proceed.
Jan 7 2019
On-wiki discussion points to this just being an oversight in the creation (https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Requests_for_permissions&oldid=877253922#%22confirmed%22_users_can_no_longer_create_articles) please proceed.
Jan 6 2019
Jan 5 2019
Testing notes (may need another task) - users without createpagemainns ARE able to create these pages if they initialize a page in another namespace, then use the MOVE process - this seems like it should be a security violation.
Dec 20 2018
No please by default, but perhaps an opt-in confirmation if people really want it. Don't slow down workflows.
Dec 18 2018
On enwiki, we just purposefully granted an account this combination, I suspect the other projects have as well.
Dec 15 2018
Closing as unable to be replicated and no additional information from reporter.
Dec 13 2018
I'll follow up with the reporter again.