[01:25:00] I created a configuration template for MediaWiki in case anyone's interested: https://kj7rrv.com/user-configuration-template-for-mediawiki-wl4x [02:58:22] wow, what a great way to destroy MW's caching mechanisms [04:55:37] Dinoguy1000: oh yeah I hadn't thought of the effect on cache [04:57:21] It shouldn't have more of an effect than any other use of parser functions though? [05:00:52] kj7rrv[m]: it will mean every page view needs to re-parse the page (and all templates the page uses). Which means both more CPU usage per page view as well as longer load times for all impacted pages [05:01:09] normal parser functions play nicely with the parser cache -- the page is parsed once (on edit) and the cached version is then used for every view [05:19:39] "normal parser functions play..." <- Oh so the problem is using the username one? [05:19:47] Maybe I'll figure out a way to do it with JavaScript instead? [05:21:08] Or maybe I'll just try to reduce the use of the config template [05:28:40] yup, the problem is the username function (or any other extension that lets you vary page content based on the user viewing the page) [05:29:33] That makes sense [05:29:49] The time template isn't really necessary [05:30:00] Hiding or showing net scripts could be done with CSS for user groups [05:30:14] Auto filling names and call signs could be done in JS [05:30:37] I think that's all the config template is used for [05:30:45] Although keeping it on net pages would only affect two, and it might be worth it on those two pages [15:38:46] it's definitely possible with JS - both getting the username of whoever's currently looking at a page, and varying date/time/etc. according to their preferences (though the latter will require saving those preferences somewhere still) [17:36:51] I haven't followed this whole thread, but date formatting is a user preference in MediaWiki under 'Appearance' ref. https://www.mediawiki.org/wiki/Help:Preferences#Date_format_and_time_offset [17:40:16] 12 vs 24 hour time display isn't, though, and that's the main use case kj has presented so far, from what I've seen [17:40:38] the "date and time" in my comment was me typing on autopilot [18:42:08] I could put configuration changes in user JavaScript [19:56:58] "I created a Mastodon account for..." <- Next step, mediawiki federates with mastodon instances 😁 [21:30:37] does Common.css get fed through CSSJanus? [22:19:45] I believe so [22:19:56] https://en.wikipedia.org/w/load.php?lang=ar&modules=site.styles&only=styles&skin=timeless [22:20:06] is different from https://en.wikipedia.org/w/load.php?lang=en&modules=site.styles&only=styles&skin=timeless [22:20:16] plus https://en.wikipedia.org/wiki/MediaWiki:Common.css has /* @noflip */ comments [22:20:41] Izno: ^ [22:20:45] I assume nothing about what en.wp is doing :) [22:22:16] the lines of interest there could as easily be there as mistakes, or as requests from elsewhere to be nice for internationalization [22:22:28] but the former comment does seem to demonstrate it [22:22:54] https://phabricator.wikimedia.org/P45877