[01:40:51] Hey @suzuneu, Q, has Waki285-Bot been erroring lately? Feels like it’s been not actioning some of its repeating tasks (updating the meta RC counter, SR/G clerking) [02:50:04] I think I got wiki loadouts working on https://loadouttest6.mirabeta.org/wiki/Main_Page [02:50:59] [1/2] Basically the requester selects a desired loadout and CreateWiki will import an XML file during wiki creation. [02:50:59] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1475686417463246970/image.png?ex=699e6392&is=699d1212&hm=ce6cd9720789d18f92410dfbe7758a13005b0acbd76489feda183fe61e3de8e7& [02:51:56] [1/3] I tested with these two commits: [02:51:57] [2/3] https://github.com/lihaohong6/CreateWiki/commit/85612a8f713dd077b33bda447763c679b43678c6 [02:51:57] [3/3] https://github.com/lihaohong6/mw-config/commit/b69c671a7df7115711b05214f4e395c351496abb [02:52:25] I’ll take one createwiki-label-loadout-test please [02:52:58] Here you go! One `createwiki-label-loadout-test` because I didn't bother to rebuild the l10n cache. [02:53:17] Ehh it dont taste right [02:55:42] Probably because it contains a random XML dump of extttestwikibeta in it lol [02:56:46] Thats why it tasted like tears and despair [02:58:28] But I’d be curious where it goes from there, and just how verbose the loadouts will get [02:59:10] I guess verbose isnt the right term more like scope or how deep will it go [02:59:59] [1/2] Still need some more testing on the CreateWiki patch. I also need to figure out how the loadout wiki is going to work. Maybe export latest revision of each non-talk page to an XML file, attribute the edit to `Maintenance script` with a summary "imported from , see original page for attribution". The XML file gets uploaded somew [02:59:59] [2/2] here on the internet and pulled by puppet to be synced to all servers. [03:00:22] [1/2] This is what it looks like when I set up l10n properly on my local wiki btw. [03:00:22] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1475688778667659325/image.png?ex=699e65c5&is=699d1445&hm=658f3f3de4ad7795c1dff4d9e67781af3e02ca6ff20ed0d0be3a99beb54034d9& [03:00:38] Do you mean how many templates, gadgets, etc. it'll have? [03:00:49] Yes [03:01:54] Like is this meant to further curb the messy wikipedia imports people tend to do, or is this an effort simply to ease the initial setup? [03:03:35] [1/2] Gadgets: HotCat (default, registered users only), Reference Tooltips (default, enabled for all), Navigation popups (optional). [03:03:35] [2/2] Template: not sure. Probably mbox and navbox as a start. Infobox is messy and I don't really want to think about it. Wikipedia templates are usually a huge pile of technical debt (e.g. infobox on dev still relies on Common.css), so maybe we roll with some simpler solutions. [03:04:38] Mostly the latter. The former would be a by-product because we can't accommodate all wikipedia templates, but it would still be nice to have less need to import from wikipedia. [03:05:48] I mean we already discourage wikipedia template imports simply because they werent meant to be used outside of wikipedia, and lets be honest they are a hot mess, this could actually help alot [03:16:00] <_chrs_, replying to posix_memalign> this would actually be a really good way to package up the more complicated wikipedia things that are useful to wikis (bc 95% of the problem with them is the importation process) [03:16:49] <_chrs_> like e.g. infobox uses common.css on dev bc. the wikipedia one still uses it (this is bc. they have raw infoboxes to handle), I've actually made a fully templatestyles for loginwiki [03:23:12] Thanks for the support. I felt that this is one of the main missing features on MH so I thought I'd give this a try. [03:24:17] Still missing stuff such as enabling additional extensions when a loadout is selected because we don't enable Gadgets by default. [03:25:32] <_chrs_> yeah this is probably one of the best improvements to the new wiki experience possible atp [03:25:34] <_chrs_> [1/4] my idea for what to go for re templates would be [03:25:34] <_chrs_> [2/4] (a) things like mbox, navbox, infobox and such [03:25:34] <_chrs_> [3/4] (b) Template:Documentation and other stuff commonly used in template documentaton [03:25:35] <_chrs_> [4/4] (c) commonly used modules [03:26:03] Very aligned with a lot of the ideas we've kicked around in MCR [03:26:41] The idea of creating quick to deploy loadouts would be very neat [03:27:07] <_chrs_, replying to posix_memalign> if this becomes a thing I'd just say turn on gadgets by default [03:27:11] IIRC labster had an extension in mind to simplify that, will have to dredge up a note [03:30:13] is there a way to install the pure skin? ive been stumped for a while [03:38:25] I think CA made a PoC of this a few rewrites of CW ago, would be uber excited to see it come to life [03:39:04] I do remember that, am also blanking on the name, urggg [03:39:54] Aha, Data Transfer [03:40:07] https://www.mediawiki.org/wiki/Extension:Data_Transfer [03:40:14] Yaron extensioj [03:41:06] https://github.com/miraheze/MirahezeMagic/pull/520 not really load out but "configure-at-request" feature for some of the core settings and what not. [03:42:43] Mhm [03:44:06] I feel like I've seen the default skin selector. It would be a great addition, especially if we adjust the default skins and add Citizen to the roaster. [03:50:38] Wait, it's from 6 months ago. I guess we need to first figure out whether we want to resurrect this PR since merging the loadout patch will probably mess it up with some more merge conflicts. [03:51:57] 18 monrhs [03:51:59] 2024 [03:52:42] <_chrs_> hmm yeah that could be linked w/ the loadouts [03:57:32] I could just redo it. [12:17:13] [1/2] Yeah I did something similar [12:17:14] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1475828916110491648/Screenshot_2026-02-24_at_12.17.02.png?ex=699ee849&is=699d96c9&hm=66ffb3cf70c19415bc5f7fabe6546c2ad946e4bfbbc90f1707187f3091687d5c& [12:17:20] Sorry didn't mean the ping [12:20:55] where are my authentication-popup fans at /j [12:22:41] fallback my beloved [13:34:10] would it also be possible to do some ManageWiki stuff by default e.g. enabling visual editor [13:34:23] since that appears to be something that trips a few users up [13:34:55] fire up a RfF [19:33:45] Oh this is really nice. I was thinking of providing skin preview links in the help message, but perhaps this is more convenient. [19:35:24] [1/3] Depends on whether you want it to be the default for all wikis or a certain loadout. [19:35:24] [2/3] To be the default for all wikis would probably require a RfF, especially since VE is a quite controversial. [19:35:24] [3/3] To make it a part of a loadout simply requires a function call to ManageWiki to enable it after the wiki is created. [21:36:46] [1/2] I can steal the code from that home page. ? 🫣 [21:36:46] [2/2] The form looks a bit like mine, but I can't get it to work with dark mode. https://ucronias.miraheze.org/wiki/Ucron%C3%ADas:Portada [21:37:36] What home page [21:38:09] https://meta.telepedia.net/wiki/Telepedia_Meta_Wiki?action=history&dir=prev [21:40:38] Sure do as you must [21:40:38] thanks @originalauthority 😀 🫡