[01:13:40] <MirahezeRelay>	 <sergiofls> is it possible to change the topic or scope of a wiki that was already created?
[01:34:18] <MirahezeRelay>	 <cynicalsix> is there any way to make it so a random image in a category shows? i can find randomimage, but i can only figure out how to make it pull from a manual list
[02:52:26] <MirahezeRelay>	 <randomizedkirbytree47, replying to sergiofls> Just edit the main page to change the description of what it's about?
[03:31:22] <MirahezeRelay>	 <.labster, replying to sergiofls> Go to Special:ManageWiki to change the description as well
[03:33:13] <MirahezeRelay>	 <.labster, replying to cynicalsix> You should be able to use DynamicPageList3 to make a list from a category, then randomly select one of those.
[04:00:57] <MirahezeRelay>	 <notaracham> Technically you should also report a scope change on the stewards noticeboard found on meta.miraheze.org, but as there's only one steward at the moment it'll be a minute before that gets reviewed
[13:04:48] <MirahezeRelay>	 <theoneandonlylegroom> any build-in way to make a list of subpages, or only w/ dpl?
[13:45:27] <MirahezeRelay>	 <RonnlaxoMain> Hallo!
[14:01:52] <MirahezeRelay>	 <m3w> [1/9] @redmin0 dormacy policy requires to file exemption, not to automatically grant upon qualifying for exemption.
[14:01:52] <MirahezeRelay>	 <m3w> [2/9] - if it was intended to automatically grant per qualify, policy needs update to reflect 
[14:01:53] <MirahezeRelay>	 <m3w> [3/9] - if intended for _no longer serves a purpose only_, should be clarified. Currently it's applying to any that become inactive 
[14:01:53] <MirahezeRelay>	 <m3w> [4/9] Imposing size limits isn't the only solution for repeat abandoned or semi abandoned wikis. 
[14:01:53] <MirahezeRelay>	 <m3w> [5/9] - an objective review to determine whether keeping is beneficial or if other active wikis would benefit from gaining the space back
[14:01:54] <MirahezeRelay>	 <m3w> [6/9] > - 1 small wiki isn't much, however hundreds together mean you can get a GB or 2 back
[14:01:54] <MirahezeRelay>	 <m3w> [7/9] > - perhaps wiki creation request policy needs to revisit how to handle abandoned forks, probably exists a clause that abandon will result in removal.
[14:01:54] <MirahezeRelay>	 <m3w> [8/9] > - MH already encountered  crisis over space shortage resulting in no backups due to over-focus on host wikis at all costs. Disaster was bound to occur. Not fault of sre.
[14:01:54] <MirahezeRelay>	 <m3w> [9/9] Active wikis are generally worth more than inactive unless wiki project in "complete" status
[14:02:30] <MirahezeRelay>	 <m3w, replying to .labster> Extwnsion Datamaps might be more user friendly
[14:23:36] <MirahezeRelay>	 <redmin0, replying to m3w> [1/10] > dormacy policy requires to file exemption, not to automatically grant upon qualifying for exemption.
[14:23:37] <MirahezeRelay>	 <redmin0, replying to m3w> [2/10] Right and I do not think LichMaster98 (or I) have said anything about automatically granting upon qualification.
[14:23:37] <MirahezeRelay>	 <redmin0, replying to m3w> [3/10] > if intended for no longer serves a purpose only, should be clarified. Currently it's applying to any that become inactive
[14:23:37] <MirahezeRelay>	 <redmin0, replying to m3w> [4/10] The presumption is that if it serves a purpose, a bureaucrat can ask for an exemption or keep making random edits so I think the policy is doing fine. Also, deleted (but not dropped) wikis can be restored if desired just in case someone realised their wiki has been "deleted" and wanted it back.
[14:23:38] <MirahezeRelay>	 <redmin0, replying to m3w> [5/10] > an objective review [snip]
[14:23:38] <MirahezeRelay>	 <redmin0, replying to m3w> [6/10] Unfortunately, that is just not feasible given the lack of volunteers.
[14:23:38] <MirahezeRelay>	 <redmin0, replying to m3w> [7/10] > 1 small wiki isn't much, however hundreds together mean you can get a GB or 2 back. While database storage isn't much, image storage is valuable.
[14:23:38] <MirahezeRelay>	 <redmin0, replying to m3w> [8/10] I agree and that is exactly what is done. (Although we have been unable to drop databases due to issues with the file storage system for about 8 months: https://phabricator.miraheze.org/T11033)
[14:23:39] <MirahezeRelay>	 <redmin0, replying to m3w> [9/10] > perhaps wiki creation request policy needs to revisit how to handle abandoned forks, probably exists a clause that abandon will result in removal.
[14:23:39] <MirahezeRelay>	 <redmin0, replying to m3w> [10/10] How would this be different from the current DP?
[14:26:03] <MirahezeRelay>	 <redmin0> [1/2] > Keeping an attempted failed fork when a real fork occurs is honestly poor taste because its getting random traffic or edits. The person who forked long forgot or gave up.
[14:26:04] <MirahezeRelay>	 <redmin0> [2/2] Right, except wikis aren't "owned" by the founders so it is the community's decision to make.
[14:31:05] <MirahezeRelay>	 <m3w, replying to redmin0> [1/3] Yes not owned by founder or whomever requested. 
[14:31:06] <MirahezeRelay>	 <m3w, replying to redmin0> [2/3] Which community are we referring to MH or original wiki community?
[14:31:06] <MirahezeRelay>	 <m3w, replying to redmin0> [3/3] - if we consider the original community never joined a dead fork but has now publicly announced a real fork, wouldn't that be obvious grounds to remove per community? Wouldn't it be respectful towards them to remove?? Why in the case of a dead fork should MH community decide?
[14:34:26] <MirahezeRelay>	 <m3w> Keeping the dead fork is no better than what another wiki hosting platform does yet would be viewed as spite in a case of a real vs dead fork
[14:49:56] <MirahezeRelay>	 <m3w, replying to redmin0> [1/10] Almost feels implied some want different enforcement compared to written policy
[14:49:57] <MirahezeRelay>	 <m3w, replying to redmin0> [2/10] If a wiki warned as dormant doesn't request exemption, no reason to grant it.
[14:49:57] <MirahezeRelay>	 <m3w, replying to redmin0> [3/10] - Random edits to avoid is same issue another wiki hosting platform put a hard stop that impacted adoption process.
[14:49:57] <MirahezeRelay>	 <m3w, replying to redmin0> [4/10] - Aware of reopen request, unless I'm mistaken that isn't likely to be repeatedly granted 
[14:49:58] <MirahezeRelay>	 <m3w, replying to redmin0> [5/10] If a wiki should have been already deleted yet technical issues prevented, a request by a real fork to no longer index is fair game. Technical issues preventing DP from being enforced isn't an excuse to reset timer as it already met conditions for removal.
[14:49:58] <MirahezeRelay>	 <m3w, replying to redmin0> [6/10] I already went through like first 6 pages of wiki discover 
[14:49:58] <MirahezeRelay>	 <m3w, replying to redmin0> [7/10] - inactive or dead
[14:49:59] <MirahezeRelay>	 <m3w, replying to redmin0> [8/10] - blatant violating policy of changing scope or copying wikipedia 
[14:49:59] <MirahezeRelay>	 <m3w, replying to redmin0> [9/10] gathered maybe a list of 10 to consider saving per the prior impending MH collapse 
[14:49:59] <MirahezeRelay>	 <m3w, replying to redmin0> [10/10] A fork is meant for a community to move or someone in their attempt to compete. When the interest or motivation is gone, it serves little purpose and per DP is grounds for removal once conditions are met
[15:01:18] <MirahezeRelay>	 <redmin0, replying to m3w> I think there is a difference, actually. We allow wiki admins to request their wikis to be deleted unlike other hosts.
[15:02:29] <MirahezeRelay>	 <theoneandonlylegroom> let's reach out to admins already?
[15:03:10] <MirahezeRelay>	 <redmin0, replying to m3w> [1/5] > 
[15:03:10] <MirahezeRelay>	 <redmin0, replying to m3w> [2/5] > Which community are we referring to: MH or original wiki community?
[15:03:10] <MirahezeRelay>	 <redmin0, replying to m3w> [3/5] The one on MH.
[15:03:11] <MirahezeRelay>	 <redmin0, replying to m3w> [4/5] > Wouldn't it be respectful towards them to remove?? Why in the case of a dead fork should MH community decide?
[15:03:11] <MirahezeRelay>	 <redmin0, replying to m3w> [5/5] Both of these questions are moot.
[15:03:33] <MirahezeRelay>	 <redmin0, replying to theoneandonlylegroom> This convo is about the DP in general. 🙂
[15:04:36] <MirahezeRelay>	 <m3w, replying to redmin0> Ok, the MH community basically no longer exists and qualified for deletion that is impeded by technical issues
[15:05:19] <MirahezeRelay>	 <m3w> Cook's entire request is moot on basis had DP been enforced, wiki wouldn't even exist
[15:07:30] <MirahezeRelay>	 <m3w, replying to redmin0> Think there's only 1 host that doesn't allow deletion unless personal project excuse
[15:08:41] <MirahezeRelay>	 <redmin0, replying to m3w> [1/12] > If a wiki warned as dormant doesn't request exemption, no reason to grant it.
[15:08:41] <MirahezeRelay>	 <redmin0, replying to m3w> [2/12] Of course, this is already the case.
[15:08:42] <MirahezeRelay>	 <redmin0, replying to m3w> [3/12] > Aware of reopen request, unless I'm mistaken that isn't likely to be repeatedly granted
[15:08:42] <MirahezeRelay>	 <redmin0, replying to m3w> [4/12] As far as I am aware, Stewards do not actually check that.
[15:08:42] <MirahezeRelay>	 <redmin0, replying to m3w> [5/12] > I already went through like first 6 pages of wiki discover 
[15:08:42] <MirahezeRelay>	 <redmin0, replying to m3w> [6/12] > 
[15:08:43] <MirahezeRelay>	 <redmin0, replying to m3w> [7/12] >     inactive or dead
[15:08:43] <MirahezeRelay>	 <redmin0, replying to m3w> [8/12] >     blatant violating policy of changing scope or copying wikipedia
[15:08:43] <MirahezeRelay>	 <redmin0, replying to m3w> [9/12] As for the first type, they will be handled by the DP.
[15:08:44] <MirahezeRelay>	 <redmin0, replying to m3w> [10/12] As for the second, please do report them on the Stewards' noticeboard.
[15:08:44] <MirahezeRelay>	 <redmin0, replying to m3w> [11/12] > A fork is meant for a community to move or someone in their attempt to compete. When the interest or motivation is gone, it serves little purpose and per DP is grounds for removal once conditions are met
[15:08:45] <MirahezeRelay>	 <redmin0, replying to m3w> [12/12] I should note here that SRE sometimes refuse to import large wikis when all or a large portion of the original community aren't moving.
[15:10:40] <MirahezeRelay>	 <redmin0, replying to m3w> "Random" people making edits is not a technical issue though.
[15:13:10] <MirahezeRelay>	 <m3w, replying to redmin0> [1/4] Stewards probably should start checking old reopen requests. Maybe something to reconsider 
[15:13:10] <MirahezeRelay>	 <m3w, replying to redmin0> [2/4] That was just to make a point of what I found from first 6 pages, didn't have time to collect a list. 
[15:13:11] <MirahezeRelay>	 <m3w, replying to redmin0> [3/4] - a simple case of violations hiding, hoping to not get caught
[15:13:11] <MirahezeRelay>	 <m3w, replying to redmin0> [4/4] That's expected of sre yet a real situation exists
[15:16:55] <MirahezeRelay>	 <m3w, replying to redmin0> [1/3] Technical issue refers to the deletion script not running to enforce DP.
[15:16:55] <MirahezeRelay>	 <m3w, replying to redmin0> [2/3] No where am I referring to random edits. 
[15:16:56] <MirahezeRelay>	 <m3w, replying to redmin0> [3/3] If it qualified after 194 days of no actions, no longer a justification to reset timer or defend keeping it. Serves MH no benefit and results in a fresh independent wiki community being at odds with you
[15:18:40] <MirahezeRelay>	 <redmin0, replying to m3w> [1/2] > Stewards probably should start checking old reopen requests. Maybe something to reconsider 
[15:18:40] <MirahezeRelay>	 <redmin0, replying to m3w> [2/2] It's a good idea but I don't think they have the time to do that at the moment. It's also import to first check if there are enough such requests to begin with.
[15:22:02] <MirahezeRelay>	 <m3w> [1/2] Like I said, storage overall is important and not having enough for disaster recovery is detrimental to MH
[15:22:02] <MirahezeRelay>	 <m3w> [2/2] At this point, maybe to survive in long term; there's a real need to be stricter unless donations can match operating costs
[15:22:47] <MirahezeRelay>	 <redmin0> Of course but Stewards lack the time required, unfortunately.
[15:27:25] <MirahezeRelay>	 <m3w> An simple solution is make a list of archived reopen requests, that way stewards can easily cross check for repeat reopen. No need to dig in archives.
[15:28:50] <MirahezeRelay>	 <m3w> This wouldn't take too long
[15:34:45] <MirahezeRelay>	 <rhinosf1, replying to m3w> Donations are nowhere near high enough to retain true disaster recovery
[15:35:29] <MirahezeRelay>	 <rhinosf1> We should have had a DR plan day 1
[15:36:50] <MirahezeRelay>	 <max20091> well, someone should make an easy tool to backup as user wishes
[15:38:11] <MirahezeRelay>	 <max20091> [1/5] The current backup is way too annoying:
[15:38:11] <MirahezeRelay>	 <max20091> [2/5] *Have to submit to phab
[15:38:11] <MirahezeRelay>	 <max20091> [3/5] *Hope someone does read it
[15:38:11] <MirahezeRelay>	 <max20091> [4/5] *Wish there is enough space for backup
[15:38:12] <MirahezeRelay>	 <max20091> [5/5] Bruh
[15:40:26] <MirahezeRelay>	 <rhinosf1> @max20091 we have actual backups
[15:40:31] <MirahezeRelay>	 <m3w> [1/2] True DR is hard but set aside storage for backups is essential. Must not return to total focus on only wiki hosting without backups since hardware isn't the best quality
[15:40:32] <MirahezeRelay>	 <m3w> [2/2] Now is best time for a full audit of what wikis to retain and maybe enact stricter standards
[15:40:33] <MirahezeRelay>	 <rhinosf1> That are automatically taken
[15:41:03] <MirahezeRelay>	 <rhinosf1> @m3w unless we had about 10% of our size. You ain't getting true DR.
[15:41:12] <MirahezeRelay>	 <rhinosf1> And we have storage to backup databases in full
[15:41:21] <MirahezeRelay>	 <rhinosf1> We have off site backups
[15:42:27] <MirahezeRelay>	 <m3w, replying to rhinosf1> Is the community not willing to allocate 10% for DR?
[15:42:51] <MirahezeRelay>	 <rhinosf1, replying to m3w> I don't think anyone's going to kill 90% of our wikis
[15:43:24] <MirahezeRelay>	 <rhinosf1> True DR would mean replicating all storage to another DC
[15:43:46] <MirahezeRelay>	 <max20091> You will never reach true DR on MH
[15:43:46] <MirahezeRelay>	 <rhinosf1> That's in another geographic location
[15:43:58] <MirahezeRelay>	 <max20091> Given its size and the cost to operate
[15:44:17] <MirahezeRelay>	 <max20091> Likely only backup the most important part which is quite small
[15:45:19] <MirahezeRelay>	 <max20091> (unless it was some insane size wiki with full of images)
[15:45:40] <MirahezeRelay>	 <m3w, replying to rhinosf1> [1/2] Was going off the 10% mentioned as basic DR, ie active wikis get priority and inactive wiki if storage exists. Now there is a dedicated disk or two it seems.
[15:45:40] <MirahezeRelay>	 <m3w, replying to rhinosf1> [2/2] Not sure where this kill 90% came from...
[15:46:26] <MirahezeRelay>	 <rhinosf1> @m3w I said we'd need to be about 10% of our current size to have enough spare resources to have proper DR
[15:46:59] <MirahezeRelay>	 <rhinosf1, replying to max20091> Not really, we proved during the SCSVG migration that Miraheze doesn't have the capacity to turn on from cold without significant trouble.
[15:47:19] <MirahezeRelay>	 <rhinosf1> We would struggle a lot operating using the backups as there's no cache.
[15:47:29] <MirahezeRelay>	 <rhinosf1> And we can't operate without the cache well
[15:47:45] <MirahezeRelay>	 <m3w> Cloudflare as cache?
[15:48:43] <MirahezeRelay>	 <max20091, replying to m3w> There's a problem with MH's wiki rendering which makes cache insanely big
[15:49:41] <MirahezeRelay>	 <max20091> I bet it's most likely image rendering faults
[15:50:25] <MirahezeRelay>	 <rhinosf1, replying to m3w> We'd need to pay
[15:50:33] <MirahezeRelay>	 <rhinosf1> @max20091 nothing to do with images
[15:50:53] <MirahezeRelay>	 <rhinosf1> Also cloudflare would still not help with parser + object caching
[15:50:57] <MirahezeRelay>	 <rhinosf1> Only varnish layer
[15:51:05] <MirahezeRelay>	 <rhinosf1> Which we didn't loose in the SCSVG migration
[15:51:38] <MirahezeRelay>	 <max20091, replying to rhinosf1> Wait, so how do MH serve images then? I thought it was from RAM or some sort like that?
[15:52:02] <MirahezeRelay>	 <rhinosf1, replying to max20091> We cache thumbnails but they are stored in Swift
[15:52:21] <MirahezeRelay>	 <rhinosf1> Thumbs aren't affected by the issues with other caching
[15:52:30] <MirahezeRelay>	 <max20091> 🤔
[15:56:31] <MirahezeRelay>	 <_______________________________d> cross-site scripting was fixed (thank god)
[16:01:03] <MirahezeRelay>	 <rhinosf1> @_______________________________d if you find an XSS vuln, please inform us responsibly
[16:01:21] <MirahezeRelay>	 <_______________________________d> there is none
[17:35:22] <MirahezeRelay>	 <therealfame> Any writers in here? I'm having a hard time coming up with how i should go about remaking a wiki for the second time on a new platform
[17:49:58] <MirahezeRelay>	 <theoneandonlylegroom> wdym
[18:43:00] <MirahezeRelay>	 <theoneandonlylegroom> [1/3] if you struggle w/ icons on Timeless, modified to be of dark colors, Zelda Wiki has white icons under public domain
[18:43:00] <MirahezeRelay>	 <theoneandonlylegroom> [2/3] <https://zeldawiki.wiki/wiki/Category:Timeless_Skin_Icons>
[18:43:00] <MirahezeRelay>	 <theoneandonlylegroom> [3/3] <https://zeldawiki.wiki/wiki/MediaWiki:Timeless.css>
[18:47:47] <MirahezeRelay>	 <theoneandonlylegroom> also how they can categorize css pages?
[18:52:32] <MirahezeRelay>	 <chimecrime, replying to theoneandonlylegroom> interesting, like this apparently
[18:54:29] <MirahezeRelay>	 <therealfame, replying to theoneandonlylegroom> Currently just need someone who can write in a better format then me to help setup page, Or help be get out what i am trying to describe on the wiki. As well as rating the references and letting me know if i should add more, delete some or use higher quality ones only
[18:55:20] <MirahezeRelay>	 <therealfame> Hmmmm...
[18:55:29] <MirahezeRelay>	 <therealfame> Maybe theres a better way i can also describe this
[18:56:17] <MirahezeRelay>	 <therealfame> Either way a simple tldr would be someone that can fill out a role of maintaining information, Or helping on writing out information.
[19:03:40] <MirahezeRelay>	 <gummiel> [1/2] Actually just tried on my wiki to just put a `[[Category:Timeless]]` on a CSS page on my wiki just on its own line. And while it will tell you there are errors, it will ask if you want to submit anyway, and it seems to work fine still if you do say yes, even without putting it in a comment, at first glance (Ofc that does leave it kinda up to you to ensure it is the only error on the 
[19:03:40] <wm-bot>	 https://meta.miraheze.org/wiki/Category:Timeless
[19:03:41] <MirahezeRelay>	 <gummiel> [2/2] page)
[19:05:14] <MirahezeRelay>	 <chimecrime, replying to gummiel> hiding it within /  / lets you save it without errors, tho I only tested it on a templatestyle css
[19:06:28] <MirahezeRelay>	 <gummiel> Which is fair, I am just saying you don't have to use a comment but I geuss either works yeah, so it is in fact possible to very easily in fact categorise css pages as an answer to Legrooms qeustion
[19:06:44] <MirahezeRelay>	 <chimecrime> yeah true
[19:10:48] <MirahezeRelay>	 <theoneandonlylegroom> interesting
[19:11:59] <MirahezeRelay>	 <theoneandonlylegroom, replying to therealfame> [1/2] depends on subject
[19:12:00] <MirahezeRelay>	 <theoneandonlylegroom, replying to therealfame> [2/2] if it's a fan wiki it needs someone who has enough knowledge of subject and you better advertise wiki in corresponding fan communities, and
[19:22:39] <MirahezeRelay>	 <therealfame, replying to theoneandonlylegroom> Gots it, Whats a good place to advertise to find an editor?
[19:23:48] <MirahezeRelay>	 <theoneandonlylegroom, replying to therealfame> I already said? if it's a wiki about some game it's logical to visit some place dedicated to that game, like reddit or discord server?
[19:24:15] <MirahezeRelay>	 <theoneandonlylegroom> of it's something more original or vague, them I dunno
[19:24:46] <MirahezeRelay>	 <theoneandonlylegroom> we had there one person who would hire editors to write stuff for her fictional world
[19:25:14] <MirahezeRelay>	 <theoneandonlylegroom> and even w/ money it's always difficult to find such editors
[19:27:10] <MirahezeRelay>	 <therealfame> Oh- Agreed if all that can be suggested is reddit..
[20:35:59] <MirahezeRelay>	 <theoneandonlylegroom> [1/2] has someone tried use this instead of Common.css?
[20:36:00] <MirahezeRelay>	 <theoneandonlylegroom> [2/2] <https://zeldawiki.wiki/wiki/MediaWiki:Gadget-Site.css>
[22:17:29] <Guest13>	 new wiki created today, changed my preference for appearance but now the wiki looks more like Wordpress than what I started out with...tried changing the style several times, but still get the same look and User Preferences is not available at the top right
[22:17:30] <Guest13>	 what did I do wrong?
[22:18:04] <MirahezeRelay>	 <theoneandonlylegroom> depends on skins
[22:19:05] <MirahezeRelay>	 <theoneandonlylegroom> go to `Special:Preferences` manually via URL
[22:19:24] <Guest13>	 agreed, but every change to the skin still seems to look the same
[22:19:39] <MirahezeRelay>	 <theoneandonlylegroom> where exactly do you change?
[22:20:00] <MirahezeRelay>	 <theoneandonlylegroom> in >wiki< style settings or your >user< preferences?
[22:20:03] <Guest13>	 default skin
[22:20:15] <Guest13>	 in user prefs
[22:20:42] <Guest13>	 before logging in, the appearance is what I started with
[22:21:22] <MirahezeRelay>	 <theoneandonlylegroom> what skin is set now in your preferences?
[22:21:23] <Guest13>	 changed here too: wiki/Special:ManageWiki/settings
[22:21:34] <Guest13>	 cologneblue
[22:21:45] <Guest13>	 but started with the default (vector-2022 ?)
[22:21:46] <MirahezeRelay>	 <theoneandonlylegroom> your user set skin will always override what you set in wiki setting
[22:22:30] <MirahezeRelay>	 <theoneandonlylegroom> so I suggest first go your user setting and put it back to vector
[22:22:45] <MirahezeRelay>	 <theoneandonlylegroom> *preferences -> apperance
[22:23:00] <Guest13>	 these are the options in the top right: MAIN PAGE ABOUT HELP FAQ LOG OUT
[22:24:11] <MirahezeRelay>	 <theoneandonlylegroom> go to `.../wiki/Special:Preferences#mw-prefsection-rendering` please
[22:27:01] <Guest13>	 both set the same now, seems to have fixed it:user pref:  Vector (2022) (default...
[22:27:02] <Guest13>	 wiki pref:  Vector (2022) (default
[22:27:51] <MirahezeRelay>	 <theoneandonlylegroom> good
[22:28:31] <Guest13>	 now I have a drop-down at the top right (user icon) with a Preferences option :)
[22:28:32] <Guest13>	 tx! (y)
[22:39:28] <Guest13>	 is there a document with screenshots that shows what the skins look like? I'm randomly switching but they all seem to look the same when I use a different browser and don't login (i.e., no user pref override)
[22:43:39] <Guest13>	 nm, I see the Preview link
[22:50:38] <MirahezeRelay>	 <Juesto> Guest13: preview is &useskin=<skinname>
[22:50:49] <MirahezeRelay>	 <Juesto> to navigate to other pages change the url
[22:50:57] <MirahezeRelay>	 <Juesto> or add the useskin parameter
[22:51:08] <Guest13>	 \O/
[23:13:23] <MirahezeRelay>	 <learning_driven> [1/2] what's the correct pronunciation of 'miraheze'
[23:13:23] <MirahezeRelay>	 <learning_driven> [2/2] is it 'mira-heh-zeh' or 'mira-heez'  or 'mira-hee-zee' ?
[23:14:11] <MirahezeRelay>	 <axyrex, replying to learning_driven> meer-ah-heez
[23:14:24] <MirahezeRelay>	 <learning_driven> tx 🙂
[23:31:19] <MirahezeRelay>	 <gummiel> There is no official correct pronunciation, so say it however makes sense for you