[00:01:50] I think the first wiki request I ever made was on mirabeta and I was trying to describe the request properly but it ended in aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa to fill out characters [00:07:15] the shorter the guide is the more likely it will be read, I might try to take a raidarr version stab which will probably be too informal but hey [00:31:28] I say all this and then I wrote one of the longest how-to guides lmao [00:35:50] Shorter is better, potentially could hatnote each section to longer essays as subpages of that guide [00:36:43] that was the longest how-to guides, @thewwrnerdguy? [00:39:47] [1/2] we range a bit long and could shrink everything yes, but most things can afford a certain length. In the real world only a slim minority of requestors I would ever expect to read or rather skim, let alone understand a majority of the policies that are conventionally asked of them, and I don't even expect it on principle because most of it is relatively common sense anyway and nobody [00:39:48] [2/2] wants to spend all day reading a bunch of policies with a marginal chance of mattering to them in the big scale [00:40:36] and so for elements relating to the request process especially anything that they should primarily read should be the biggest targets of brevity in as few places as possible to bounce around and so the guide at a spitball is probably too long if its over 3 paragraphs of yap [00:40:58] no matter how much anything beyond that is factual or could be of potential circumstantial use [00:43:57] @dmehus [[help:js]] [00:43:57]

[00:44:27] 32k bytes [00:58:49] I enjoy challenging myself to be brief [01:02:48] @thewwrnerdguy: oh, yes, I saw that one. That one is impressive. It is detailed, but it's chunked out well into sections [01:03:43] @wikitideharej: that's a very good practice. I need to do that more. Brevity is definitely a skill. Some people are more naturally good at it [17:39:56] very nice all in all, though i personally think the youtube one leans a bit broader in scope than I'd typically want but I'd prob ask for a 2o not deny [17:40:24] i have other thoughts i will give later but pix is still not in judgement think mode so I asked the other WRs to give thoguths [17:40:50] np! for what it's worth all of those are the current examples on the page, just with some padded language to make them hit the 350-char limit [17:40:59] (I didn't add anything original) [17:41:48] oh yea fair nuff [17:42:10] yeah maeks sense in hindsight some of them felt, i dont wanna say bloated but, yeah that they were expanded in length [17:42:22] eepy pix.. [17:43:01] Though if others also have issues w/ some of the examples would prob be a good chance to just remake them better [17:43:20] or if we want burn it down and remake a guide from scratch [17:43:31] but i think the current one is mostly fine to salvage [17:48:55] will wait for thoughts on that, for now gonna take a meander to toss ideas on this month's miraheze monthly to refine later [17:49:11] i think the new phorge ux improvements can be mentioned, and def the commons rfc [17:49:40] my rfs is already mentioned [17:49:52] though with minimal glazing if anyone wants to fix that /jole [17:50:40] alternatively i may just go crawl up into offtopic and yap about random old childhood tv shows [17:51:16] anyone used to watch slugterra? [17:52:48] @posix_memalign should most of the prose about commons rfc be in headlines for what's happening [17:53:09] I think inclusion of being closed with a 'see headline above' in whats happening [17:53:38] gonna compare past issues [17:53:59] oh right Subwayfare was removed [17:54:08] so maybe replace rfp section with volunteer changes [17:54:30] Seems to be the convention anyways [17:54:43] skimming past issues i dont see a request for perms header [17:57:25] reminded me to clean up her permissions too, yay [18:22:22] [1/3] for the "wikis considered bad" one that's a reception wiki which is hard-banned [18:22:22] [2/3] using ✅ and ❌ might be accessible but it does make it a bit unclear whether you'd be declining or requesting more details [18:22:23] [3/3] you also don't need to count the characters as it's literally impossible to submit a request less than 350 [18:23:35] hopefully [18:25:09] Feel free to use ❔ for those which need more details versus those that would be outright declined; it's probably good to have a separate section for that actually instead of just "good" and "bad" requests [20:19:49] @thewwrnerdguy: re: Miraheze Monthly August 2026. Tech portion seems a bit short. Do you guys have any other worthwhile updates to share, and should we re-promote the Tech:Noticeboard Request for Feedback re: MW 1.46 proposed extension removals? [20:53:39] ca has just completed a task for the speedscope extension, idk if that'll be generally available by the end of the month but that could be relevant [20:53:46] I think we upgraded citizen this month? [20:55:41] That’s a good oke [20:56:04] Can skim mw-config and puppet commits [20:57:36] should also help [20:58:34] I was looking for something like that earlier, thanks? [20:58:41] Per wiki CSP is another one [20:59:05] new phorge login [20:59:32] custom protection levels [21:00:18] @pixldev did you ever get round to [21:01:12] wgSitemapNamespaces in managewiki [21:01:35] Making the guide? Not yet, I still have the edit menu open for the page to create [21:01:59] Can try to slide it in tonight if you want [21:02:09] That I added a note about on the MM page yea [21:02:19] Sure, can add that [21:04:19] citizen enabled on loginwiki [21:05:46] https://github.com/miraheze/mw-config/commit/243ab8035c6155ea4434259c0d91ff82e96af5d7 to help prepare for NextTide [21:06:46] Do we have anything else on 1.46 progress? We should show we’re actively working on it [21:08:01] tbh I think extension testing is kinda done, there's not really any more momentum [21:08:10] the next thing would be nextide [21:08:15] I think NextTide is the next thing [21:08:18] lmao [21:08:38] It’s time [21:08:40] WWR [21:08:48] Mobilize the Roblox era [21:09:05] tbh I think your commit there is enough of a status update [21:11:42] [1/3] I think what I’d probably wanna do is: [21:11:42] [2/3] A) go to my satellite communities with a list of untested extensions and ask them to tell me the important ones to then to have a shortlist of priority and used extensions we may have missedc and then [21:11:42] [3/3] B) go back and try to drag those wikis into NextTide [21:12:33] IRWA as always is great for this, could probably use it to make an announcement to all members(maybe ping reps) and make a thread to collect names [21:15:39] I can also go to Rain World [21:15:53] @cosmicalpha Oi boss man do you know of any other big NextTide blockers [21:16:48] I don't believe so, I was thinking we could launch NextTide in about a week. We have some other things that should take priority then move to start NextTide. [21:18:23] Like what? [21:18:24] Mostly working on configuring and extensively testing https://github.com/miraheze/CreateWiki/pull/848 which is absolute priority as otherwise the AI will stop working entirely very soon, I want to get that done before shifting focus to NextTide. [21:18:33] Oh yes [21:18:45] There was a note about that on MM actually [21:20:27] Want me to proceed with part A of my idea then? [21:20:50] Mobilizing local communities to call out extensions that really should be verified before starting f to move prod wikis [21:20:55] That works with me. [21:22:25] K, I’ll go to RW first and run a wider scale announcement by the IRWA council [21:23:38] Oh btw this somehow reminded me. My android app for MediaWiki instances is now listed publicly and open for anyone to preregister for stable or join the open beta. More beta testers for this stage would be appreciated also, though of course not required lol. [21:27:46] Anyway I got quite a bit of things I have been meaning to do for months done today lol. [21:28:27] is changing the icons of cosmos to the OOUI icons a part of that list [21:28:41] No lol [21:28:55] :( [21:28:58] I haven't worked on Cosmos in way to long. I really do need to again. [21:29:41] you do...... [21:29:45] I keep saying that then pushing it off though. I really do need to get back into it though. [21:30:03] it probably needs a full on remake IMO [21:30:10] It does yeah. [21:30:21] from the backend to the frotend [21:31:23] It was my first development project in MediaWiki so it was never all that good code wise also. It was originally a JS implimentation over timeless then changed to modify the timeless source code in the first version of the skin. It evolved from there, zero timeless code is left, but it is still a horrible implimentation in many ways. [21:31:58] whenever you got time, i recommend checking the suggestions channel in the cosmos mediawiki server [21:31:59] ALSO [21:32:07] did you renew the mw.cosmos link yet? [21:32:20] mw cosmos example wiki [21:34:05] I'd be happy to preregister or join the beta! [21:38:29] https://play.google.com/store/apps/details/WikiPortal?id=org.wikitide.wikiportal [21:52:43] does mm mean mattermost or miraheze monthly [21:54:47] Miraheze Monthly [21:54:55] the Ms are both capitalised [21:55:31] hmm so is mm mm and MM is Miraheze Monthly [21:55:59] It meant mattermost in this case I think. [21:56:31] I did but forgot to setup the custom domain again thanks. [21:57:46] Pre-registered! [22:05:46] Former in this case [22:14:37] pre-registered 🎉 [22:15:58] :MirahezeStewards: [22:22:30] I guess so. This is a relatively uneventful month. I was hoping something would happen on the MediaWiki front but nothing yet, though there is still a week for nexttide (looks at CA). [23:01:39] and (restricted) are still blocking, probably shouldn't be that much work to resolve both though [23:04:14] @thewwrnerdguy: MM could also mean [[Missing Mirahezians]] [23:04:30] Perhaps it's time to convert that to a dab page? 🤔 [23:09:41] I see MM far more often refer to Monthly than Missing [23:09:50] I have never seen MM stand for Missing Mirahezians [23:19:57] That may just be the more contemporary usage [23:39:59] Perhaps