[01:12:02] Gloria: should ori make a locale that sorts his way? :) [01:12:11] Yes! [01:12:31] LC_ALL=en-ori sort [07:49:31] doublewiki links disappeared near wikisource interwiki. Anybody knows of it? Or --> bugzilla ? [07:56:36] ankry: probably doublewiki is not compatible with wikidata links? [07:57:10] file in bugzilla if not present yet (doublewiki component but cc wikidata-bugs) and link in wikidata-l [09:23:25] Hello. There is some problems on [[en:List of PlayStation 3 games]] - templates after the "Viking: Battle for Asgard" entry are broken (only showing a link to the template page) [09:23:44] The HTML source of the generated page also shows [09:25:25] Somebody might comment on its Talk page? [09:25:50] What's more, the time usage from the NewPP limit reports shows monstrous 49.997 seconds (Real time usage). There are tons of templates on the page and that's probably the reason. Is there a way to fix this? [09:26:02] * Zhaofeng_Li checks for comments [09:27:21] There are no comments about it on the talk page, and I don't think administrators can fix this - it's a server restriction. [10:55:32] Zhaofeng_Li, this page is a great example of something that should not be, categories are more appropriate for such number of items [10:57:06] MaxSem, yup, I notice it's in [[Category:Pages where template include size is exceeded]]. [10:58:18] The problem needs to be fixed by splitting it into smaller lists, however. Is there a bot that can do this automatically, or is some manual labour required? [10:59:17] so server admins can't help you - while we theoretically can raise the limits it will simply reduce user experience due to awful performance [10:59:51] I'd say delete it, not split:P [20:16:35] who's running the typography program / where does one report issues ? [20:16:55] jdlrobson might know [20:16:58] NotASpy: the beta features time [20:17:05] *team [20:17:18] what is going on with typing tonight? [20:17:29] tonithg* [20:17:53] just helped an editor running Chrome 31.0.1650.63 m who was complaining about "all the content is on the left side of the screen" [20:18:10] Chrome 31?! [20:18:22] twkozlowski: there is 32 already [20:18:43] NotASpy: let him read an RTL wiki, it will solve the problem [20:18:56] * twkozlowski pats his SeaMonkey 2.22 [20:19:14] they've gone now, just sort of passing on what they were telling us in the help channel [20:23:23] NotASpy: this was already discussed like 5 times [20:23:47] NotASpy: the "official position" is that changes will be considered on next experiment iteration (in a few weeks probably) [20:24:07] everybody's else's unofficial opinion is that this was a really bad idea [20:24:40] isn't betafeatures opt-in? [20:24:54] NotASpy: there's a thread on the betafeature talk page on mw.org and a wontfix bug somewhere [20:24:55] Yes. [20:25:09] i don't see the issue, then [20:25:09] ori: yeah, but an existing betafeature was retrofitted with some weird stuff [20:25:30] that's kind of what I'm wondering. I'm guessing there's a few inexperienced editors going around enabling features and running into problems with layout and stuff. [20:25:33] well, it's called "beta features" [20:25:36] and, since the stuff is completely unrelated to the name, everybody and their dog is confused where it comes from [20:25:55] i think everyone just disabled the feature already, heh [20:25:58] maybe that's the real bug [20:26:09] i had to explain wtf is going on to ~5 people myself [20:26:10] https://bugzilla.wikimedia.org/show_bug.cgi?id=59815 [20:26:12] (so far) [20:26:16] implement a mean for betafeatures to discretely signal new changes [20:26:37] maybe some visual annotation on the betafeatures link [20:27:26] maybe [20:28:07] we should do a wikiBBS clone [20:28:20] without commenting on that particular change, it seems plausible that some visual changes are desirable overall but take some getting use to, by dint of changing some essential property of a very familiar interface [20:28:45] an opt-in beta features component seems like the way to test that without forcing it on all users [20:28:51] James_F would be the lead, harder to do than VE [20:29:11] errm wut [20:29:22] !b 59815 is a WONTFIX? [20:29:22] https://bugzilla.wikimedia.org/59815 [20:29:37] yes [20:29:37] "Sure, we know this breaks shit, but we won't fix it." is my first impression without reading the bug yet [20:33:59] Well, I can tell you one thing [20:34:13] If this won't get fixed, people will simply disable Beta Features and you'll get no feedback at all. [20:34:16] Why bother. [20:35:11] no feedback == no bugs. software works! [20:36:53] OK, now I read the bug and the feedback on MW.org [20:37:13] People /have/ disabled Beta Features already, and you /will/ get no feedback at all. Thank you for listening. [21:42:44] twkozlowski: there is 32 already [21:42:47] 32? hahahaha. [21:43:06] (<- 33) [21:43:12] ? [21:43:30] chrome? [21:43:52] yes [21:56:14] NotASpy: https://www.mediawiki.org/wiki/Talk:Typography_Update [21:56:27] NotASpy: Although the narrow page issue has been captured numerous times ;-) [22:11:07] thanks, jdlrobson [23:04:45] Just asking: What's up with icinga for us normal folks, any reason for httpauth? btw: today browsing in wp felt a bit slow and just saw that: http://ganglia.wikimedia.org/latest/?c=Text%20caches%20eqiad&h=cp1066.eqiad.wmnet&m=cpu_report&r=day&s=by%20name&hc=4&mc=2 related? [23:05:59] all text caches seems to be busy atm, interesting [23:12:34] se4598: haven't seen that/heard about it, I'm checking [23:13:05] se4598: use icinga without https [23:15:56] matanya: i kept redirected to https [23:16:14] se4598: using httpseverywhere? [23:17:11] matanya: no, even the not used IE does this [23:17:29] hmm, i'll have a look [23:20:06] se4598: it used to work, file a bug [23:20:20] se4598: e.g. [23:20:21] https://bugzilla.wikimedia.org/show_bug.cgi?id=54713