[03:52:02] I'm using Docker on an ARM64 system (Raspberry Pi), but it seems like I can't get Lua to exec. [03:52:26] And now I'm getting fatal "MWException" errors [03:54:18] Helmet[m]: I don't think we ship with lua compiled for arm64, you would need to install lua on the system (e.g. apt install it, or compile it yourself. However do note you need to use lua 5.1.x not newer) [03:54:58] bawolff: Yeah. I apt installed in the container [03:55:21] Then just set $wgScribuntoEngineConf['luaPath'] to the binary [03:56:05] bawolff: Seems to be working. I'm trying to figure out the infoboxes now, but maybe I don't have the right template imported. [03:56:16] I only imported the base Template:Infobox from Wikipedia [03:56:29] "I'm following this https://www...." <- As per the guide. [03:56:42] Importing templates from wikipedia is a giant pain in the ass [03:57:23] especially now that everything is depending on wikidata, and there's not a good answer for doing that locally [03:57:32] It's late, honestly I might try another day. [03:57:42] Is there an easy way to do infoboxes locally? [03:57:58] What are you trying to accomplish? [03:58:07] I mean, I'm just trying to use it like a personal notebook really. [03:58:26] Ah ok, in that case it might be easier to just make your own templates [03:58:55] bawolff: Okay. I'll look into that sometime. [03:59:09] Infoboxes at there core are just

Some text here

[04:00:00] alternatively, sometimes it works better to import templates from smaller wikis because they are less complex. english wikipedia tends to make super fancy templates [04:00:25] Looks like it broke again. [04:01:08] * ~~Looks like it broke again.~~ [04:01:14] * Looks like it broke again. [04:01:17] This is a bit of a controversial opinion, but personally I sometimes think its simpler to just install mediawiki directly instead of using docker [04:01:55] Yeah, with all the addons and stuff, you might be right. [04:02:09] I fixed it by disabling the my addons for now. [04:02:23] Or, if you're not planning to do dev stuff with mediawiki, and are using something debian based, apt install mediawiki [04:02:36] I'm not currently using Scribunto or TemplateStyles so I turned them off. [04:03:24] bawolff: I'm really just fiddling around with home server stuff. I'll try different projects and stuff. [04:03:42] Cool cool [04:04:00] I thought MediaWiki would be a good place for writing down things and documenting as I went through my struggles in self hosting as well as switching to Linux. [04:04:18] Though I could also do Markdown files on Nextcloud 🤔 [04:04:32] But I figured it could have a little more expansion and images and stuff. [04:04:56] I did not know how complicated having a wiki could be. [04:04:56] Right now is the start of intern (gsoc) season, so there are a lot of people who are hopeful to be chosen running around trying to install mediawiki, so some people might assume you're with them and give advice that's more suitable for if you want to be a mediawiki developer than if you want to just use it [04:05:32] I see. [04:05:36] Helmet[m]: Another cool project for making a personal notes wiki is https://tiddlywiki.com/ [04:05:59] I mean, if y'all want to give me a job 🤷‍♂️ [04:06:46] Helmet[m]: By all means if you are interested I encourage you to apply - https://www.mediawiki.org/wiki/Google_Summer_of_Code/Participants [04:08:34] It was how i got my start way back in 2010 [04:10:01] bawolff: Hm. Looks interesting. [04:10:11] Perhaps less daunting than Mediawiki? [04:10:52] possibly less daunting than trying to import a template from english wikipedia ;) [04:11:42] bawolff: I'm sure I could figure it out, I just need to let it cook for a while. 🧠🍳 [04:12:34] English wikipedians just built and built and built on their templates, to the point where copying them is now is basically a herculean task [04:14:43] hey, you could do a gsoc project around making it easy to import templates ;) [04:18:10] bawolff: I'll make a simple template wiki 😆 [04:18:15] Full of templates for self hosters like me [04:18:37] One issue with enwiki templates is that they tend to have huge dependency chains which you'll need to trace manually because recursive export is based on link tables, and link tables only record live branches. The other issue is that chances are your server just won't be able to render them with a reasonable performance. [04:20:35] I've often thought having a mediawiki extension that is basically just a bundle of useful templates, would be a useful thing [04:21:01] I guess I just thought it was base Wikicode stuff. Like you'd just put a {{infobox }} block and it would appear. [04:21:23] I thought it would be built in, as much as they're used. [04:21:57] Anyway it's late. I'm logging off for the night. Thanks for your help [04:22:23] It does make sense to assume that. The contrived divide where templates are user content and not "software" is one of the bigger failings of mediawiki as an indepent software package imo [04:22:42] That would be Page Exchange, I think? [04:23:32] oh cool. I did not know that existed [05:32:40] Anybody can help me with mediawiki local intallation with docker?? [07:08:31] Ayush: You forgot the wait 6 hours to see if anyone responds part of irc culture :) [07:09:01] Not that you can see this now, but generally speaking, just ask your question, its unlikely people will respond without knowing what the issue is [09:18:35] Well that's what happens kinda... (full message at ) [09:22:06] can anyone help me how wikimedia decode the url ?? [09:22:07] for example : if URL is /wiki/Special:Nearby#/page/Lübeck [09:22:07] is it by using the function decodeURI ?? [09:22:33] Here url need to be decode as it contain Non-Ascii character [10:34:36] can anyone help me with this... [10:46:16] Nikhil61: I recommend submitting your patch with the function you think it's the most suitable. If the reviewer thinks otherwise, they'll let you know in the review process [10:50:05] where should i do further communication with reviewer at phabaricator or gerrit if they have suggest me some changes in patch?? [11:44:17] is there an easy way to search the source of pages? e.g. find all pages containing the code "{{blah}}"? I know about "What links here" but that also includes indirect transclusion, like if a page uses {{blubber}} which in its source uses {{blah}}. [11:49:13] Nikhil61: Code review happens on gerrit. See for example: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/883588 . Reviewers will comment there (once you upload your patch) if your patch needs some improvement [11:49:43] The default search does that [11:49:43] Though not too well [11:50:42] Nikhil61: did you read my previous message before you left? [11:51:16] You can also use categories to mark pages using certain template [11:51:33] yaa i read [11:51:34] thanks for replying [11:52:13] taylan: If you have CirrusSearch, you can use the insource: modifier to search for wikitext code instead of rendered contents. Although searching for special characters like { can be tricky [13:59:10] Hello! I'm rewriting my LocalSettings.php to simplify the organization. Is there a performance penalty in splitting it over multiple php files and including the other php files in the main LocalSettings.php using PHP include()/require()? [14:03:00] @auxfree no, that's sort of how wmf's config works as well. [14:04:40] Okay, thanks! Is there some place I can learn how this is optimized? Like how it would cache and detect if I change anything in these files? [14:11:04] auxfree: i believe that would be done by php's opcache, although i don't know the details of how it works [14:11:20] but "php opcache" is the term to search to learn more [14:11:55] Okay, I will look into it. Thanks for the direction! [14:56:43] good morning everyone, does any one know how to disable the message "The page has been created" on 1.39 after a new page is created? [15:14:33] @paulx the toast popup ? [15:14:54] or an inline message at the top of the page ? [15:27:17] how can I make a pull request on an extension? in particular, the Theme extension, to which I had contributed vector/dark-grey. I've made a lot of improvements recently and would like to contribute them to upstream. [15:28:03] it's on Gerrit, I should mention [15:28:25] https://www.mediawiki.org/wiki/Gerrit/Tutorial/tl;dr [16:35:09] Why does Wikimedia stats show 0 for unique devices? [16:35:12] https://stats.wikimedia.org/#/en.wikipedia.org [16:55:24] noone is reading right now [17:14:03] OriginalAuthorit: my educated guess is that the data for January has not been exported yet. [20:03:55] can the username of my Wikimedia developer account be changed? I.e., my user on https://wikitech.wikimedia.org [20:06:47] Hello, I am Pradnya Shimpi, a sophomore at IIT Roorkee. I want to contribute to Wikimedia, how can I get some issue assigned [20:07:35] taylan: at the moment, we are unable to rename developer accounts [20:07:45] Pradnya: Is there any task you are interested in in particular? [20:07:50] p858snake: alright, thanks [20:08:09] Pradnya: You don't need permission to start working on something, you can assign something to yourself if you're interested in working on it [20:08:38] I haven't gone through the tasks list yet, do you have any suggestions? [20:08:40] taylan: Of course, you can just make a second account if you want [20:09:03] bawolff: I'd like to keep the shell account name that I chose [20:09:13] I'll live with the sub-optimal username ^^ [20:09:14] Pradnya: What are your interests, and how good are you in various technologies like php, js, etc [20:09:29] taylan: Almost nobody notices the real username anyways [20:09:59] the little things bother me way too much sometimes :) [20:10:12] At the time I was convinced to use "Brian Wolff" as my wikitech username, and have regreted that it is not consistent ever since (Back in the day, there was a brief period where there was a push for people to use real names) [20:11:38] bawolff I am fairly comfortable with php, js, python etc. I have worked on multiple projects in js and python [20:14:47] Pradnya: Do you want to make some selenium tests? https://phabricator.wikimedia.org/T321935 is available [20:15:27] Pradnya: But there is a long list at https://phabricator.wikimedia.org/maniphest/query/jsySdXllltwv/#R feel free to pick whatever looks interesting to you [20:43:35] after "git review" succeeded, will my patch be looked into automatically? through what channel do I get feedback if needed? [20:45:08] I wish my patches were looked at automatically ;) [20:45:22] taylan: There should be a link to the Gerrit change in your console log after git review, you will get feedbacks from there [20:45:23] taylan: Generally speaking, feedback will come on gerrit.wikimedia.org [20:46:09] taylan: In gerrit there is a button where you can add people as reviewers to your patch. Generally its a good idea to add about 2 people who would be familiar with the area your code is in [20:46:33] If developers comments on the bug your patch is for, they are good candidates to add [20:47:02] if your not sure from the bug report who to add, git log from the file you edited can help you find good candidates [20:47:22] This tends to be more important for complex patches where not everyone knows enough about the area to meaningfully review it [20:47:24] I see. Found the link. If only I could remember the name of the friendly person who accepted my previous contributions to the Theme extension... (They had added them manually.) [20:47:55] Theme would probably be ashley (Jack Phoneix) [20:48:38] I do seem to remember that it was a feminine name so that could be it... [20:51:20] what does the "Resolved" checkbox while composing a message do? [20:51:36] It marks it as no longer an "issue" [20:51:56] e.g. If you were commenting to say that something is wrong with the patch, you would check resolved if the issue was fixed [20:52:18] If your comment is not an issue with the patch, generally you would check the resolved checkbox immediately [20:52:33] ah ok. it was already checked and I leaved it like that. [20:56:23] So shall I set it up on windows or is Linux recommended ? [20:56:54] I have wsl but I can always dual boot as well [20:57:10] Pradnya: I reccomend linux if you have access to both [20:57:17] Most instructions are written with linux in mind [20:57:24] And most things are tested on linux [20:57:32] WSL is also not recommended? [20:57:55] You can certainly do stuff on windows, but you might have to figure out some parts yourself and it isn't as well tested [20:58:07] I've never used WSL so not really sure [20:58:36] But I'd put it in the same category as windows in general - in theory it should be fine, in practise nobody is really testing it so ymmv [20:59:04] bawolff: have you met MatmaRex [20:59:51] Pradnya: So if you are doing that task, in phabricator click the "Assign/Claim" choice from the add action dropdown to mark yourself as working on it [21:00:04] Reedy: Does MatmaRex still use windows! [21:00:07] Such a sadist [21:00:08] :o [21:00:35] bawolff Okay ig I'll use Linux, ubuntu 20.04 should work or shall I just go for 22.04 [21:00:44] either version is fine [21:00:45] i work on windows, but i run the code in a linux virtual machine [21:01:17] I think i recall paladox mentioning something about using WSL [21:01:36] MatmaRex something like WSL? [21:01:42] haven't used WSL in many years [21:01:53] moved to a mac in 2016 :P [21:02:37] Pradnya: no, just a boring old virtual machine (using VirtualBox). i think i started before they invented WSL, and then i didn't have any reason to switch, but WSL might even work better [21:03:10] Ig I'll just take the safe path and set it up on ubuntu [21:03:10] I suppose people using docker, docker works on windows [22:28:16] taylan: wonderful patch, great job, happy to +2 that :D (and oh boy, I sure wish there was a theme-specific equivalent to $wgResourceModuleSkinStyles[] so that you could target e.g. precise OOUI or WikiEditor RL modules instead of having one giant .css file that gets applied on all page loads, but...it is what it is, we gotta live with the status quo, alas) [22:30:18] heya :) thanks for the kind words. yeah, the CSS is kind of terrible sadly, I hope there will be better theming options one day... [22:40:14] there's https://phabricator.wikimedia.org/T122924 / https://gerrit.wikimedia.org/r/c/mediawiki/core/+/465451 , but from what I understood back then, there wasn't much...political buy-in into a new feature that's primarily of interest to third-party MW instances; code-wise, I expect that while the patchset does need some manual love (E:Theme has changed a bit since 2019, Fomafix has done nice job on it!), it should still be doable: alas, we probably can't [22:40:14] have something like $wgResourceModuleSkinStyles[][] (that's https://phabricator.wikimedia.org/T183444 btw) before Theme is in core since it'd have to integrate super-tightly with RL... [23:06:06] Izno[m]: How you do personally feel an abuse filter with a warning action to dissuade inline styling? [23:06:37] you'd have to disable it on all talk and potentially-talk namespaces [23:06:53] else the custom sig folks will murder you [23:07:07] That's fine by me [23:07:12] Yeah, I don't think that's feasible. [23:07:41] And there is plenty of inline styling which for your use case is benign. [23:07:58] Almost everything in CSS basically. [23:09:31] AntiComposite: I will quickly change my sig to use [23:10:31] Oh, hey, there's something we can get consensus to ban though probably. [23:10:35] 🙂 [23:10:37] fun fact: nope [23:11:16] it was supposed to be added to the validator, but got nix'd because people complained non-deprecated markup was longer and would make their sigs hit the character limit [23:11:45] What a shame :P [23:11:55] ~~~~ [23:12:10] There hasn't been an actual consensus discussion it, but someone or another made a config variable for it. [23:13:07] @Izno[m] okay what about a warning only for color and background-colour attributes? [23:13:20] i did :) [23:14:28] (i wrote a validator for signatures for the talk pages work like two years ago, but it's been only enabled in warning mode ever since. someone could start a discussion somewhere to enable it for real, you know) [23:15:28] it is set to enforce, but only against new signatures [23:15:32] Yeah, was pretty sure that was you but it's long enough ago that I didn't want to assign credit. [23:15:50] nobody ever got around to figuring out what to do with unchanged old bad signatures [23:15:55] Seddon, maybe. [23:16:52] Izno[m]: Do the communities have a consistent means of styling tables with template styles? [23:21:18] And by consistent I mean, some nascent but acceptable means [23:21:32] Also, IDK if the edit filters would pick up on transcluded content having inline colors (that would be another thing to dodge). [23:22:02] Pretty sure they don't. [23:23:20] Now, back to my Korra binge. [23:50:01] Has anyone found a way to disable the god awful MobileFrontend editor? [23:50:01] I looked into the extension code but it was not enough for me to figure out how to prevent it from loading [23:50:53] I did manage to kill it but my method is far from being good lol [23:52:02] Archimedes1560[m: Have you tried removing the line "wfLoadExtension('MobileFrontend')" from LocalSettings.php :P [23:52:18] * Platonides was thinking the same thing xD [23:52:44] If for some reason you like the general style of MobileFrontend, you could still use the minerva skin [23:53:17] Hold up, let me hack the sysadmin first