[01:51:01] <lpt>	 There is a mistake in the table for the resistance of copper wire.  Another user has already pointed it out but it has not been fixed.  How do I fix it or get it fixed.
[01:52:13] <jackmcbarn>	 lpt: what wiki is this about?
[01:53:41] <lpt>	 If you look up wire gauges the table that comes up has a column that is completely in error.  It lists the ohms per 1000 ft of wire but the number are off by an order of magnitude
[01:54:09] <Krenair>	 That doesn't answer the question, lpt.
[01:54:41] <jackmcbarn>	 is this about en.wikipedia.org?
[01:54:51] <lpt>	 sorry, but this is the first time I have tried anything so I do not know the jargon.  I am referring to Wikipedia
[01:55:04] <jackmcbarn>	 okay. just hit "edit" and find the number and change it and hit "save"
[01:55:33] <lpt>	 The whole column is wrong, there are an awful lot of entries
[01:56:06] <lpt>	 And I do not know the exact correct values
[01:56:12] <Krenair>	 I'm guessing  you want the #wikipedia-en channel
[01:57:21] <lpt>	 What does that mean?
[01:58:35] <lpt>	 I give up, let someone else fix it.
[02:15:36] <refffg>	 we need an op in #wikipedia-en-blp
[02:19:01] <refffg>	 !op
[02:19:01] <wm-bot>	 There are multiple keys, refine your input: openbasedir, openid, opsschool, opw, 
[02:19:13] <refffg>	 i need help
[02:19:13] <wm-bot>	 Hi refffg, just ask! There is no need to ask if you can ask
[02:19:24] <refffg>	 now
[02:19:25] <refffg>	 help
[02:19:49] <Krenair>	 what?
[03:13:02] <No_one_at_all>	 so the javascript constructor mw.Uri does not exist (is undefined) on our wiki. Any idea why?
[03:20:29] <xdaveyx>	 Hello
[03:33:34] <Katie>	 Hi xdaveyx.
[03:33:58] <xdaveyx>	 Hi Katie. 
[03:34:22] <xdaveyx>	 I am looking at doing some scripted importing with mediawiki.
[03:34:26] <xdaveyx>	 Is it possible to use maintenance/edit.php with namespaces?
[03:53:09] <Katie>	 Probably, yeah.
[06:42:44] <josephine_l>	 Hi Niharika and tonythomas - either of you around? :)
[06:43:11] <Niharika>	 Hi josephine_l. What's up? 
[06:43:32] * tonythomas lurkes
[06:43:59] <josephine_l>	 Niharika : Is it okay for me to create the subtask for my community bonding report soon, state that it's a work in progress, and just fill it in as I go?
[06:44:08] <josephine_l>	 It's a bit early but I tend to forget stuff :P
[06:44:37] <josephine_l>	 On the other hand if you guys might want some format changes etc I should probably wait til it's closer to the end of the bonding period?
[06:45:28] <Niharika>	 josephine_l: Yeah, sure. :) Don't create a subtask of that task I linked, because it was for the last round and is now closed. Just make a task and copy one the information mentioned in that task. 
[06:45:37] <Niharika>	 It's fine, you can create it. 
[06:46:19] <josephine_l>	 Thanks Niharika! I'll just subtask my main project task, that okay?
[06:46:41] <Niharika>	 josephine_l: Yes, that sounds good. 
[06:46:49] <josephine_l>	 Cheers :)
[11:59:37] <domax>	 Hi, can anyone provide login support for me? 
[11:59:58] <domax>	 i can't login to my account anymore, and password reset does not send me an e-mail 
[12:01:26] <Na3iL>	 domax, What web-mail you use?
[12:02:04] <domax>	 google mail
[12:02:29] <domax>	 gmail.com
[13:55:42] <Niharika>	 I'm also facing an issue in receiving password reset emails. If someone else can reproduce the issue, I can file a ticket.
[14:00:41] <Reedy>	 Niharika: Probably just file one
[14:01:29] <Niharika>	 Will do.
[14:46:13] <mildused>	 How come mediawiki registration has First Password, Domain: labs, then Confirm Password? Shouldn't the passwords be together?
[14:52:42] <Reedy>	 It'd probably look nicer
[14:52:50] <Reedy>	 But it's probably just the way it's built into the form
[14:52:55] <Reedy>	 mildused: File a bug asking for it fixing :)
[14:53:21] <mildused>	 Or fix it myself?
[14:53:38] <Reedy>	 You could, yes
[14:53:50] <Reedy>	 Might be worth filing a task anyway, even if you plan on fixing it yourself
[14:54:04] <Reedy>	 But you don't have to
[14:55:09] <Reedy>	 https://github.com/wikimedia/mediawiki-extensions-LdapAuthentication/blob/master/LdapAuthentication.php#L762-L776
[14:55:12] <Reedy>	 That's for the login form
[14:58:15] <mildused>	 Reedy: Thanks
[15:46:08] <Reedy>	 mildused: Did you submit your other patch?
[15:47:00] <mildused>	 Reedy: Other patch?
[15:47:14] <Reedy>	 'api-error-duplicate-archive'
[15:47:29] <mildused>	 I thought I did
[15:48:02] <Reedy>	 What's your gerrit username?
[15:49:54] <mildused>	 opatel99
[15:51:50] <Reedy>	 Bleh, gerrrit does it on email
[15:51:59] <Reedy>	 I can't see a merged or open changed for that
[15:52:23] <mildused>	 Let me check. 
[15:54:48] <Vulpix>	 maybe you did git commit but not git review?
[15:55:00] <Reedy>	 Looks like that might be the case
[15:55:14] <mildused>	 Seems to be. I'll get it fixed
[15:55:19] <Reedy>	 :)
[16:02:42] <mildused>	 Reedy: Can I mark you as reviewer?
[16:02:47] <Reedy>	 Sure
[16:03:22] <Reedy>	 "Mulhall is an Anglicized Irish name"
[16:03:58] <saper>	 quite possible
[16:04:24] <Reedy>	 saper: Wrong channel :P
[16:16:55] <mildused>	 Oh I first cloned it as anonymous. I gotta clone the core from my ssh. Reedy , first commit coming up.
[16:17:04] <Reedy>	 mildused: No you don't
[16:17:08] <Reedy>	 You can just change the remote
[16:33:56] <mildused>	 Reedy: May I PM?
[16:34:09] <Reedy>	 Sure
[18:00:41] <Supervivente>	 Hi, how can I get the list of page revisions which are not patrolled, using API?
[18:06:59] <Vulpix>	 edit patrolling is done in recent changes, so it should use the recent changes api
[18:08:02] <Vulpix>	 Supervivente: https://www.mediawiki.org/wiki/API:RecentChanges  rcshow=!patrolled
[18:09:27] <Supervivente>	 thanks, but I need revisions for specific page
[18:10:44] <Vulpix>	 Supervivente: that's not possible, the patrolled propery is stored in the recent changes table, not in revision
[18:11:52] <Vulpix>	 recentchanges api doesn't allow to filter by title
[18:12:10] <Vulpix>	 also note that old entries in the recent changes table are purged periodically
[18:14:58] <Supervivente>	 maybe I can get the last patrolled revision ID for the page?
[18:21:12] <Vulpix>	 not from API
[18:22:39] <Reedy>	 bawolff: Increase
[18:22:39] <Reedy>	 :P
[18:23:04] <bawolff>	 crap
[18:23:22] <Reedy>	 heh
[18:36:42] <mildused>	 How come "Account creation error You have not specified a valid username." during registration only occurs after pressing submit? Can it be done such that all requirements are fulfilled live before submission?
[18:37:02] <Reedy>	 They could, but not everyone has JS enabled, which would be needed
[18:37:51] <Reedy>	 So you'd still need both
[18:37:53] <mildused>	 Ahh.
[18:38:12] <mildused>	 but that could be in <noscript>
[18:38:42] <bawolff>	 I imagine its just that nobody has written the code to support doing that
[18:39:04] <mildused>	 May I?
[18:39:17] <bawolff>	 Yes of course
[18:39:23] <bawolff>	 Patches always welcome
[18:39:44] <Reedy>	 I seem to recall MaxSem or someone trying to do password validation in JS... Maybe?
[18:39:47] <Reedy>	 That didn't make it in
[18:40:04] <Reedy>	 mildused: Have a look in phabricator, someone might have filed a task for it, and there might be other ideas
[18:40:19] <mildused>	 Thanks Reedy bawolff . I'll look into it
[18:40:39] <Reedy>	 Maybe an API module to do the validation might be the better way
[18:40:49] <Reedy>	 Rather than duplicating copious code into JS
[18:41:14] <bawolff>	 You have to be careful with password validation. if you do it with ajax, its possible to leak info about the password. Especially if you do it based on an onchange event
[18:41:28] <Reedy>	 Aye
[18:41:52] <bawolff>	 but usernames are pretty public, so I think username validation would be totally fine
[18:42:08] <Reedy>	 Ditto
[18:42:40] <mildused>	 maybe a password strength api?
[18:43:30] <Reedy>	 As bawolff said, we've then got issues sending plaintext passwords
[18:43:36] <Reedy>	 So is much of a grey area
[18:43:47] <Reedy>	 Like I say, there was at least one attempt of that a little while ago
[18:44:11] <mildused>	 Maybe I could better allocate my time. The topic seems to be contested
[18:44:31] <bawolff>	 mildused: Checking if the username is already taken should be uncontroversial
[18:45:53] <mildused>	 Yeah. I'll try it out. Leaving the passwords alone since it's sketchy
[18:55:11] <Katie>	 Hmmm.
[18:55:23] <Katie>	 I thought input validation got added when the form was recentlyish redesigned.
[18:55:26] <Katie>	 To include the silly stats.
[19:39:36] * bawolff had no idea that baseball is the #12 most popular password
[19:46:04] <mildused>	 b453b4ll
[19:48:01] <bawolff>	 mildused interestingly enough, that's not in the top 1 million. I kind of would expect it to be
[19:49:15] <Reedy>	 bawolff: Might be worth checking with ori etc if it should be a cdb... As we seem to be moving away from them for some things
[19:50:30] <bawolff>	 hmm, I'll add him as a reviewer to the patch
[19:52:11] <Vulpix>	 I'd expect that password check to be an extension and not in core
[19:52:24] <Reedy>	 hehe
[19:52:38] <bawolff>	 Vulpix: I could see arguments either way
[19:53:12] <bawolff>	 But if we enable it by default (unclear if we will), I think its makes more sense in core
[19:53:51] <Vulpix>	 well, I don't see a task where this discussion should be going
[19:54:06] <Reedy>	 heh
[19:54:46] <bawolff>	 Step 1 to manipulating public opinion, avoid giving places for people to express their opinion ;)
[19:54:59] <Reedy>	 CR +2 HURRY REVIEW
[19:55:50] <bawolff>	 Vulpix: For now maybe mention on the patchset, and see what others think
[19:56:17] <Vulpix>	 I'm not really opposed to it, but I think there was some sort of convention to not bloat core with things that should be in extensions
[19:56:33] <Vulpix>	 like Extension:HitCounters etc
[19:56:54] <Vulpix>	 although there are moves in the other direction as well... <poem> etc
[19:56:58] <bawolff>	 HitCounter was more because it was kind of crap
[19:57:01] <Vulpix>	 I'm confused :S
[19:57:21] <mildused>	 Same..
[19:57:31] <mildused>	 Except my confused is different than your confused
[19:58:29] <bawolff>	 I think HitCounter was removed because it caused performance problems, wasn't very good at giving analytics as had no notion of time frame, and was incompatible with front-end caching (varnish, etc)
[19:59:22] <bawolff>	 In my experiance, some people like putting things as extensions, and some don't, and we have a tendency to go in somewhat of a cycle between making everything into an extension and making nothing into an extension
[20:00:50] <mildused>	 I guess after users become dependent on an extension such that it's a necessity to install it, it'd be worthwhile to merge that extension into core.
[20:01:47] <Reedy>	 We've had stuff stripped out of core, and stuff put into core
[20:02:02] <Reedy>	 Some of it is historical when mw core wasn't so open
[20:02:31] <Vulpix>	 My idea was: Extension if it can be done as an extension easily (with hooks, etc) and it's not considered something trivial or extremely used. Otherwise in core. This one seems to be trivial to implement as an extension, and is also optional
[20:03:22] <mildused>	 The goal may be to ensure the core is lightweight, but still containing the features that are requisite for usage. The question then turns into How essential is this feature compared to other features that have been deemed core-worthy.
[20:04:06] <Reedy>	 Yeah, it would be trivial to put into an extension
[20:05:41] <Vulpix>	 well, now that I see the PasswordPolicyChecks class, it could be all an extension
[20:05:52] <Reedy>	 lol
[20:06:47] <Vulpix>	 I think there's already an extension to check password lenght somewhere
[20:06:55] <bawolff>	 no, that's in core
[20:07:37] <Reedy>	 There's a SecurePasswords extension
[20:07:45] <Reedy>	 Which can do that stuff
[20:08:05] <Vulpix>	 https://www.mediawiki.org/wiki/Extension:SafeCreate
[20:08:08] <Reedy>	 https://github.com/wikimedia/mediawiki-extensions-SecurePasswords
[20:08:17] <Katie>	 There's also SecureSessions.
[20:08:20] <Katie>	 But that's something else.
[20:08:34] <Reedy>	 https://www.mediawiki.org/wiki/Extension:SecurePasswords#Configuration_parameters
[20:09:34] <bawolff>	 The majority of that extension is in core now (although not the digit/symbol/letter requirements)
[21:52:50] <bawolff>	 Its really against coding standards to do for ( $i = 0; $i < count( $foo ); $i++ ) ?
[21:52:54] <bawolff>	 seems kind of silly
[21:52:59] <bawolff>	 count is constant time afaik
[21:53:56] <Reedy>	 doesn't it repeatedly calculate the count?
[21:55:46] <bawolff>	 yeah, but I thought php arrays stored the total number of elements, making count($foo) O(1)
[22:41:36] <Krenair>	 http://php.net/manual/en/function.count.php#116726 implies that is the case now but wasn't always
[22:41:48] <Krenair>	 Reedy, ^
[22:51:56] <Reedy>	 Krenair: Which version did that change in?
[22:52:07] <Reedy>	 And as we're still supporting 5.3 we should code towards that..
[22:52:08] <Krenair>	 I didn't look into the details
[22:53:24] <Reedy>	 [1] https://github.com/php/php-src/blob/PHP-5.5/ext/standard/array.c#L306 
[22:53:24] <Reedy>	 [2] https://github.com/php/php-src/blob/e10e151e9b92313a7085272c85bebf6c82017fce/ext/standard/array.c#L264
[22:53:38] <Reedy>	 5.5 seems to be still counting
[22:53:38] <Reedy>	 		case IS_ARRAY:
[22:53:39] <Reedy>	 			RETURN_LONG (php_count_recursive (array, mode TSRMLS_CC));
[22:54:07] <Reedy>	 So presumably it's 5.6 or 5.7 it's fixed in
[22:56:46] <Krenair>	 look at the source of that function