[00:07:45] so what elements would I have to set to transparent background to just have the body background image show? [00:18:17] none i believe [00:18:29] background image renders over the color [00:19:17] i would still set the color to something similar to you image so its not a jarring swicth while your image loads in [00:32:17] [1/2] Hi! i made a request for a new wiki like an hour ago but still doesnt appear here , is this normal? [00:32:18] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1346279046404898978/image.png?ex=67c79b91&is=67c64a11&hm=a850a3fc18fcd66205b345a1b8f46f2b19b2ed704eebaf7d363a2df972523855& [00:32:46] check your notifications [00:33:31] [1/2] like either of these 2 [00:33:32] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1346279356691120210/image0.jpg?ex=67c79bdb&is=67c64a5b&hm=464b289e829fdb8ccafbe36e3b99adb302e4326660f4bb936995ad664e1909c4& [00:33:55] [1/2] This request could not be automatically approved and requires a manual review for the following reason: "The request lacks sufficient detail regarding the specific content and structure of the wiki. Please provide more information about the intended articles, topics, and how the wiki will be organized to better understand its purpose and scope." [00:33:55] [2/2] i got this when i submitted it and then i updated it almost immediately, and then havent gotten anything since [00:34:54] it's probably in the "Needs more details" section then [00:35:14] Whats that? [00:36:02] https://cdn.discordapp.com/attachments/407537962553966603/1346279990169436210/image0.jpg?ex=67c79c72&is=67c64af2&hm=4e65210c58a4acbdc048d336e08d9a0c7f015452853fbcc315d1b72bb7eb3d20& [00:37:00] Ah i see, do I just need to wait for someone to review my updated version? [00:37:03] Ty for help btw 🙏 [00:37:10] yep [01:44:20] can you change the font size of individual text? [02:00:17] how does mobile.css work [02:26:47] [1/2] Wiki noob here. I've done some searching in this discord and online and am still slightly confused on my options. Basically, I have a new wiki setup and I want to create a central table for a bunch of data (specifically on items in a game). I then want to use some tool to filter and display that data on other pages (such as filtering by a type of item or a value of the item, etc. [02:26:47] [2/2] ). I've seen options like SemanticMediaWiki and Cargo when searching, but I don't seem to have the perms for adding these extensions to my wiki. [02:28:03] To me I think cargo seems to be a better option, I'd be able to create tables of data using `` and then query that data using `` [02:30:02] Those extensions can be problematic little cry babies so we have them restricted to staff [02:30:16] You can request them be enabled in [[SR/RC]] [02:30:17]

[02:30:51] Hm like they're likely to be used incorrectly or they break often? I'm open to other options but I haven't found any for organizing data without pulling it from an API or using Lua. [02:31:21] Thanks though, this is the kind of request I had assumed existed but couldn't find. Still finding my way around the meta wiki [02:32:08] They can have performance issues so we don’t let them be enabled willy nilly [02:32:29] Understandable if it's crunching loads of data [02:32:34] SMW also has bricked some wikis while enabled when it isn’t updated to the newest software versions [02:32:51] Meta is a bit messy at times yea [02:33:10] feel free to ask here and someone can probably point you in the right direction [02:33:16] i thought this was in the sidebar though [02:34:13] Looks like it is, under "Steward Requests". Tbh I'm just now actually realizing what a Steward means [02:35:08] The terms are a little confusing. I believe I'm a beaurocrat for getting the wiki created (still not sure why not admin but maybe that's a higher role). Steward seems to be miraheze tech or admin people. [02:35:25] [[Stewards]] are the top community role [02:35:25]

[02:35:32] ? [02:35:40] But I'm like day 2 of using miraheze so I'm picking this up as I go. Not meaning to ask about it here, I can read up myself [02:35:47] Can press every button, are top authority in conduct and policy [02:36:06] (welcome :Partyheze: ) [02:36:32] welcome to miraheze [02:36:58] Meta can have gaps at times so if something isnt clear please feel free to ask though [02:40:05] Actually would you mind checking if I created this right? I don't think it looks right since it turns into just a link. [02:40:28] Oh I can't seem to paste the link to it [02:41:41] Nevermind I misread something. I placed the code on my own page instead of the meta page. Nevermind me [02:41:55] Ah, non #verifyed users are blocked from sending links [02:42:05] those pesky spammers [02:47:03] No prob I got it working and it looks right on the request page [02:51:12] Yes. The wiki is in the queue, so it will be looked at as soon as possible [03:03:42] Thank you! [03:31:38] [1/5] Hey everyone, tonight I made the decision to move [the wiki I've been independently hosting](https://www.beastiepedia.net/) to Miraheze due to a number of technical issues we've had over the past 9 months it's existed. While I think it was a worthwhile experiment to try hosting independently, the reliability and stability of a larger platform is something that I think will be a [03:31:38] [2/5] big help. [03:31:39] [3/5] I've been looking through the options for moving a wiki, and it seems that the two options for moving from an independently hosted MediaWiki instance are Special:Export and the pagedump maintenance script. [03:31:39] [4/5] Beastiepedia is currently hosted using Heroku, which has an ephemeral file system. Because of that, while I can run the pagedump script, I can't actually get it from the server (I tried a couple of ways of trying to do this, no dice. If anyone who has Heroku experience does know a way of doing this though I'd love to hear it.) [03:31:39] [5/5] Is there a different way I can get an entire wiki than pagedump or by just plugging the name of every single page into Special:Export? If anyone's ever moved a wiki from Heroku to Miraheze in the past and can provide an example that would be great, although I recognize I'm probably in a pretty weird boat here. [03:32:57] there's a bot which can scrap wiki dumps, xml and files, from any public MediaWiki instance [03:33:59] but only on our volunteers can operate it really [03:37:17] Oh that would be excellent. If a volunteer would be open to helping with that it would be much appreciated. [03:38:18] @pixldev you busy? [03:38:38] I'm not in a huge rush or anything, whenever is convenient is totally fine. [03:38:48] Busy is such a loaded word [03:38:55] ArchiveBot? [03:39:11] wikiteam yeah, it's an indie wiki [03:40:09] Love to see it [03:40:36] cracks knuckles [03:40:42] https://www.beastiepedia.net/ [03:40:44] lets see [03:42:24] in the meantime you can request the wiki and familiarise yourself w/ ManageWiki [03:42:50] Done! Running job `c7465fa1-1a75-481a-9251-a25b2164e1e9`. I will notify you when it updates. Use `/status` with the job ID or use the `Info` button to manually check the job. [03:42:54] aka Miraheze's way of admining things [03:43:01] good bot [03:43:02] [1/2] https://beastiepedia.miraheze.org/wiki/Main_Page [03:43:02] [2/2] the wiki was already approved actually. in fact i expected it to take way longer and not work on this until a later date lol [03:43:13] but i'll check out managewiki for sure [03:43:38] wiki review process was recently automated to mitigate growing amount of requests [03:44:10] so it's unusually quick lol [03:44:22] Yep! Huge improvement, we can now assess most requests in a day vs a week and a half plus [03:45:04] welcome to Miraheze [03:45:12] [[ManageWiki]] [03:45:12]

[03:45:32] Great to see such a growth in interest, but it's been rough keeping up with such growth without paid staff [03:45:58] One day we can pay CA [03:46:02] One day [03:46:21] and agent and paladox and the other folks [03:47:40] i imagine! if I move over to miraheze instead of the indie wiki i'll def become a donor, in the past i've already budgeted some money every month towards keeping the heroku instance running [03:48:00] what was your old infra? [03:48:26] i was using heroku [03:48:47] (with AWS for images bc heroku doesn't support that with its database stuff natively) [03:49:00] in hindsight this was not a good idea [03:49:06] but that's why i'm here [03:49:53] Woah... I'm just thinking how you even thread all that together neatly... [03:50:17] Well, glad to have you here! [03:50:23] it was a real challenge [03:50:24] Silly aracham [03:50:31] this is mediawiki [03:50:33] we dont do neat [03:50:37] and one that was thoroughly unnecessary [03:50:45] but at the same time i learned a lot doing it so it wasn't a total waste [03:50:52] another one to quip [03:50:58] absolutely [03:51:22] Hard lessons learned/earned make the next thing easier [03:55:48] [1/2] looking at the wiki management stuff and about extensions, it says that Cargo is supported but Restricted, and that normal users and wikis can't use it [03:55:48] [2/2] Beastiepedia makes a lot of use of Cargo, and if we're not able to fully use it I'm not sure if we'll be able to make the site work through Miraheze. What exactly does Restricted mean in this context? [03:57:20] Hmm, I thought cargo was unrestricted but that might be wikibase [03:58:07] In any case, you can request restricted extensions to be enabled on [[SR/RC]], we're usually reasonably quick to action [03:58:07]

[03:58:45] oh alright great. I'll definitely do that once we make sure the site scrape/export thing works [04:01:33] There's vanishingly few restricted extensions we won't enable in managewiki, aside from a handful that are on their way out, those that don't play nice with others, and those that are a security risk [04:15:09] Nope, never has been iirc [04:15:18] Or maybe it has [04:16:30] Cargo is cool [04:16:42] when it isn’t deleting dbs or xssing to hell [04:24:30] if using the CSS extension on a page, is using a border-image SUPPOSED to not work? [04:29:42] Job ended. @pixldev [04:30:02] @drchillbrain [04:30:19] Images will need to be requested on [[phorge]] [04:30:20]

[04:31:35] sounds good! thanks again for your help. [04:34:26] And we are also still working on reducing this to make more self manageable as well. CirrusSearch will soon be unrestricted. [04:34:39] ooooooh boy [04:35:14] It used to be yeah I restricted it because of major performance issues at the time with wikis with a large amount of pages. [04:36:01] https://issue-tracker.miraheze.org/T9477#196643 [04:48:24] [1/3] Real quick just for clarity: [04:48:24] [2/3] I have both the Images and the XML file from this scrape [04:48:25] [3/3] Should I submit through https://meta.miraheze.org/wiki/Special:RequestImport with the XML file and then create a separate Phorge request for the images? Or should I just request everything through one Phorge request? [04:57:30] Either mix is fine, though I can help on the special:requestimport if it's small enough for the xml to fit in there [04:58:15] Using RequestImport for XML is good as it will be imported almost immediately that way as all we have to do is press a button there. [04:59:00] alright cool, submitted the requestimport [05:01:34] Started import [05:08:04] @notaracham do Stewards have access to RequestImport to approve or did I forget to open that up to other groups also? Since it no longer requires our intervention (most of the time) it doesn't need to be limited to tech anymore but I can't remember if I opened that up lol. [05:09:35] asking because of this which reminded me lol [05:14:29] Stewards have requestimport access, but I don't recall if any other non-tech roles do [05:15:07] I wonder if any others should then... [05:15:13] I think that was a direct carryover from the WT merger [05:15:31] I don't think so [05:16:46] Yeah it wasn't because pre merger ImportDump wasn't fully automated until about a month later when I finally finished that work so it would have still needed tech intervention pre-merger. [05:17:04] Yeah, so I'm probably just conflating things then [05:17:21] I had to check when I made those changes lol [05:17:26] Still, big jump forward! [05:17:31] February 2024 [05:17:48] Ah, so that'd be why then. That was right in the midst of platform migration [05:17:54] Yep [05:18:30] Anyway do you think it'd be useful for any other groups to have? [05:18:56] Mmmh, wiki mechanic I guess if we ever really do anything with it and GA, probably [05:19:39] It literally just requires a single button to be pressed or if there is no interwiki prefixes it needs one for licensing reasons but there is a form right on requestimport to add interwiki also. [05:19:53] wouldn’t be a bad idea to grant access to GS at least [05:21:03] Yeah that could be good. [05:21:54] I'll look at/consider that tomorrow [05:28:47] hm? [05:29:49] Access to RequestImport [05:29:58] To approve imports [05:52:00] Is there any particular etiquette for DMing a moderator (who helped me prior)? Had a question about some CSS they sent me. [06:21:24] This import finished just FYI someone will handle the image part as soon as we can. [06:21:57] Sometimes there is a bit of a backlog on that though. [06:22:08] Y'all are heroes, thanks so much this was so much easier than I thought it would be [06:22:26] And we have maintenance on Wednesday also so it may be after that. [06:22:31] And yeah that's fine, like I said I'm in no rush the old site will work fine in the meantime [06:25:11] Probably a pretty simple question, but do Miraheze wikis come with licensing templates by default? (just like how Fandom and wiki.gg do) [06:26:08] No, because Miraheze is more of stock MediaWiki by default then the other two are, however that may be a very good idea to do... [06:28:08] How long d oes it usually take for a new wiki request to pass queue? Just to get an idea [06:30:25] from a few seconds to a few days/hours, I'm not sure what the manual review time is these days but it depends on if the AI can automatically approve it. [06:30:25] 🥀 [06:30:25] we've been discussing default templates sets for quite some timea [06:30:25] and still didn't get to resolution [06:31:13] alright, thanks [06:31:25] renders css for moblie client [06:31:51] it belongs to MobileFrontend extension [06:31:56] does it work for all skins [06:32:04] Oh im currently on status: on hold, i imagine that will take longer then right? [06:32:09] no, only what you set as mobile skin [06:32:09] yes tmk [06:32:16] on moblie™️ [06:32:30] oh nbm [06:32:50] fuck mobile.css, all my homies hate mobile.css [06:33:00] That only means the AI couldn't automatically approve it. It may take a bit longer yeah. But shouldn't take quite as long as they used to take. [06:33:44] Thank you! [06:34:02] No problem [06:34:47] I'm going ti suffer making css work for mobile in timeless.css then [06:36:42] dude timeless is mobile adaptive skin [06:36:56] if you use it as default desktop skin you don't even need mobile mode [06:36:57] i know [06:37:16] wdym [06:37:44] what's desktop skin you set? [06:38:13] timeless [06:39:16] here you go [06:39:39] disable MobileFrontend, you'll have to poke only Common.css and Timeless.css [06:39:54] common.css is a choice right [06:39:54] no need for mobile mode switch or Mobile.css [06:42:07] [1/3] though isn't there some stuff i have to change in mobile [06:42:08] [2/3] like this thing [06:42:08] [3/3] https://cdn.discordapp.com/attachments/407537962553966603/1346372118979416115/Screenshot_20250304-034147.png?ex=67c7f23f&is=67c6a0bf&hm=0f8c82ed2140b3e202359f7bb372464aa9c7f359be889d92cd508249d033ef8d& [06:42:54] [1/2] common.css just works on any available for the wiki [06:42:54] [2/2] for specific skin you need to edit specific css [06:43:20] layout changes on mobile resolution, new elements, all still done via timeless.css [06:43:44] again, mobile.css belongs to mobile mode extension [06:44:34]