[01:03:08] hah, don't let anyone other than nik touch it [01:06:35] <^d> jeremyb: ;-) [06:18:44] TimStarling: Mahdi apparently has not confirmed his email, and has lost his password, and so the only way he could get it reset is if you sent it manually [06:19:09] (for a Wikipedia) [06:19:35] uhhh, where did you learn this? [06:19:45] jeremyb: from -stewards [06:19:51] * jeremyb goes there [06:25:37] this is User:Mahdiz? [06:25:47] yes [06:25:48] https://fa.wikipedia.org/w/index.php?title=%D9%88%DB%8C%DA%98%D9%87%3A%D8%B3%DB%8C%D8%A7%D9%87%D9%87%E2%80%8C%D9%87%D8%A7&type=newusers&user=&page=%DA%A9%D8%A7%D8%B1%D8%A8%D8%B1%3AMahdiBot&year=&month=-1&tagfilter=&hide_thanks_log=1 [06:26:00] specifically his bot account is inaccessible [06:26:13] he says his normal user account is fine [06:26:28] make a confirmation edit i guess? [06:27:10] shorter URL: https://fa.wikipedia.org/w/index.php?title=ویژه%3Aسیاهه‌ها&type=newusers&user=&page=user:MahdiBot&year=&month=-1&tagfilter=&hide_thanks_log=1 [06:27:15] gah [06:27:51] https://fa.wikipedia.org/w/index.php?title=special:log&type=newusers&user=&page=user:MahdiBot&year=&month=-1&tagfilter=&hide_thanks_log=1 [06:27:55] that's better :) [06:28:16] my bot can edit in 23 october [06:28:18] https://fa.wikipedia.org/wiki/%D9%88%DB%8C%DA%98%D9%87:%D9%85%D8%B4%D8%A7%D8%B1%DA%A9%D8%AA%E2%80%8C%D9%87%D8%A7/MahdiBot [06:28:44] what happened? did you lose its configuration file or something? [06:29:08] 25 05:59:02 < Mahdi> 23 oct I could login but now wikipedia says your password is incorrect and it can not reset my password! [06:29:22] sounds like he doesn't know what happened [06:29:40] i guess you could just set bot's email to the same as owner's email [06:30:00] is my link sufficient connection? [06:31:23] yes please set the botemail to owner email [06:31:25] Mahdi: when did you last change the bot's password? [06:32:12] 5 october i think [06:32:42] after http://meta.wikimedia.org/wiki/October_2013_private_data_security_issue [06:37:38] ok, you should have a password reset mail in your inbox [06:38:34] !log set email address for user MahdiBot to be the same as Mahdiz [06:38:57] Logged the message, Master [06:41:04] yes its work [06:41:05] thanks a lot [06:41:54] :) [06:42:09] no problem [06:42:12] woot [06:42:31] so, no clues how it got that way? [06:43:59] no [06:58:59] the 23th is when it created the account on loginwiki https://meta.wikimedia.org/wiki/Special:CentralAuth/MahdiBot [06:59:51] 23rd* [06:59:52] :P [07:00:08] it previously (2011) happened to me that I had to reconfirm email, presumably after logging in on a wiki for the first time; CentralAuth sometimes loses some data [07:00:29] yeah, that's because now I must run to a conference [07:01:01] run! [07:03:05] are the characters in my signature showing up garbled for anyone else when they look at the top section in https://www.wikidata.org/wiki/Wikidata:RFD ? [07:03:36] {{worksforme}} [07:03:51] unless [07:03:56] you're talking about that psi character [07:04:02] before your sig [07:04:21] yup [07:04:25] not a psi for me though [07:04:27] a hangul [07:04:46] characters removed [07:04:56] idk how they ended up there in the first palce [07:05:14] Jasper_Deng: WTF? [07:05:17] that could be a serious bug [07:05:22] reverted [07:06:14] probably isn't, of course [07:06:20] but give me a minute or two to investigate [07:08:09] okay. there. https://www.wikidata.org/w/index.php?title=Wikidata:Requests_for_deletions&diff=81298212&oldid=81298111 [07:08:22] sorry, Jasper, you were right :P [07:08:28] now... any idea why that happened? [07:08:30] * Jasper_Deng trouts Pink [07:08:35] :'c [07:08:46] this guy might've been editing from some weird encoding platform [07:09:05] in the sense that those bytes were switched [07:09:05] or that guy might just have pranky malware [07:10:44] https://www.wikidata.org/wiki/User_talk:RekishiEJ [07:22:23] * Jasper_Deng wonders why Pink rolled him back [07:22:30] (in the first place) [07:23:45] Jasper_Deng: because at the time i hadn't actually bothered to check that the code matched the display, and I *had* confirmed that I hadn't originally used that mojibake, so there was a minor possibility that there could be an actual rendering issue, and I didn't want to mess with the example of it [07:24:34] i just figure it's always better to leave things as they are until you can be sure of what caused the problem [09:31:10] is it possible for mediawiki to track access without the use of external tools? [09:31:19] such as which IP is reading what [09:34:34] ToAruShiroiNeko: http://www.mediawiki.org/wiki/Extension:Access_Log [09:34:53] thanks [09:35:42] does that also log the IPs? [09:36:17] not the IPs of the viewing users [09:36:26] probably needs checkuser extension then [09:36:37] Jasper_Deng ya I want to track the reader too [09:36:49] it tracks logged-out users [09:37:02] it would need some more code to make IPs available to CU [09:38:05] hmm [09:38:18] I suppose I am looking for https://www.mediawiki.org/wiki/Extension:UserPageViewTracker with IP tracking [09:39:18] for logged-in users CU only logs edits [09:50:28] hi guys. in monobook, the left menu is gone in the watchlist [09:51:40] witch wiki? [09:57:39] :nl [09:59:44] Z5: works for me. witch browser do you use? [10:00:46] Jasper_Deng that is true [10:00:53] hmm I dont think such a tool exists yet [10:01:38] which* [10:03:38] a tool to track viewer activity [10:23:58] mmmm. strange, Steinsplitter : i use firefox, also tested with chromium. [10:24:22] hmmm :/ [10:27:21] let me try refreshing the cache..... [10:28:01] it's back, Steinsplitter : probably a temporary glitch. thanks. [11:09:27] Hi, I visited https://commons.wikimedia.org/wiki/File:Islamic_compex_Shakhi_Zinda_-_13.JPG to move file, but it shows error and it says There is no file under the file name. what is this...? (have a related bug: [[bugzilla:53770]]) [11:31:14] hi. is it possible somehow to discover if user has changed account's email address recently ? [11:32:45] somebody like TimStarling should be definitely helpful *pinging* [11:34:02] jeremyb perhaps [11:34:17] reedy [11:56:06] it would be possible depending on binlogs and we would have to have a very good reason to do it [11:56:19] (private information) [12:09:29] apergos: became not actual. ruwiki user's account was under control or his wife's friend for few hours so there was possible need then [12:10:06] glad it worked out [14:06:53] Base: welp, not me. i could read the binlogs if i had them (i've done it before in other situations) but i don't have access to them [14:07:13] nor prod DB access for that matter :) [14:26:12] jeremyb: i was asking if it real at all :) hopefully we dont need to use the possibility [14:26:23] in the situation i mean [17:34:35] An error has occurred while searching: Pool queue is full [17:34:45] I just got that while trying to execute a search on enwiki [17:34:58] Transient, works now [17:42:31] FastLizard4: yes, SNAFU [17:53:56] We need a better search methods than using swimming pools [17:54:53] * jeremyb points Reedy at the clouds. aka Cirrus [17:57:16] <^d> New search also uses pool cool so we don't overload elastic :p [17:57:35] <^d> But yes, it's way nicer than the 4 (or 5?) search pools we have now. [17:57:41] <^d> *pool queue [17:57:54] <^d> wtf is a pool cool? [17:58:13] https://www.google.com/images?q=pool+cue [17:58:20] <^d> FastLizard4: Yeah, pool counter errors are basically almost always a transient thing though. Only time to be worried is if it doesn't disappear shortly. [17:58:34] <^d> *queue [17:58:41] <^d> Why am I having so much trouble with that word? [17:59:03] Mmm, ok [17:59:15] <^d> FastLizard4: The pool queue is used to keep the apaches from overloading other things, like parser processes or the search backend. [17:59:23] Because queue has more consecutive vowels in it than should be natural? :P [17:59:29] ^d: Ahh, makes sense [17:59:35] First time I've ever seen the error, though [17:59:43] <^d> You shouldn't most of the time. [17:59:46] So I went, "wait what?" [17:59:51] <^d> And when you do, it should almost always resolve shortly. [18:00:04] Oh yeah, I just bonked Search again [18:00:51] bonked? :) [18:01:03] <^d> I assumed bonked means clicked ;-) [18:01:08] Indeed [18:01:14] <^d> It would be way cooler if we had onBonk() though [18:01:21] Not to be confused with "blonk", which is the noise an IRC client makes when someone says your name :P [18:01:35] https://en.wiktionary.org/wiki/bonk#English [18:01:37] <^d> Mine's more of a "blunk" [18:01:54] FastLizard4: FastLizard4 FastLizard4 [18:02:03] To strike or collide with something. [18:02:05] To have sexual intercourse. [18:02:07] ^ Close enough [18:02:08] :p [18:02:24] Now, how do we go about proposing onBonk() as the standard? [18:02:42] onBonk(); createChild [18:02:52] wow [18:03:00] greg-g [18:03:01] wow [18:03:16] vatican approves [18:03:17] <^d> greg-g wins. [18:03:24] XD [18:03:29] Five points to greg-g [18:04:24] onBonk(protected); # returns null [18:05:18] heh [18:06:58] sorry, I'll stop [18:07:07] onBonk() { setTimeout(86400*273, deliver); } [18:07:31] Oh dear [18:07:37] (timeout varies with species. tweak as needed) [18:07:54] i wonder if gestation is in wikidata... [18:09:51] jeremyb: !!!!! that'd be an awesome bit of wikidata [18:11:07] reminds me of http://linux.about.com/od/funnymanpages/a/funman_baby.htm [18:11:23] yes! [18:11:27] jeremyb: property for species, yea, it should [18:11:53] mutante: how about for linux distros? or other software? :P [18:12:17] debian is ~1.7-2.3 years :P [18:12:25] hehe, could work with the same one, yea [18:13:24] jeremyb: https://www.wikidata.org/wiki/Wikidata:Property_creators [18:15:33] mutante: gah, that's work, i'd have to go look up the infobox param names! not now [18:25:00] are we still seeing weird cached redirects mutante ? or can we remove that from the /topic [18:25:26] Reedy: have you seen anything recently re cached redirects? [18:26:01] I think there was a couple of mentions [18:26:19] I seem to recall Elsie had commented on the bug again, maybe [18:26:21] * Reedy checks [18:27:28] greg-g: havent heard any more complaints. last time i checked the bug it was resolved [18:27:33] eh, where was the bug number again [18:27:42] https://bugzilla.wikimedia.org/show_bug.cgi?id=56006 [18:27:45] :) ok [18:27:57] I think after the api boxen were kicked that was mostly it [18:28:23] agrees [18:28:37] rock [18:28:41] ty [18:28:48] last one i fixed was like quality.wm wiki [18:28:52] heh [23:06:46] I think after the api boxen were kicked that was mostly it [23:06:51] What does that mean? [23:07:01] Meta-Wiki's API was returning 404s for me until it stopped. [23:22:42] Elsie: restarted [23:23:03] All the API boxes were restarted? [23:26:34] the apaches were, I believe [23:26:51] not an actual reboot, but a restart of apache [23:27:03] the apache-graceful-all didn't kick some of them hard enough, apparently [23:28:59] Elsie: it just means Apache restart, because the config was synced but not reloaded [23:29:07] that [23:29:23] mutante: What were the API boxes doing? [23:29:33] Not serving any requests or 404ing or ...? [23:29:52] 404 for api.php afair [23:30:02] because of the foundationredirect [23:30:21] * Elsie nods.