[04:54:24] https://issue-tracker.miraheze.org/T15045 do we have any requirement to have a page on mw.org for exts [04:55:21] would love at least a proper readme [05:01:45] Afaik we did? [05:03:59] Also, if these are just changes to Vector legacy, why can't they just replicate this with CSS/JS? [05:04:28] Doesn't make much sense to have a clone of Vector just with some changes, because it'll still have vector-2022 as a part of it. And if you have regular vector enabled it won't be compatible. [05:05:36] They should prob remove the 2022 part of the skin if they aren't going to use it. [05:05:52] It's not a hard requirement (e.g. Bucket doesn't have it, nor did ImgTag pre-approval) but rather one intended to exclude extensions with no documentation. At least that's my personal interpretation. [05:06:24] Well, the readme in their repo is blank. [05:31:47] Much more scrutiny if there if zero documentation. [05:33:06] We dont have hard policy on it but I also don't like approving hacks of other skins exactly either as it can mostly be done via CSS/JS and it is more likely to break down the line and they'll have to keep maintaining it at our upgrade pace. [12:46:47] do you wanna note this in the task [13:37:46] > so RenderBlocking wouldn't be needed and to (hopefully) improve performance by reducing the bonfire that is the JS file [13:40:01] That's why I later said if they're going to only customise the legacy part of Vector, to remove the 2022 part so it wouldn't be incompatible with regular Vector. [15:39:09] This one worked for the first 16 namespaces but not for ones like Module. I know I could manually enter in the details for NS 828, but wondering if there's a proper way to get the Scribunto defaults [15:46:14] Missing `--force` I think. It's the same return value of https://discord.com/channels/407504499280707585/808001911868489748/1394210785386823680 which was also missing `--force`. [17:28:44] `--force` was the one that worked for the first 16 namspaces [18:52:40] I created https://meta.miraheze.org/wiki/User:MacFan4000/sandbox to test creating the server table with DPL [18:53:35] there are parameter inconstancies, but also we need to figure out how to deal with the cloud cpu stuff being handled differently [18:54:59] and by parameter inconstancies i mean we need to either stick with ssd or stick with nvme when specifying storage [18:55:08] [1/2] aw damn took my joy of making the template away D: /j [18:55:09] [2/2] thank you!!!!!!!!!!!!!!!!!! [18:55:57] issue is that the params are different for cpu cores on cloud servers [19:03:50] actually looks like we can still specify the cpu param at the same time and it wont show on the page but will show in the table [19:11:18] added a second table as well for decommed servers [19:12:24] my intention is to leave a separate manual table of those that dont yet have their own page, and each can be removed upon creation of said page [19:36:30] smart [19:37:18] i think we can omit the kernel field since absolutely none of them use it [19:37:50] some do, i just misspelled the parameter name [19:37:54] (fixed now) [19:39:10] well, IG for running servers its only mwtask171 and mwtask181, but it is pretty widely used for decommed servers [19:40:08] and those mwtask ones are likely outdated [19:40:51] im not even sure how useful that information is since it would likely be tied to the OS version, no? [19:41:16] basically (slightly convenient) data duplication imo [19:41:25] not sure, but it's always been part of the infobox [19:41:55] will pester for CA's opinion after the maintenance [19:42:42] also after the maint: cloud servers should specify proxmox version with debian in paranthesis [19:43:08] i was thinking a tooltip template would be a cool solution to that [19:44:06] (as in, hovering over "Proxmox 9" would explain that proxmox uses debian as a core) [22:59:05] heyy, i've found an LG L600V in my loft, and I've test this phone, it's work but the battery is rly low, how can I rechage this type of battery ? With a universal chager Li-Ion ? [22:59:56] I don't think this is the right server for a question like that [23:11:05] older phones typically have a microusb slot on the side [23:11:20] or they can only be charged with the accompanying dock [23:13:11] i think you should take this conversation elsewhere [23:13:22] tech channel for tech conversations amirite [23:13:49] phones more like a fossil though [23:14:37] That should go to #offtopic please [23:14:53] this channel is for Miraheze related technical discussion [23:33:06] DPL tables are now implemented [23:33:34] and updated cloud* pages for trixie and fixed any param inconsistancies [23:34:11] please use the nvme fields better formatting on server pages. [23:34:18] All servers should use that not ssd. [23:34:40] cloud and test151 use the new version of the template a lot still wasnt updated to it. [23:36:17] the DPL tables are easier when things aren't split across multiple params [23:37:48] But on the server pages it looks nicer with better formatting on more clear to split it. That is why I spent a lot of time working on this in the new infoboxes. DPL can handle it its just a little bit more complex also. [23:44:57] added in the new column with formating to add U.2 NVMe at the end [23:45:22] old column can be removed when all existing pages are updated