[00:44:37] With one week to go, we have raised $16,955.70, surpassing two-thirds of our goal! Thank you as always for your support in keeping Miraheze running. https://meta.miraheze.org/wiki/Fundraiser [00:51:43] what happens in the event of no funds [00:53:44] debt collectors walk in and smash our spinnies [01:13:56] not my spinnies [01:18:05] [1/3] As someone who is not in a position to make decisions: pause hardware expansions and purchases; restrict wiki resource usage disproportional to their traffic; disable new wiki creations; reintroduce a RfC similar to a [poorly received one](https://meta.miraheze.org/wiki/Requests_for_Comment/NordVPN); and eventually a [board statement](https://meta.miraheze.org/wiki/Board_of_Di [01:18:06] [2/3] rectors/Meetings/20230615-Statement). [01:18:06] [3/3] Though the previous shutdown was due only in part to the financial situation. [01:21:00] I don’t think not expanding storage is an option right now [01:21:15] Especially given the state of file redundancy (goose egg) [01:21:31] But I would support cracking down on file usage [01:22:04] Strong oppose to stopping new wiki creations though [01:24:25] One idea that was floated a while back that I’d support as a lite measure: domain registrar affiliated links, transparently placed on [[custom domains]] and labeled as a way to support Miraheze [01:24:25]

[01:25:01] Assuming it’s a provider we would otherwise recommend anyways [01:27:33] [1/2] Relevant to this conversation: [01:27:33] [2/2] https://meta.miraheze.org/wiki/Board_of_Directors/Meetings/20260306-Minutes [01:27:54] TL;DR: Hardware expensive, we upped the budget to accomodate it [01:28:52] Yeah this is what I had in mind. With rising hardware prices and the likely outcome of the fundraiser we don't seem to have any funding left for upgrades for the rest of the year (barring a huge lump of money unexpectedly thrown at us). [01:29:12] We did look at instituting raid (becoming increasingly necessary) w/o expansion, it didn't really save us much [01:31:05] (We have enough to cover the updated plan with funds to spare for annual renewal) [01:32:13] I still need to update the budget [01:33:05] [1/2] That is basically a prelude to shutdown or a zombie state like ShoutWiki when all else fails. [01:33:05] [2/2] Though admittedly I have not considered this problem seriously before giving my response. Worst case scenario is that we can't afford upgrades and become slow again like 2023. The other outcomes are unlikely as long as we have a decently healthy volunteer culture that doesn't get everyone else burnt out. [01:37:35] The good news is that our server bill is paid through the end of the year and that we still have plenty of cash reserves. [01:46:13] Not to mention, although our budget unexpectedly increased, we have been having our most successful fundraiser ever. So I’m not worried about the revenue dropping to zero overnight. [01:54:08] Also, pretty great that we were able to make our working capital start working for us too [01:54:41] It's not huge, but it helps take some of the load off of our community [05:15:48] https://discord.com/channels/407504499280707585/1465572781784563773 anyone got any ideas on how to do this the "easy" way [08:35:47] What exactly is a global lock on Miraheze? My understanding is that it is more or less functionally identical to a global block. [11:08:48] discord.com/invite/YDMeaDQM [11:23:14] @Discord Moderators [11:29:19] :BanHammerMH: [12:38:06] I can't help because i'm new to this wiki thing, but i tell you, thats one cool styling to that wiki lol. I might copy some of that stuff into my own wiki 😄 😄 [12:41:14] thanks, if you're gonna just copy stuff from my wiki, please atleast provide attribution (credits) and a link to my wiki [12:42:13] if I do, i'll do that. but i won't, i just want to understand how you worked the html x css so well [12:42:31] tbf i didnt really style my wiki someone else did it [12:43:40] one question though, is all the css stored in common.css? [12:43:56] no its in citizen.css [12:46:26] is citizen an extension? [12:50:29] a skin [12:53:16] i didn't know i could add that, thanks for the tip [12:59:04] is there a way to search for wikis that have a specific skin ? i want to see examples of what people did with the erudite one [13:02:28] https://communities.miraheze.org/wiki/List_of_wikis_by_default_skin [13:03:04] [1/4] also... i tested the CSS, and my page have no change, despite it's category. [13:03:04] [2/4] I do not know why it worked with Hollow Knight wiki, but it didn't work with mine. [13:03:05] [3/4] https://cdn.discordapp.com/attachments/407537962553966603/1480913883865550942/image.png?ex=69b16807&is=69b01687&hm=761ad358e23351eb4ae8d010a158b9d1e049aeacb0bac1e885c7040351c870c8& [13:03:05] [4/4] https://cdn.discordapp.com/attachments/407537962553966603/1480913884289433815/image.png?ex=69b16808&is=69b01688&hm=1f60cea5a785ed4c2e3ecba94698297bbf9d67b59b346811e9f3b84573a83dc9& [13:06:05] exactly what i needed, thanks! [13:21:48] i just noticed vector is a skin on that list but i dont see it in the list of possible skins (its not even greyed out) [13:22:56] check your special:preferences [13:23:13] it's one of the default skins that don't need to be turned on manually [13:25:34] oh i see it [13:25:41] merry christmas [13:25:49] so how can i set it to be the default of my wiki? [13:26:36] it's also written on this page: search for `$wgDefaultSkin` in your managewiki [14:20:27] why do i not have perms to edit extensions and stuff even tho i made the wiki 😭 [14:22:35] anyone got some advice on what i should do [14:23:02] thats a decently frequent bug, request help at [[SR/P]] [14:23:02]

[14:23:19] preciate it [14:29:35] Hello [16:23:31] I know it's possible I just missed something but I'm trying to figure out how to blur/mark an individual image in a gallery like another wiki did but I wasn't able to figure it out [19:22:20] So, there is a difference between miraheze's navbox and wikipedia's navbox. Wikipedia make uses of the lua module, and alias the \#invoke call to the template. However, the lua module of miraheze is different than wikipedia's. Which leave me in an annoying state. [19:23:24] the one we have on devwiki should be rather standalone whilst the one(s) from wikipedia probably do a bazillion other things like grabbing data from wikidata [19:26:27] yeah, but the navbox templates in dev are not working as expected. The lists aren't made to be horizontal. Exemple: [19:26:49] This is a `Navbox|with collapsible groups`. And it's kind of awful 🙂 [19:27:27] [1/2] Someone tempered with Template:Hlist/styles.css and it got imported into dev. [19:27:27] [2/2] https://dev.miraheze.org/wiki/Template:Hlist/styles.css?action=history [19:28:19] Right, I noted an issue with that page a while back. [19:29:12] But my issue isn't from the css, it's the template not bothering to handle lists. [19:30:53] Somehow `| bodyclass = hlist` is not being added to the output. [19:31:22] yeah, something like that. [19:31:26] So there are 2 issues and your list won't show up as horizontal unless you fix both. [19:31:41] I gotta leave but since the issue identified shouldn't be too bad to fix them both. [19:31:57] I fixed the styling issue on my end, though I didn't update the dev page. (I can do that if you want) [19:32:44] Also the template on dev is a standalone thing and doesn't actually invoke the Lua module. If you want the Lua module you'd need to change it to use the `{{#invoke` syntax. [19:33:37] That's the 3rd issue. The lua module can't handle sub boxes. It's for simple navbox only. [19:37:08] [1/6] If you look at wikipedia `with collapsible groups`: [19:37:09] [2/6] It does: [19:37:09] [3/6] ``` [19:37:09] [4/6] {{#invoke:Navbox|with collapsible groups}} [19:37:10] [5/6] ``` [19:37:10] [6/6] But that isn't handled by miraheze's version of the module 🙁 [19:43:23] is it possible to upload mp4s in your wiki?? [19:44:14] Yes [19:44:28] You may need to enable it in ManageWiki [19:44:42] how do i do that 😭 [19:45:18] Add it to `$wgFileExtensions` [19:45:26] In additional settings [19:46:58] thank you :) [19:47:07] Yw :] [20:01:05] here 👆 [20:03:24] These are the changes I made to the Navbox template: . Could somebody from miraheze validate the changes so they can be backported to the dev wiki? [20:19:31] <_chrs_, replying to xrogaan> looks correct, though in backporting terms I would honestly just start over with the wikipedia version [20:20:00] [1/2] You may have to invoke it explicitly `https://dev.miraheze.org/wiki/Template:Navbox_with_collapsible_groups`. [20:20:01] [2/2] The module came from Wikipedia in 2023 https://en.wikipedia.org/w/index.php?title=Module:Navbox&oldid=1157419082 which probably didn't have this feature back then. [20:20:10] The wikipedia version is the Lua module. So that more work than I can do. [20:20:21] <_chrs_> we have a bit of a problem on devwiki where people have "de-wikipedafied" templates and then "oops, turns out wikipedia did that complicated thing for a reason" [20:20:40] <_chrs_, replying to xrogaan> tbh I'll probably get around to making it work with lua at some point [20:24:41] <_chrs_> a lot of wikipedia templates use way too many modules so people go try and completely de-Lua the template which often breaks things [20:25:56] <_chrs_> when reality is more that "there are some uses of modules MH wikis don't need and the removal of which will make it way easier to import" but a where a full pre-Lua rollback still breaks things [20:26:09] I don't believe it works. Or rather, I can't understand how to invoke it properly. `{{#invoke:Navbox|collapsible}}` doesn't work. `{{#invoke:Navbox|navbox}}` works. [20:26:50] (you can try yourself) [20:28:28] there is only the `p.navbox` function available. [20:32:06] [1/2] I meant directly using `{{Navbox with collapsible groups`. [20:32:06] [2/2] I had it working on Blue Archive Wiki before but I copied from Wikipedia, so it's probably not too helpful. [20:34:03] The non-lua template (kind of) works on my end now, with the change I made. [20:34:48] The collapsible part doesn't seems to work. But whatever, it's more of a temporary thing right now.