Sun, Jul 23
Thu, Jul 20
on-wiki is too dependent on random editors - ANY non-free license should override any free license
Tue, Jul 18
Mon, Jul 17
@jsn.sherman I can now log on.
Sat, Jul 15
Steps to reproduce now:
- go to wikipedialibrary.wmflabs.org
- press logon
- get error
Fri, Jul 7
Just had another user with issue (https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(technical)&oldid=789384548#Problem_with_logging_in) Nineko - they only got in after finding a wiki they had never logged in to with central auth (zh.wikivoyage in this case).
Thu, Jul 6
@MusikAnimal - forget that last one - there was a deletion action in the middle there.
Here is another example, in this case the page history also shows the size wrong (+163)
Sun, Jul 2
@Reedy is there anything you want done here?
@Zoranzoki21 see https://en.wikipedia.org/wiki/Wikipedia:Using_AWB_with_2FA for the "Easy Guide"
Just had another one reporting on enwiki, User:Thankyoubaby - had them resolve it by browsing directly to https://login.wikimedia.org
Sat, Jul 1
Fri, Jun 30
In some cases it could be desirable to link back, so if this is going to be implemented it should be in a manner that is editor controlled as to the link back target.
Jun 24 2017
Jun 14 2017
Please note, as decided in Wikipedia:Articles for deletion/Screenshot/fodder the English Wikipedia community rejects having such test pages hosted in mainspace. Possible alternatives would be loading the text to a specific version, or using a different namespace.
Jun 7 2017
If it really is a title only search perhaps "Show page titles containing:" would be ever better
May 31 2017
WMF legal replied:
May 30 2017
@Mholloway is this concern related to a specific interface (e.g. the Android Mobile Client interface, the general Web interface) ?
May 25 2017
@RobH (https://en.wikipedia.org/w/index.php?title=Wikipedia:Bureaucrats%27_noticeboard&oldid=782186616) was opened and closed out as DELETE the archives. Please review that discussion. Note there was no reply from WMF legal - but if there are legal controls in place than existing foundation policies would trump these volunteer decisions.
May 24 2017
May 21 2017
enwiki discussion has asked if there are WMF-Legal issues that need to be addressed - dropped them an email.
May 19 2017
I prodded the enwiki discussion at https://en.wikipedia.org/wiki/Wikipedia:Bureaucrats%27_noticeboard#wikien-bureaucrats_archives
May 16 2017
Apr 26 2017
@RobH we will review the archive needs and submit a separate ticket for them if this is closed prior to a decision.
Apr 17 2017
There is a enwiki RFC open that may resolve the community consensus question here: https://en.wikipedia.org/wiki/Wikipedia_talk:Translation#RFC
One recurring issue has been trouble with the translation tool interface - it is hard to add community controlled messages in to the page - adding a MediaWiki transclusion to the page where community expectations could be spelled out may be sufficient. Any devs of this tool have options for us?
Apr 16 2017
@kaldari - the existence of the enwiki abusefilter is preventing all CXT by newer users to the English Wikipedia - however it does not represent a community consensus that machine translation is supported otherwise - please cite an enwiki discussion supporting enabling machine translation - the only thing I am seeing in https://en.wikipedia.org/wiki/Wikipedia:Translation#Avoid_machine_translations - specifically saying to avoid machine translations for all editors.
Apr 7 2017
Apr 5 2017
Apr 3 2017
Mar 30 2017
Mar 22 2017
Another example on enwiki - going to a page with editnotices (e.g. https://en.wikipedia.org/w/index.php?title=Abortion&action=edit) using the source editor works fine - if switching to VE the notices are lost, manually looking for them in the triangle button says no notices. (Firefox, monobook)
Jan 30 2017
Jan 27 2017
Jan 9 2017
In Firefox 50.1.0 I don't see a key named network.cookie.maxPerHost - is the workaround suggesting to create this key, is so what datatype?
Jan 4 2017
I'd like to see an optional set of parameters for protection to solve this. 2 possible workflows:
Jan 1 2017
Dec 20 2016
Dec 19 2016
I'm not too picky on the "how" as long as the result is that information on if the password was correctly guessed is not revealed. Similarly, the authentication failed error message should not be different for bad token vs bad password vs bad both.
Suggested implementation would be to collect all authentication information simultaneously (userid, passphase, 2FA response). For accounts without 2FA enabled, simply ignore any (including null responses) to the challenge response.
Dec 16 2016
I'm not sure what dewiki is trying to do, but its a mess to readers right now who are seeing this:
Thank you for the note.
I suppose whatever parts the local communities want. If devs are pushing that only plain text and the variable will be supported for this interface then this (and the parent) should just be moved to won't fix.
@Anomie this is "by design" ?
@Legoktm it appears that both the use of #if statements, as well as wiki formatting like bold are no longer being processed.
Dec 10 2016
Related discussion with some examples:
For global renames: would be handy to have a "name history" - perhaps a seperate log request - e.g. given a current name, what were all prior names. This is available in the global rename log, but has to be recursively queried name by name.
@Legoktm thank you - verified it works for multi-action Global Renames as well.
@Legoktm no more of the opposite - entering only the "current" name should be able to find the rename log that made the current name come in to existence.
Adding "prior username" to the local move log would be fine and could be useful too
Possibly related to T40123
Possibly related to T152830
Possibly related to T152829
Dec 1 2016
Maybe the footer needs work too - that doesn't tell you if it came from say enwiki, eswiki, dewikibooks, etc
Perhaps something like email@example.com and include which project generated the mail? Examples:
firstname.lastname@example.org; email@example.com; etc./
Nov 24 2016
Our standard project settings don't give bots editinterface access - this has to be specifically added, project policies should be able to resolve your concerns - and if someone won't follow policy they don't get access.
@Krinkle BotPassword restrictions in general are working (for example I didn't enable rollback on my personal account and couldn't use utilities like Huggle that checked for it until I did).
Nov 16 2016
I believe it is time based - had you recently authenticated before attempting this?
Nov 15 2016
Community notified this is going live, baring any last min complaints here.
@Reedy I don't think this is really an OATH issue. This already is happening for certain sensitive actions such as password change and email change. This could be accomplished by simply requiring re-authentication in general for additional actions.
Nov 13 2016
@Reedy I'm successfully using BotPasswords with AWB already - what is this task about?