[01:51:50] <PixDeVl>	 btw @orduin once/if my PR to CW get's merged do you want me to add the config to https://www.mediawiki.org/wiki/Extension:CreateWiki. I'm thinking now if any other parts need lots of updates. The table schema haven't been changed since 2020 I think but idk how much they changed in the codebase itself. OS seems to be keeping it updated with the new
[01:51:51] <PixDeVl>	 WIP API
[01:52:52] <PixDeVl>	 not a ton of people use CW outside of us so not a big deal but can't hurt to stay up to date on docs, even if it's just to leave a good impression on the recent changes watchers lol
[03:14:26] <MirahezeRelay>	 <.guardianx.> [1/6] Good evening, new to having this much control in a wiki, mainly did things in managed wiki's. Likely going to mess up the language so forgive me please LOL.
[03:14:26] <MirahezeRelay>	 <.guardianx.> [2/6] I'm looking to make a fairly large table and then parse that table out into various pages based on a filter, the reason for the main table is to have a goal of users form editing the table.
[03:14:27] <MirahezeRelay>	 <.guardianx.> [3/6] Is there a best practice for this?
[03:14:27] <MirahezeRelay>	 <.guardianx.> [4/6] Debating using an array, but I don't know much about them and am in the process of learning.
[03:14:27] <MirahezeRelay>	 <.guardianx.> [5/6] filtering a large table into smaller tables seems to require some extensions I don't know if I really need.
[03:14:28] <MirahezeRelay>	 <.guardianx.> [6/6] Any suggestions more than welcome.
[04:43:35] <MirahezeRelay>	 <m3w, replying to .guardianx.> create a template and make the table using wikitext, protect the template, insert the template
[04:43:44] <MirahezeRelay>	 <m3w> there is no per section protect possible
[09:03:54] <MirahezeRelay>	 <cosmicalpha> @elliethepwincess do you want me to help so you can learn how to add to ManageWiki or not?
[09:05:06] <MirahezeRelay>	 <elliethepwincess> I'm a bit confused on how those settings work so sure
[09:06:40] <MirahezeRelay>	 <cosmicalpha> okay but not yet, I have a huge headache and am on 15 hr flight right now that I should try and get some sleep.
[15:19:30] <MirahezeRelay>	 <pixldev, replying to elliethepwincess> You want help doing config PRs? I could try and help
[15:21:50] <MirahezeRelay>	 <pixldev> Side note @reception123 I had an idea about https://issue-tracker.miraheze.org/T10674
[15:22:26] <MirahezeRelay>	 <reception123, replying to pixldev> just so you know part of it is already done in ManageWiki
[15:22:30] <MirahezeRelay>	 <reception123> it just needs the table part
[15:22:32] <MirahezeRelay>	 <pixldev> Dang
[15:22:33] <MirahezeRelay>	 <reception123> like WikiDiscover
[15:22:43] <MirahezeRelay>	 <pixldev, replying to reception123> How so
[15:23:00] <MirahezeRelay>	 <pixldev> Never mind I guess lol:(
[15:23:32] <MirahezeRelay>	 <reception123> oh no, I mean the table is still fully needed for it to work
[15:24:00] <MirahezeRelay>	 <reception123> oh, interesting
[15:24:01] <MirahezeRelay>	 <reception123> https://github.com/miraheze/ManageWiki/pull/399
[15:24:50] <MirahezeRelay>	 <pixldev> I was thinking a page that shows a list of wikis by any toggle settings like extensions
[15:32:32] <MirahezeRelay>	 <reception123> well yeah basically like WikiDiscover
[16:43:33] <MirahezeRelay>	 <solodayheavenofficial> https://github.com/miraheze/YouTube/pull/27
[16:44:05] <MirahezeRelay>	 <solodayheavenofficial, replying to solodayheavenofficial> I made some changes to the PR to fix some isuses
[16:44:12] <MirahezeRelay>	 <solodayheavenofficial> Would appreciate if someone could review the changes
[17:03:43] <MirahezeRelay>	 <pixldev> Took way to long to find the request review button dang
[17:16:11] <MirahezeRelay>	 <cosmicalpha, replying to solodayheavenofficial> CI is failing: syntax error in extension.json
[17:16:14] <MirahezeRelay>	 <solodayheavenofficial> ah
[17:16:16] <MirahezeRelay>	 <solodayheavenofficial> will check
[17:16:24] <MirahezeRelay>	 <solodayheavenofficial> https://tenor.com/view/computer-works-for-me-meme-engineering-dvd-gif-27508941
[17:16:27] <MirahezeRelay>	 <solodayheavenofficial> but will figure out whats wrong
[17:20:35] <MirahezeRelay>	 <pixldev, replying to solodayheavenofficial> Dang imagine working with an extension you can actually test on your machine
[17:20:39] <MirahezeRelay>	 <pixldev> Couldn’t be me
[17:22:33] <MirahezeRelay>	 <pixldev> Side question cause thought of it: would it be possible to grant shell access on test without accessing to the database (and by proxy prod) this isn’t me asking how the hell do I get shell I’m just genuinely curious if that’s physically possible. I doubt it would be unless you removed www-data sudo access and that kinda makes working with MediaWiki difficult
[17:24:07] <MirahezeRelay>	 <cosmicalpha> Due to sql.php and eval.php/shell.php it probably isn't necessarily feasible as something we'd likely do but it may be technically possible but not 100% reliable.
[17:24:34] <MirahezeRelay>	 <cosmicalpha> We may split beta into a different DB altogether maybe though
[17:25:20] <RhinosF1>	 It would be possible if it was a different db and password
[17:25:34] <RhinosF1>	 And we didn't store the prod creds on test at all
[17:25:55] <RhinosF1>	 I would probably firewall off the prod dbs too for sanity
[17:26:15] <MirahezeRelay>	 <pixldev, replying to cosmicalpha> Yeah that’s probably the cleanest option and what Rhinos has mentioned a few times
[17:26:32] <MirahezeRelay>	 <pixldev> Although it’s obviously not a priority considering everything else on tech’s plate
[17:26:43] <MirahezeRelay>	 <cosmicalpha, replying to RhinosF1> Yeah we would.
[17:26:48] <MirahezeRelay>	 <solodayheavenofficial, replying to pixldev> Perhaps mirabeta could be set up so that IP addresses are not stored or are assigned random values
[17:26:53] <MirahezeRelay>	 <solodayheavenofficial> And same for emails
[17:27:00] <MirahezeRelay>	 <solodayheavenofficial> Because you don't really need real information on mirabeta
[17:27:05] <MirahezeRelay>	 <pixldev> The issue is beta uses the same db cluster as prod
[17:27:11] <MirahezeRelay>	 <solodayheavenofficial, replying to pixldev> Ah I see
[17:27:23] <MirahezeRelay>	 <pixldev> We could pull a WMF and say beat has no privacy policy I think
[17:28:10] <MirahezeRelay>	 <pixldev, replying to pixldev> That I can think of the only immediate benefit would be removing the NDA from test shell and being proper which really only benefits this idiot and maybe some other users who may want to help in development
[17:28:20] <MirahezeRelay>	 <pixldev> So hardly convincing reasoning to waste time in it
[17:28:45] <MirahezeRelay>	 <cosmicalpha> Yeah it won't be soon but it is on an eventually to-do
[17:29:10] <MirahezeRelay>	 <rhinosf1> Beta's privacy policy should be at risk tbh
[17:29:16] <MirahezeRelay>	 <rhinosf1> That's not no privacy policy
[17:29:21] <MirahezeRelay>	 <pixldev> To quote our fallen penguin
[17:29:23] <MirahezeRelay>	 <m3w, replying to pixldev> I mean you can install linux server as either live mode or permanent to a usb, wouldn't take much to set up mediawiki for dev environment
[17:29:24] <MirahezeRelay>	 <rhinosf1> But just be prepared for this to go wrong
[17:29:26] <MirahezeRelay>	 <pixldev> We’ll do it soon™️
[17:29:36] <MirahezeRelay>	 <cosmicalpha> We are only using about 50% of our resources right now so we can do something with them and putting more into beta would be good to streamline upgrades etc... also...
[17:29:45] <MirahezeRelay>	 <pixldev, replying to m3w> Oh I have a local mw dev environment
[17:30:00] <MirahezeRelay>	 <pixldev> The issue is a wiki farm with Create and ManageWiki isn’t as easy
[17:30:02] <MirahezeRelay>	 <solodayheavenofficial, replying to m3w> I run MediaWiki on my normal pc, not on a USB just on Apache I have installed
[17:30:05] <MirahezeRelay>	 <solodayheavenofficial, replying to pixldev> Oh that's true
[17:30:14] <MirahezeRelay>	 <solodayheavenofficial> I've never tested anything with CreateWiki
[17:30:14] <MirahezeRelay>	 <m3w, replying to solodayheavenofficial> is that a windows or macOS?
[17:30:15] <MirahezeRelay>	 <pixldev, replying to solodayheavenofficial> docker(mwcli) on WSL here
[17:30:18] <MirahezeRelay>	 <solodayheavenofficial, replying to m3w> Linux
[17:30:21] <MirahezeRelay>	 <m3w> ok
[17:30:22] <MirahezeRelay>	 <solodayheavenofficial> I use Ubuntu specifically
[17:30:28] <MirahezeRelay>	 <m3w> are you using same os as production?
[17:30:36] <MirahezeRelay>	 <cosmicalpha> I do need to see if I can find my CW/MW docker image as it would be good to have...
[17:30:40] <MirahezeRelay>	 <solodayheavenofficial, replying to m3w> Doubt it but don't know
[17:30:41] <MirahezeRelay>	 <rhinosf1> Our prod is Debian
[17:30:51] <MirahezeRelay>	 <solodayheavenofficial> I'm not targeting a specific OS, I hope that what I code works on most OS's
[17:31:03] <MirahezeRelay>	 <solodayheavenofficial, replying to rhinosf1> Ah, Ubuntu is Debian-based so it should be good
[17:33:19] <MirahezeRelay>	 <m3w> https://jsonlint.com/ and https://jsonchecker.com/ says your extension.json is valid
[17:33:57] <MirahezeRelay>	 <m3w> same for https://jsonformatter.org/
[17:34:00] <MirahezeRelay>	 <cosmicalpha> I think it is valid actually but placement for resource paths and package files configuration wrong
[17:34:09] <MirahezeRelay>	 <solodayheavenofficial, replying to m3w> Yeah I know, I've been looking at it for a while and can't figure it out
[17:34:11] <MirahezeRelay>	 <solodayheavenofficial, replying to cosmicalpha> Hmm
[17:34:28] <MirahezeRelay>	 <cosmicalpha> But not certain I may be imagining things
[17:34:30] <MirahezeRelay>	 <solodayheavenofficial> I'm not sure what could be wrong because it loads for me and looks right, I had asked in the MediaWiki support server about it because I couldn't get it working at first but now it's working
[17:34:33] <MirahezeRelay>	 <solodayheavenofficial> I'm not 100% sure
[17:34:58] <MirahezeRelay>	 <m3w> usually when I modify and its telling me broken, I use any of those to quickly locate issue.
[17:35:19] <MirahezeRelay>	 <solodayheavenofficial> For me, VSCodium usually tells me where the json formatting errors are at
[17:35:33] <MirahezeRelay>	 <cosmicalpha, replying to m3w> That's a good practice. I usually spend an hour looking at it to realize I forgot a comma or something.
[17:35:35] <MirahezeRelay>	 <m3w> that being all said, why are you electing to not use embedvideos [fork] by starcitizen folks?
[17:35:47] <MirahezeRelay>	 <m3w, replying to cosmicalpha> rather not waste my time getting stressed out
[17:36:06] <MirahezeRelay>	 <cosmicalpha, replying to m3w> You know that is kinda a good point it would be one less extension for us to maintain...
[17:36:46] <MirahezeRelay>	 <solodayheavenofficial, replying to m3w> Miraheze made an original YouTube extension a while ago, I just thought I should make a PR to improve the performance of the extension a bit because I see the extension on Miraheze wikis sometimes messing up core web vitals
[17:36:47] <MirahezeRelay>	 <m3w> would be good especially for you to have less to maintain
[17:37:11] <MirahezeRelay>	 <m3w, replying to solodayheavenofficial> perhaps now is a good time to encourage to switch
[17:37:51] <MirahezeRelay>	 <m3w> [1/4] what if you bump up version for ```php
[17:37:51] <MirahezeRelay>	 <m3w> [2/4] "requires": {
[17:37:52] <MirahezeRelay>	 <m3w> [3/4]         "MediaWiki": ">= 1.35.0"
[17:37:52] <MirahezeRelay>	 <m3w> [4/4]     },```
[17:37:57] <MirahezeRelay>	 <solodayheavenofficial> If you embed a YouTube video directly (i.e. <iframe src="youtube.com" etc immediately on page load)  it will always mess up the core web vitals score because YouTube loads so much garbage and bloat
[17:38:09] <MirahezeRelay>	 <solodayheavenofficial, replying to m3w> That is what I have on my machine
[17:38:13] <MirahezeRelay>	 <solodayheavenofficial> Is it not on the fork repo
[17:38:25] <MirahezeRelay>	 <m3w> I checked the code in your commit
[17:38:33] <MirahezeRelay>	 <m3w> ie pr
[17:38:57] <MirahezeRelay>	 <m3w, replying to solodayheavenofficial> OMG, why is iframe tag even allowed?
[17:39:05] <MirahezeRelay>	 <m3w> kill it with fire
[17:39:20] <MirahezeRelay>	 <m3w, replying to solodayheavenofficial> bump it to 1.39 and see if the process rejects
[17:39:40] <MirahezeRelay>	 <m3w> though I see in sre channel, up to 1.42
[17:39:50] <MirahezeRelay>	 <cosmicalpha, replying to solodayheavenofficial> It was a fork to begin with just stripped out some sources that weren't to privacy safe.
[17:40:12] <MirahezeRelay>	 <solodayheavenofficial> [1/51] So the solution is (small snippet, cuts out most of the code just to give you an idea)
[17:40:12] <MirahezeRelay>	 <solodayheavenofficial> [2/51] ```php
[17:40:12] <MirahezeRelay>	 <solodayheavenofficial> [3/51] $url = $urlBase . $ytid . '?' . $argsStr;
[17:40:12] <MirahezeRelay>	 <solodayheavenofficial> [4/51] return "
[17:40:13] <MirahezeRelay>	 <solodayheavenofficial> [5/51] <div class=\"mw-ytVideo\" style=\"width: ${width}px; height: ${height}px\">
[17:40:13] <MirahezeRelay>	 <solodayheavenofficial> [6/51]     <img
[17:40:13] <MirahezeRelay>	 <solodayheavenofficial> [7/51]         width=\"${width}\"
[17:40:14] <MirahezeRelay>	 <solodayheavenofficial> [8/51]         height=\"${height}\"
[17:40:14] <MirahezeRelay>	 <solodayheavenofficial> [9/51]         src=\"https://i.ytimg.com/vi_webp/{$ytid}/maxresdefault.webp\"
[17:40:14] <MirahezeRelay>	 <solodayheavenofficial> [10/51]     />
[17:40:15] <MirahezeRelay>	 <solodayheavenofficial> [11/51]     <span style=\"
[17:40:15] <MirahezeRelay>	 <solodayheavenofficial> [12/51]         width: {$width}px;
[17:40:16] <MirahezeRelay>	 <solodayheavenofficial> [13/51]         align-items: center;
[17:40:16] <MirahezeRelay>	 <solodayheavenofficial> [14/51]         pointer-events: none;
[17:40:17] <MirahezeRelay>	 <solodayheavenofficial> [15/51]         display: flex;
[17:40:17] <MirahezeRelay>	 <solodayheavenofficial> [16/51]         height: 100%;
[17:40:18] <MirahezeRelay>	 <solodayheavenofficial> [17/51]         justify-content: center;
[17:40:18] <MirahezeRelay>	 <solodayheavenofficial> [18/51]         top: 0;
[17:40:19] <MirahezeRelay>	 <solodayheavenofficial> [19/51]         left: 0;
[17:40:19] <MirahezeRelay>	 <solodayheavenofficial> [20/51]         position: absolute;
[17:40:20] <MirahezeRelay>	 <solodayheavenofficial> [21/51]     \">
[17:40:20] <MirahezeRelay>	 <solodayheavenofficial> [22/51]         <svg style=\"fill: gray; stroke: white\" xmlns=\"http://www.w3.org/2000/svg\" width=\"64\" height=\"64\" viewBox=\"0 0 24 24\">
[17:40:21] <MirahezeRelay>	 <solodayheavenofficial> [23/51]             <path d=\"M12 5c-4.4 0-8 3.6-8 8s3.6 8 8 8 8-3.6 8-8-3.6-8-8-8zm-2 12V9l6 4-6 4z\"/>
[17:40:21] <MirahezeRelay>	 <solodayheavenofficial> [24/51]         /svg
[17:40:22] <MirahezeRelay>	 <solodayheavenofficial> [25/51]     /span
[17:40:22] <MirahezeRelay>	 <solodayheavenofficial> [26/51]     <iframe
[17:40:23] <MirahezeRelay>	 <solodayheavenofficial> [27/51]         style=\"display: none\"
[17:40:23] <MirahezeRelay>	 <solodayheavenofficial> [28/51]         frameborder=\"0\"
[17:40:24] <MirahezeRelay>	 <solodayheavenofficial> [29/51]         allowfullscreen
[17:40:24] <MirahezeRelay>	 <solodayheavenofficial> [30/51]         width=\"{$width}\"
[17:40:25] <MirahezeRelay>	 <solodayheavenofficial> [31/51]         height=\"{$height}\"
[17:40:25] <MirahezeRelay>	 <solodayheavenofficial> [32/51]         data-src=\"{$url}\"
[17:40:26] <MirahezeRelay>	 <solodayheavenofficial> [33/51]     />
[17:40:26] <MirahezeRelay>	 <solodayheavenofficial> [34/51] /div
[17:40:27] <MirahezeRelay>	 <solodayheavenofficial> [35/51] ";
[17:40:27] <MirahezeRelay>	 <solodayheavenofficial> [36/51] ```
[17:40:28] <MirahezeRelay>	 <solodayheavenofficial> [37/51] ```js
[17:40:28] <MirahezeRelay>	 <solodayheavenofficial> [38/51] $( ".mw-ytVideo" ).toArray().forEach( function ( ytVideo ) {
[17:40:29] <MirahezeRelay>	 <solodayheavenofficial> [39/51]     ytVideo.addEventListener( "click", function ( event ) {
[17:40:30] <MirahezeRelay>	 <solodayheavenofficial> [40/51]         // Disable cursor: pointer effect on ytVideo
[17:40:30] <MirahezeRelay>	 <solodayheavenofficial> [41/51]         event.target.style.cursor = 'unset';
[17:40:31] <MirahezeRelay>	 <solodayheavenofficial> [42/51]         // Hide placeholder thumbnail
[17:40:31] <MirahezeRelay>	 <solodayheavenofficial> [43/51]         event.target.children[0].style.display = 'none'; 
[17:40:32] <MirahezeRelay>	 <solodayheavenofficial> [44/51]         // Hide placeholder play button
[17:40:32] <MirahezeRelay>	 <solodayheavenofficial> [45/51]         event.target.children[1].style.display = 'none';
[17:40:33] <MirahezeRelay>	 <solodayheavenofficial> [46/51]         // Show YouTube embed iframe
[17:40:33] <MirahezeRelay>	 <solodayheavenofficial> [47/51]         event.target.children[2].style.display = '';
[17:40:34] <MirahezeRelay>	 <solodayheavenofficial> [48/51]         event.target.children[2].setAttribute( 'src', event.target.children[2].attributes['data-src'].textContent ); 
[17:40:34] <MirahezeRelay>	 <solodayheavenofficial> [49/51]     });
[17:40:35] <MirahezeRelay>	 <solodayheavenofficial> [50/51] });
[17:40:35] <MirahezeRelay>	 <solodayheavenofficial> [51/51] ```
[17:40:36] <MirahezeRelay>	 <solodayheavenofficial, replying to m3w> It's allowed for extensions to add
[17:41:06] <MirahezeRelay>	 <cosmicalpha, replying to solodayheavenofficial> What the hell am I even looking at with raw html in an extension I'd almost say this extension is not security-safe tbh
[17:41:14] <MirahezeRelay>	 <solodayheavenofficial> That's how it's always been
[17:41:25] <MirahezeRelay>	 <m3w> iframe tags were determined no longer security safe
[17:41:28] <MirahezeRelay>	 <solodayheavenofficial> Oh I see what you mean
[17:41:30] <MirahezeRelay>	 <cosmicalpha> I don't think I ever looked in depth
[17:41:31] <MirahezeRelay>	 <solodayheavenofficial> Omg I am stupid
[17:41:35] <MirahezeRelay>	 <solodayheavenofficial> Yeah that is
[17:41:36] <MirahezeRelay>	 <solodayheavenofficial> An issue
[17:41:56] <MirahezeRelay>	 <m3w> an alternative exists, tell folks to switch and this is no longer approved
[17:41:57] <MirahezeRelay>	 <cosmicalpha> Um I think we should just remove YouTube tbh let me check how many wikis use it...
[17:42:01] <MirahezeRelay>	 <solodayheavenofficial, replying to cosmicalpha> yea
[17:42:13] <MirahezeRelay>	 <m3w, replying to cosmicalpha> don't just pull plug, give time to transition first
[17:42:48] <MirahezeRelay>	 <cosmicalpha> 1649 wikis use it.
[17:43:16] <MirahezeRelay>	 <solodayheavenofficial> Yeah so
[17:43:20] <MirahezeRelay>	 <solodayheavenofficial> I think this has an XSS issue
[17:43:34] <MirahezeRelay>	 <solodayheavenofficial> Because "RegEx cannot parse HTML" and it's using regex to determine what it should put in the html
[17:43:37] <MirahezeRelay>	 <pixldev, replying to solodayheavenofficial> What
[17:43:42] <MirahezeRelay>	 <solodayheavenofficial, replying to pixldev> youtube extension
[17:43:49] <MirahezeRelay>	 <pixldev> Okay um
[17:43:53] <MirahezeRelay>	 <solodayheavenofficial> I just noticed this
[17:44:00] <MirahezeRelay>	 <pixldev> CA do you wanna make the despoil task?
[17:44:02] <MirahezeRelay>	 <solodayheavenofficial> Will do some more testing and open a phorge security task if I can reproduce
[17:44:13] <MirahezeRelay>	 <pixldev> Depool*
[17:44:44] <MirahezeRelay>	 <cosmicalpha> We should put a site notice up for wikis using it and write a transition guide on Meta to link to I think.
[17:45:02] <MirahezeRelay>	 <solodayheavenofficial> [1/28] ```php
[17:45:02] <MirahezeRelay>	 <solodayheavenofficial> [2/28]         // Did we not get an ID at all? That can happen if someone enters outright
[17:45:03] <MirahezeRelay>	 <solodayheavenofficial> [3/28]         // gibberish and/or something that's not a YouTube URL.
[17:45:03] <MirahezeRelay>	 <solodayheavenofficial> [4/28]         // Let's not even bother with generating useless HTML.
[17:45:03] <MirahezeRelay>	 <solodayheavenofficial> [5/28]         if ( $ytid === false ) {
[17:45:04] <MirahezeRelay>	 <solodayheavenofficial> [6/28]             return '';
[17:45:04] <MirahezeRelay>	 <solodayheavenofficial> [7/28]         }
[17:45:04] <MirahezeRelay>	 <solodayheavenofficial> [8/28]         // Support the pixel unit (px) in height/width parameters, because apparently
[17:45:04] <MirahezeRelay>	 <solodayheavenofficial> [9/28]         // a lot of people use it there.
[17:45:05] <MirahezeRelay>	 <solodayheavenofficial> [10/28]         // This way these parameters won't fail the filter_var() tests below if the
[17:45:05] <MirahezeRelay>	 <solodayheavenofficial> [11/28]         // user-supplied values were like 450px or 200px or something instead of
[17:45:06] <MirahezeRelay>	 <solodayheavenofficial> [12/28]         // 450 or 200
[17:45:06] <MirahezeRelay>	 <solodayheavenofficial> [13/28]         if ( !empty( $argv['height'] ) ) {
[17:45:07] <MirahezeRelay>	 <solodayheavenofficial> [14/28]             $argv['height'] = str_replace( 'px', '', $argv['height'] );
[17:45:07] <MirahezeRelay>	 <solodayheavenofficial> [15/28]         }
[17:45:08] <MirahezeRelay>	 <solodayheavenofficial> [16/28]         if ( !empty( $argv['width'] ) ) {
[17:45:08] <MirahezeRelay>	 <solodayheavenofficial> [17/28]             $argv['width'] = str_replace( 'px', '', $argv['width'] );
[17:45:09] <MirahezeRelay>	 <solodayheavenofficial> [18/28]         }
[17:45:09] <MirahezeRelay>	 <solodayheavenofficial> [19/28]         // Define urlArgs - container for every URL argument.
[17:45:10] <MirahezeRelay>	 <solodayheavenofficial> [20/28]         $urlArgs = [];
[17:45:10] <MirahezeRelay>	 <solodayheavenofficial> [21/28]         // Got a timestamp to start on? If yes, include it in URL.
[17:45:11] <MirahezeRelay>	 <solodayheavenofficial> [22/28]         if (
[17:45:11] <MirahezeRelay>	 <solodayheavenofficial> [23/28]             !empty( $argv['start'] ) &&
[17:45:12] <MirahezeRelay>	 <solodayheavenofficial> [24/28]             filter_var( $argv['start'], FILTER_VALIDATE_INT, [ 'options' => [ 'min_range' => 0 ] ] )
[17:45:12] <MirahezeRelay>	 <solodayheavenofficial> [25/28]         ) {
[17:45:13] <MirahezeRelay>	 <solodayheavenofficial> [26/28]             $urlArgs['start'] = $argv['start'];
[17:45:13] <MirahezeRelay>	 <solodayheavenofficial> [27/28]         }
[17:45:14] <MirahezeRelay>	 <solodayheavenofficial> [28/28] ```
[17:45:30] <MirahezeRelay>	 <solodayheavenofficial> [1/14] ```php
[17:45:30] <MirahezeRelay>	 <solodayheavenofficial> [2/14]     public static function url2ytid( $url ) {
[17:45:30] <MirahezeRelay>	 <solodayheavenofficial> [3/14]         // @see http://linuxpanda.wordpress.com/2013/07/24/ultimate-best-regex-pattern-to-get-grab-parse-youtube-video-id-from-any-youtube-link-url/
[17:45:31] <MirahezeRelay>	 <solodayheavenofficial> [4/14]         $pattern = '~(?:http|https|)(?::\/\/|)(?:www.|)(?:youtu\.be\/|youtube\.com(?:\/embed\/|\/v\/|\/watch\?v=|\/ytscreeningroom\?v=|\/feeds\/api\/videos\/|\/user\S[^\w\-\s]|\S[^\w\-\s]))([\w\-]{11})[a-z0-9;:@?&%=+\/\$_.-]*~i';
[17:45:31] <MirahezeRelay>	 <solodayheavenofficial> [5/14]         $id = false;
[17:45:31] <MirahezeRelay>	 <solodayheavenofficial> [6/14]         if ( preg_match( $pattern, $url, $preg ) ) {
[17:45:32] <MirahezeRelay>	 <solodayheavenofficial> [7/14]             $id = $preg[1];
[17:45:32] <MirahezeRelay>	 <solodayheavenofficial> [8/14]         } elseif ( preg_match( '/([0-9A-Za-z_-]+)/', $url, $preg ) ) {
[17:45:32] <MirahezeRelay>	 <solodayheavenofficial> [9/14]             $id = $preg[1];
[17:45:33] <MirahezeRelay>	 <solodayheavenofficial> [10/14]         }
[17:45:33] <MirahezeRelay>	 <solodayheavenofficial> [11/14]         return $id;
[17:45:34] <MirahezeRelay>	 <solodayheavenofficial> [12/14]     }
[17:45:34] <MirahezeRelay>	 <solodayheavenofficial> [13/14] ```
[17:45:35] <MirahezeRelay>	 <solodayheavenofficial> [14/14] could possibly try to find a way to put something that just gets through the regex
[17:46:20] <MirahezeRelay>	 <solodayheavenofficial> Actually not entirely sure
[17:46:25] <MirahezeRelay>	 <theoneandonlylegroom> for a second I thought I use YT but apperently is EV
[17:46:26] <MirahezeRelay>	 <solodayheavenofficial> Because it only allows alphanumeric characters it seems
[17:46:32] <MirahezeRelay>	 <cosmicalpha> Okay umm... I wonder if I can strip YouTube and replace the entire extension with just making {{#youtube and other hooks alias to {{#ev: in EV
[17:46:41] <MirahezeRelay>	 <cosmicalpha> For auto migration
[17:47:00] <MirahezeRelay>	 <solodayheavenofficial> I'm not sure if it's safe or not yet
[17:47:03] <MirahezeRelay>	 <solodayheavenofficial> [1/16] ```php
[17:47:03] <MirahezeRelay>	 <solodayheavenofficial> [2/16]         if (
[17:47:03] <MirahezeRelay>	 <solodayheavenofficial> [3/16]             !empty( $argv['width'] ) &&
[17:47:04] <MirahezeRelay>	 <solodayheavenofficial> [4/16]             filter_var( $argv['width'], FILTER_VALIDATE_INT, [ 'options' => [ 'min_range' => 0 ] ] ) &&
[17:47:04] <MirahezeRelay>	 <solodayheavenofficial> [5/16]             $argv['width'] <= $maxWidth
[17:47:04] <MirahezeRelay>	 <solodayheavenofficial> [6/16]         ) {
[17:47:04] <MirahezeRelay>	 <solodayheavenofficial> [7/16]             $width = $argv['width'];
[17:47:05] <MirahezeRelay>	 <solodayheavenofficial> [8/16]         }
[17:47:05] <MirahezeRelay>	 <solodayheavenofficial> [9/16]         if (
[17:47:06] <MirahezeRelay>	 <solodayheavenofficial> [10/16]             !empty( $argv['height'] ) &&
[17:47:06] <MirahezeRelay>	 <solodayheavenofficial> [11/16]             filter_var( $argv['height'], FILTER_VALIDATE_INT, [ 'options' => [ 'min_range' => 0 ] ] ) &&
[17:47:07] <MirahezeRelay>	 <solodayheavenofficial> [12/16]             $argv['height'] <= $maxHeight
[17:47:07] <MirahezeRelay>	 <solodayheavenofficial> [13/16]         ) {
[17:47:08] <MirahezeRelay>	 <solodayheavenofficial> [14/16]             $height = $argv['height'];
[17:47:08] <MirahezeRelay>	 <solodayheavenofficial> [15/16]         }
[17:47:09] <MirahezeRelay>	 <solodayheavenofficial> [16/16] ```
[17:47:13] <MirahezeRelay>	 <solodayheavenofficial> I don't know what these functions do because I don't know much about MW yet
[17:47:18] <MirahezeRelay>	 <solodayheavenofficial> What's filter_var
[17:47:44] <MirahezeRelay>	 <cosmicalpha, replying to solodayheavenofficial> <https://www.php.net/manual/en/function.filter-var.php>
[17:47:49] <MirahezeRelay>	 <solodayheavenofficial> Just looked it up yea
[17:47:55] <MirahezeRelay>	 <solodayheavenofficial> Yeah it only allows integer values for width and height
[17:48:09] <MirahezeRelay>	 <solodayheavenofficial> And the regex only accepts alphanumeric values for the id
[17:48:14] <MirahezeRelay>	 <cosmicalpha> yeah that is safe but the whole extension is just a mess tbh
[17:48:25] <MirahezeRelay>	 <solodayheavenofficial> Could be rewritten to be better
[17:48:32] <MirahezeRelay>	 <cosmicalpha> No need
[17:48:34] <MirahezeRelay>	 <solodayheavenofficial> Alr
[17:48:43] <MirahezeRelay>	 <cosmicalpha> We don't need to maintain a duplicate extension tbh
[17:48:48] <MirahezeRelay>	 <cosmicalpha> It is more work for SRE
[17:48:50] <MirahezeRelay>	 <solodayheavenofficial, replying to cosmicalpha> Alright true
[17:49:07] <MirahezeRelay>	 <solodayheavenofficial> Can you send a link to the source code for the mediawiki extension that embeds videos?
[17:49:25] <MirahezeRelay>	 <theoneandonlylegroom> <https://www.mediawiki.org/wiki/Extension:EmbedVideo_(fork)>
[17:50:19] <MirahezeRelay>	 <theoneandonlylegroom> it's really better to use as template than as direct replacement for `<youtube>`
[17:50:59] <MirahezeRelay>	 <theoneandonlylegroom> I think ...
[17:51:45] <MirahezeRelay>	 <solodayheavenofficial> I looked at the GH page and it seems like a pretty well-written extension that has all the same functionality as the Miraheze extension plus more and also solves the problems I was trying to solve with PR #27
[17:53:23] <MirahezeRelay>	 <cosmicalpha, replying to solodayheavenofficial> https://github.com/StarCitizenWiki/mediawiki-extensions-EmbedVideo
[17:53:36] <MirahezeRelay>	 <cosmicalpha> oh delayed Discord lol
[18:32:58] <MirahezeRelay>	 <rodejong> [1/21] 📚 ANNOUNCEMENT from MediaWiki Discord
[18:32:58] <MirahezeRelay>	 <rodejong> [2/21] https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/5B6XFPFYBETRBRWKQP4AKBFFJENGQLRR/
[18:32:59] <MirahezeRelay>	 <rodejong> [3/21] MediaWiki Language Extension Bundle 2024.04
[18:32:59] <MirahezeRelay>	 <rodejong> [4/21] Kartik Mistry @ 29 Apr 2024 7:30 a.m.
[18:32:59] <MirahezeRelay>	 <rodejong> [5/21] We would like to announce the release of MediaWiki Language Extension Bundle 2024.04. This bundle is compatible with MediaWiki >= 1.40.0 and requires PHP >= 7.4.0.
[18:33:00] <MirahezeRelay>	 <rodejong> [6/21] The next MLEB is expected to be released in 3 months. If there are very important bug fixes, we will do an intermediate release. Please give us your feedback at https://www.mediawiki.org/wiki/Talk:MLEB.
[18:33:00] <MirahezeRelay>	 <rodejong> [7/21]     Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2024.04.tar.bz2
[18:33:00] <MirahezeRelay>	 <rodejong> [8/21]     sha256sum: 743753d6f743e270b49465e534eceb557839095fc0a160ea6c8323a33a9017fb
[18:33:00] <MirahezeRelay>	 <rodejong> [9/21]     Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2024.04.tar.bz2.asc
[18:33:01] <MirahezeRelay>	 <rodejong> [10/21] Quick links:
[18:33:01] <MirahezeRelay>	 <rodejong> [11/21]     Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
[18:33:02] <MirahezeRelay>	 <rodejong> [12/21]     Announcements of new releases will be posted to a mailing list: https://lists.wikimedia.org/postorius/lists/mediawiki-i18n.lists.wikimedia.org/
[18:33:02] <MirahezeRelay>	 <rodejong> [13/21]     Report bugs to: https://phabricator.wikimedia.org/project/view/1464
[18:33:03] <MirahezeRelay>	 <rodejong> [14/21] Highlights:
[18:33:03] <MirahezeRelay>	 <rodejong> [15/21]     IMPORTANT We're planning to make changes to how and when we release MLEB. You can read more about it on Phabricator and leave your comments.
[18:33:04] <MirahezeRelay>	 <rodejong> [16/21] Detailed release notes for each extension are available at:
[18:33:04] <MirahezeRelay>	 <rodejong> [17/21] https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle/2024.04
[18:33:05] <MirahezeRelay>	 <rodejong> [18/21] -- 
[18:33:05] <MirahezeRelay>	 <rodejong> [19/21] Kartik Mistry | કાર્તિક મિસ્ત્રી
[18:33:06] <MirahezeRelay>	 <rodejong> [20/21] kartikm.wordpress.com
[18:33:06] <MirahezeRelay>	 <rodejong> [21/21] [editor's note: https://phabricator.wikimedia.org/T356847 -  Changing MediaWiki Language Extension Bundle (MLEB) Release Process]
[18:33:25] <MirahezeRelay>	 <pixldev> Interesting
[18:33:32] <MirahezeRelay>	 <pixldev> Uh guys what’s a languages bundle
[18:33:42] <MirahezeRelay>	 <rodejong> No Idea
[18:34:03] <MirahezeRelay>	 <elliethepwincess> a bundle of languages
[18:34:07] <MirahezeRelay>	 <pixldev> So true
[18:34:27] <MirahezeRelay>	 <pixldev, replying to elliethepwincess> Nope!
[18:34:29] <MirahezeRelay>	 <pixldev> > The MediaWiki language extension bundle (MLEB) is a curated set of MediaWiki extensions offering multilingual features. It attempts to provide an easy way to bring comprehensive language support to a MediaWiki.
[18:35:05] <MirahezeRelay>	 <rodejong> Perhaps a downloadable package without all languages, but with a limited nr of languages
[18:38:55] <MirahezeRelay>	 <theoneandonlylegroom> so Translate is part of it or it's a TranslateWiki thing?
[18:39:09] <MirahezeRelay>	 <theoneandonlylegroom> mleb more like mlem
[18:49:07] <MirahezeRelay>	 <cosmicalpha> Our deploy tool supports upgrading all mleb extensions at once using `--upgrade-pack=mleb` just thought it was a fun fact lol don't mind me
[18:49:33] <MirahezeRelay>	 <pixldev, replying to cosmicalpha> Automation my beloved
[18:50:22] <MirahezeRelay>	 <cosmicalpha> When I made the current deploy system I also added --upgrade-pack=universalomega lol I probably should remove it tbh
[18:50:30] <MirahezeRelay>	 <pixldev> Huh
[18:50:34] <MirahezeRelay>	 <pixldev> What for
[18:50:48] <MirahezeRelay>	 <cosmicalpha> I never update all my extensions at once lol
[18:51:02] <MirahezeRelay>	 <rhinosf1> We should keep that
[18:51:04] <MirahezeRelay>	 <rhinosf1> It's fun
[18:51:24] <MirahezeRelay>	 <pixldev, replying to cosmicalpha> And don’t worry I yap more than most people here combined lmao
[18:51:38] <MirahezeRelay>	 <cosmicalpha> <https://github.com/miraheze/puppet/blob/21e5a47d681124d1880f5edb3a26d7fedea7a026/modules/mediawiki/files/bin/mwdeploy.py#L90>
[18:52:48] <MirahezeRelay>	 <cosmicalpha, replying to rhinosf1> lol maybe
[18:53:52] <MirahezeRelay>	 <cosmicalpha> I should update mleb though
[18:54:26] <MirahezeRelay>	 <pixldev> Oi Cosmic does RemovePII work on local non farm wikis?
[18:54:37] <MirahezeRelay>	 <cosmicalpha> It requires CentralAuth so no
[18:54:55] <MirahezeRelay>	 <cosmicalpha> It should be made to though
[18:55:26] <MirahezeRelay>	 <pixldev, replying to cosmicalpha> Sadge. More blind development fun ig
[18:56:02] <MirahezeRelay>	 <pixldev> Since my CW pr is pending review might try my hand at what we were talking bout before
[18:56:07] <MirahezeRelay>	 <pixldev> Removing local rights
[18:56:47] <MirahezeRelay>	 <pixldev, replying to cosmicalpha> Mentally noting this as if I find myself bored and with time May do as well
[18:57:09] <MirahezeRelay>	 <pixldev> I don’t wanna overload myself with things to do
[18:57:24] <MirahezeRelay>	 <pixldev> But if I wanna code at least I won’t have a shortage of things to do
[21:02:31] <MirahezeRelay>	 <pixldev> anyone know the least worst way to store/cache a value taken from reading an on wiki page to be used in a hook that im pretty sure is run before each page load?
[21:02:46] <MirahezeRelay>	 <pixldev> reading a page every pageload seems not great idea
[21:03:33] <MirahezeRelay>	 <rabbydevs, replying to pixldev> couldnt you use some extension to add data to the wiki page then to use that in the hook
[21:03:37] <MirahezeRelay>	 <rabbydevs> instead of reading the wiki page?
[21:04:08] <MirahezeRelay>	 <m3w> pix if you explain exactly what the end goal is, might be easier to provide potential solution
[21:04:13] <MirahezeRelay>	 <rabbydevs> true
[21:04:13] <MirahezeRelay>	 <pixldev> good idea
[21:04:15] <MirahezeRelay>	 <pixldev> so
[21:04:26] <MirahezeRelay>	 <m3w> otherwise this is shooting in the dark
[21:04:32] <MirahezeRelay>	 <pixldev> yea mb
[21:09:23] <MirahezeRelay>	 <pixldev> [1/2] im working on an extension that allows admins to set the colors of basic things like link color without writing CSS themselves. im storing the values by writing the values to a json content model page. To actually apply the css rules since mw only like static files my idea is to use the ResourceLoaderGetConfigVars hook to make all of the color values accessible via https://www.mediaw
[21:09:24] <MirahezeRelay>	 <pixldev> [2/2] iki.org/wiki/ResourceLoader/Core_modules#mw.config, then use that to set the css root variables(setting the actual selectors and rules in a static file). so since the values are written to the on wiki page I need to find a way to ig cache them to be applied each time the hook runs
[21:09:27] <MirahezeRelay>	 <pixldev> if that makes sense
[21:43:07] <MirahezeRelay>	 <pixldev> im thinking https://www.mediawiki.org/wiki/Object_cache may be of help here tho
[21:52:17] <MirahezeRelay>	 <originalauthority, replying to pixldev> interesting thought process
[21:52:33] <MirahezeRelay>	 <originalauthority> Fandom sets them in WikiFactory variables
[21:52:42] <MirahezeRelay>	 <pixldev> I'm.. receptive to better ideas
[21:52:44] <MirahezeRelay>	 <originalauthority> similar to how Cosmos does it
[21:52:45] <MirahezeRelay>	 <pixldev, replying to originalauthority> o
[21:52:53] <MirahezeRelay>	 <pixldev> interesting
[21:53:02] <MirahezeRelay>	 <pixldev> i kinda know what that means
[21:53:19] <MirahezeRelay>	 <originalauthority> Theme Designer just posts to the WikConfig API to update the variables in WikiConfig, which then in turn applys them to FandomDesktop
[21:53:41] <MirahezeRelay>	 <originalauthority> (yes I have too much time on my hands looking at how Fandom does things)
[22:10:17] <MirahezeRelay>	 <z_ezinho> [1/2] is there any way to like completely get rid of these error messages
[22:10:17] <MirahezeRelay>	 <z_ezinho> [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1234627847117733958/image.png?ex=66316c49&is=66301ac9&hm=08ccebaf0dc10277b9b5b2be12c0667d0334c6ca16e2104e788ff07a4bcf844a&
[22:11:29] <MirahezeRelay>	 <z_ezinho> the [page](https://witheredhope.miraheze.org/wiki/Republican_Senate) is working just fine and these messages kinda annoy me even though it's a small detail lol
[22:11:50] <MirahezeRelay>	 <theoneandonlylegroom> remove duplicate arguments from the code?
[22:12:42] <MirahezeRelay>	 <theoneandonlylegroom> and you're using infobox base
[22:12:51] <MirahezeRelay>	 <z_ezinho> is it possible to get it to pinpoint the error or nah
[22:12:54] <MirahezeRelay>	 <theoneandonlylegroom> it's intended to be used on other infobox templates
[22:13:12] <MirahezeRelay>	 <pixldev, replying to originalauthority> would cosmos be a good reference point to implement this instead of my current triple layered duct tape?
[22:13:54] <MirahezeRelay>	 <z_ezinho, replying to theoneandonlylegroom> i used the base intentionally but does it create problems or
[22:14:10] <MirahezeRelay>	 <z_ezinho> is it just not the best choice
[22:14:17] <MirahezeRelay>	 <theoneandonlylegroom> I can't tell, I'm about to go eeping
[22:14:31] <MirahezeRelay>	 <z_ezinho> alright, gn!
[22:15:50] <MirahezeRelay>	 <elliethepwincess, replying to z_ezinho> if you want to specifically remove just those categories without changing anything else you can put `HIDDENCAT` on the category page
[22:16:13] <MirahezeRelay>	 <elliethepwincess> but I'm not sure if there is a way to disable them from being added automatically
[22:16:31] <MirahezeRelay>	 <pixldev> is this from PI box?
[22:16:58] <MirahezeRelay>	 <z_ezinho, replying to elliethepwincess> YES thats exactly what i mean
[22:17:01] <MirahezeRelay>	 <z_ezinho> thank you so much
[22:46:13] <MirahezeRelay>	 <originalauthority, replying to pixldev> probably, yeah.
[22:46:30] <MirahezeRelay>	 <pixldev> Time for more running and copying like a headless chicken
[22:58:09] <MirahezeRelay>	 <cosmicalpha, replying to originalauthority> Cosmos uses just a miniature version of ManageWiki tbh. I still need to rewrite and improve it eventually...
[23:35:23] <MirahezeRelay>	 <jph2, replying to elliethepwincess> @z_ezinho you could also edit the template to remove the duplicate parameter call