[01:23:39] hello, in a script I'm working on I'm loading the jStorage module with `mw.loader.load( 'jquery.jStorage' );`, however it appears sometimes the rest of the script runs before it finishes loading [01:23:49] according to the docs this should load synchronously [01:24:20] I tried wrapping my script in $(document).ready [01:28:28] Ummm [01:29:38] * T13|detached tries to remember if jStorage is still using localStorage which is unreliable because something is causing it to always be full. [01:29:51] I found it, I think it's mw.loader.using [01:30:09] but now I'm having different issues, possibly related [01:31:49] got it! that's one bug out of the way [01:32:24] Still haven't figured out the best way to handle removing the More (cactions) menu when there's no child elements. The setTimeout solution could work but seems so hacky [01:37:09] setTimeout doesn't work... [01:37:44] I'd just absorb the section. [01:38:57] what do you mean by absorb? [01:39:39] Suck it into moremenus [01:40:30] Basically replace 'more' with 'page' [01:40:58] ahh okay, so not make a "submenu" called More under Page [01:41:10] Then have 'more' be an element of 'page' [01:41:20] so do make it a submenu [01:41:27] Yes [01:41:57] yeah, that I could do, if I kept the same cactions ID the mw.util.addPortletLink should work [01:42:24] But have a function tied to 'page' so it checks if 'more' has any elements on mouseover of page via function [01:43:13] If there is no elements for it, hide it if shown, if it's hidden and something gets added, then show. [01:43:41] yeah I gotcha, that would work, but it just seems unfair to takeover other scripts' links, embedding them in mine [01:44:06] But you're not really. [01:44:06] and what if the links have nothing to do with the "Page", then it's just counterintuitive [01:45:05] If they have nothing to do with the page, they shouldn't be in p-catction (page-clickActions) [01:45:13] true [01:45:43] Those scripts should add their links to ptoolbar or ptb [01:47:44] alright I'll give it a go :) [15:49:20] andre__: Hi [15:49:29] andre__: What should I do for https://phabricator.wikimedia.org/T57503 ? [15:50:53] apergos: ^ [15:51:19] hmm. I wonder if Ariel was the default assignee in Bugzilla. Which is a horrible concept [15:51:39] because it gives you that long list of things and you cannot use the tool anymore to see what you /really/ plan to work on [15:51:45] but yeah, hoo pinged. thanks. :) [15:51:54] andre__: I think he was, I probably have assigned the ticket to him personaly. [15:52:00] how much space are we talkign about? [15:52:00] and that ticket is "Mirror more Kiwix downloads directories" for anybody wondering here. [15:52:41] Kelson: [15:52:47] andre__: I wonder why this looks to be a long fight to have this [15:53:02] Kelson, I don't see any traces of a fight? [15:53:49] it's just that some not-high-priority stuff sometimes falls through the cracks I'm afraid. And I don't know how 'religiously' floks check their task notifications [15:54:35] apergos: [OT] if you feel like going through tickets assigned to you on https://phabricator.wikimedia.org/maniphest/ and unassigning what you do not plan to work on (e.g. stuff just assigned to you because of stupid default assignees in Bugzilla), that might make sense if you want to be able to use Phab as a planning tool. just saying :) [15:56:29] andre__: "fight" in French sense [15:56:37] (and Italian) [15:56:39] apergos: Hi [15:56:47] haha [15:56:59] apergos: I just have sent you an email with the mass storage usage per project [15:58:03] andre__: I mean going forward looks to be difficult (at least for me) ... although this is a pretty trivial problem. [15:58:39] andre__: but "fight" is too much... [16:01:59] andre__: apergos: we currently working on a solution (with wmflabs) to create, each month, new version of all our project. This should be ready in the next month. So next step is to prepare a nice page summarize everything (for example @http://dumps.wikimedia.org/kiwix/) [16:02:28] andre__: apergos : but to do that we need to have the snapshots available [16:03:48] ok. I just need an estimate of the total space, so I can make sure we have or can get capacity in a timely fashion [16:05:06] ok, thanks for that email [16:05:13] how many snapshots would you want us to keep? [16:05:17] apergos: it's moving but we talk about ~2.5 TB [16:05:21] yeah [16:05:27] so we need to get more storage for that [16:05:47] it's a fine thing anyways, we need it generally [16:06:55] apergos: I don't plan to keep trace of old snapshots - so don't keep more than one "old" snapshot to let the started downloads finish correctly and then delete them [16:07:30] right [16:07:57] well we won't get 3t of more storage, we'll get a chunk, if I have anything to say about it that is [16:08:35] apergos: for now, http://dumps.wikimedia.org/kiwix is a "slave" of http://download.kiwix.org... but if everything works well... we might think to change the way it works. The master being then download.wikimedia.org [16:08:43] I wanna chat with robh about it, there's two approaches we can take, but he's the proudement dude [16:09:06] *procurement [16:09:53] apergos: might you at least for now change "0.9" for "wikipedia"? this is "only" 640 GB. [16:09:56] ?\ [16:10:06] sec [16:10:50] yes I can do that but anything after that absolutely must have more storage [16:11:55] apergos: Thank you, this sounds good to me. We work anyway on the long term here... so it's important that everyone is agree & we have substainable solutions [16:13:34] do you have any links pointing to the 0l9 directory someplace? [16:13:53] 0.9 [16:13:57] I mean to our copy of it [16:16:55] Kelson: [16:18:05] apergos: something like this? http://download.kiwix.org/zim/ [16:18:52] apergos: or you mean pointing to own of the zim files in http://dumps.wikimedia.org/kiwix/zim/0.9/ ? [16:19:50] apergos: If this is the question, the answer is no. http://download.kiwix.org works as a "gateway". All links point to http://download.kiwix.org which redirects to one of the mirrors. [16:20:25] apergos: on time per hour, all mirror are checked so see if they are still online... Anyway "0.9" contains now almost only deprecated content [16:20:35] I mean pointint to 0.9 or into it [16:20:40] ok great [16:20:56] cause I will not be keeping it around [16:22:21] apergos: of course [16:22:45] hm here's an rsync I don't bw limit. maybe I should [16:26:14] apergos: we have pretty much bandwidth on that server, so you don't need to limit it too much. [16:26:29] well I o it on our en to save our server :-D [16:26:31] *end [16:26:34] *do [16:26:37] *sheesh typos [16:28:04] apergos: ah ok :) [16:28:31] ok that's set and I'll look at it later on to see if it's happening [16:28:38] doesn't matter if it takes days for the first sync up [16:28:45] apergos: great. Merci. [16:28:50] sure thing [17:50:50] hi guys, I have a question [17:52:01] Base: go ahead and ask it please, people will answer if they can. [17:52:04] !ask [17:52:13] .... where's the bot? :) [17:52:53] Base, don't ask to ask, just ask. [17:53:25] oh, there's the bot [17:54:59] legoktm: Error: There's the bot is not a valid command [17:55:01] ;) [17:55:22] when a new namespace is added to a wiki it is known that pages which had been in a preudonamespace with the same name (i mean where they are in ns0 but prefixed with new namespace's prefix). the same goes for a new alias or for a new interwiki prefix. it's known to be fixed by moving pages by id via api or via some maintenance script. The question is are some similar troubles to be expected when enabling subpages support for a namespace which [17:55:23] already has pages with / in names? (but which are not considered subpages atm 'cause they are disabled for the ns) [17:56:08] ah i didnt finish first sentence [17:56:30] ... same name (i mean where they are in ns0 but prefixed with new namespace's prefix) become trapped. [17:56:34] in ns0 [17:57:45] base there is a maintenance script to fix that [17:59:34] Base: namespaceDupes.php [17:59:51] Base: no, enabling subpages doesn't cause this kind of issues. [18:00:54] MatmaRex: so MW'll just understand that these pages are subpages since the moment of enabling and all'll work ok? that sounds good, thanks :) [18:02:24] well yeah but the devs never remember to run it [18:02:31] thus e.g. the last records in https://ru.wikipedia.org/w/index.php?title=Служебная:Журналы&offset=20130101000000&limit=50&type=move&user=Base&page=&year=2012 [18:02:44] Base: yes, some things might get updated only after pages are purged, but nothing will be broken [18:02:57] Base: thats not the issue [18:03:12] Base: let me grab the ticket [18:03:27] Base: there's an ongoing problem with pages being in wrong namespaces on wikimedia wikis, apparently. not related to new namespaces being added. [18:03:59] Hi guys, I was suggested here by someone from the #en-help site. [18:04:01] well that log I showed it from back when d: was added) it's fixed now [18:04:24] Base: https://phabricator.wikimedia.org/T87645 [18:04:26] I think the statistics of this page is not correct: http://stats.grok.se/en/latest90/Relapsing_polychondritis [18:04:37] It seems that it is missing days, and also it is not up to date [18:04:48] *are not correct [18:05:34] Don't really know how to fix it, so I was hoping someone could have a look at it. [18:05:50] Betacommand: oh wow so much [18:07:10] Ellen: it's currently a bit behind, see https://lists.wikimedia.org/pipermail/analytics/2015-February/003342.html [18:08:21] legoktm, ohh ok :-) I will just wait for it. thank you! [18:09:40] in which file are extension Translate's configs for wikis? [18:16:15] Base: https://noc.wikimedia.org/conf/ InitialiseSettings.php and CommonSettings.php [18:20:38] Betacommand, yeah IIRC the database knows nothing about subpages... [18:21:07] using subpages in a namespace that does not support it does not magically put the page in the main namespace despite it's title [18:45:04] legoktm: mmm. is it possible to enable it in a wiki with another sourcelanguage than English? I heard claims that it's possible but e.g. by the look of $wgTranslateBlacklist it doesnt seem so [18:45:47] Base: I'm not really familiar with Translate, so I don't know [19:16:25] Nemo_bis: perhaps you know something? and btw what's current twn's irc? [19:22:34] Base: #mediawiki-i18n [19:31:34] hello [19:33:02] hi [19:40:48] (Yes, any source language is fine) [19:48:18] How does the foundation protect against ZSS? [19:48:46] https://en.wikipedia.org/wiki/ZSS ? [19:49:29] legoktm: no, http://www.zerma.com/en/zss-standard-shredders.html [19:51:01] Sorry, XSS [19:51:39] uamaol: Not sure what you mean.... you mean in MediaWiki? [19:52:03] www.enwp.org/Cross-site_scripting [19:52:05] https://www.mediawiki.org/wiki/Cross-site_scripting has some details [19:52:57] I really need to update that page... [19:53:07] I was just in #wiki-help-en and i was told to change my skin. [19:53:29] you can add scripts and css rules to pages. surely enough this must have limitations. [19:54:05] You can add any scripts to your own account.. it has no effect on other users [19:54:23] But no, you can't add scripts to any page [19:54:35] CSS is filtered heavily [19:55:30] How about JS limiations? [19:55:38] like chanign styles? [19:56:05] uamaol: try! [19:56:09] uamaol: There are no limits on the scripts you add to your own account-- that only affects you, so you're free to do what you like with it [19:56:22] That's hilarious [19:56:45] it's practically impossible to sandbox javascript in a manner that leaves javascript both (a) useful, (b) secure [19:57:22] admins and various other users can change your JS though [19:57:49] they're trustworthy, hopefully [19:59:13] I'm aware it is just myself that would be affected by such a change [19:59:47] But I was thinking this laid back attitude must surely give room for abuse. [20:00:24] see also: wikis [20:00:55] uamaol: There are a few potential issues, but the value to power users to script common stuff seems to be worth it to most people. [20:01:48] Fair enough. [20:02:22] So I'm assuming this is practically self governed then? [20:03:12] unless someone breaks their own account, then they can ask an admin to fix it for them. Yeah. [20:05:02] crickey [20:05:25] CSS-changing JS works. [20:06:14] or turn off their JS and fix it [20:07:56] Was I just in here? [20:08:07] yes uamaol [20:08:10] * uamaol has quit (Quit: Page closed) [20:08:22] cheers [20:11:57] Just checking so I can save this in my bookmark [20:12:18] , concatenates channels in urls :o [20:57:33] ^mass purge or idlers? [20:57:52] net problems [20:57:53] ? [20:58:11] or purge [20:58:16] whatever works for you