[04:12:45] @posix_memalign we have about like 2 ish days until march is over....I guess it wouldn't be terrible if march edition went a little bit over but you know the M of the M is prop gonna need time for it's own editing [04:12:51] unless you're already doing that? [04:16:31] yay ping worked [04:25:49] [1/3] i'm trying to figure out wiki highlights section a bit: for example [04:25:49] [2/3] "The Anime Vanguards Wiki covers the Roblox game Anime Vanguards, a tower defense game with anime characters. It moved to Miraheze in March 2026 and uses the Vector 2022 skin." [04:25:50] [3/3] i want it to say something like "it uses a customised version of the Vector 2022 skin" or some emphasis like that cuz it's really clean [04:25:55] oh oops [04:25:57] double ping [04:26:53] This is an interesting situation. I will send a DM. I'm not too worried about it since there is always a backup plan, though. [04:27:24] Yeah talking about the Vector 2022 customization is good. If there is anyting else interesting about the wiki feel free to include as well. [04:27:49] IIRC they're using a subdomain of the game's official site? [04:28:08] let me double check [04:28:20] looks like it [04:28:24] https://vanguards.gg/changelog [13:52:57] [1/2] my very rough draft that's looking for feedback, but not formally yet since I still need to cook with the wording: [13:52:58] [2/2] https://meta.miraheze.org/wiki/User:Skye/Draft:Interface_Specialist [13:54:03] mainly trying to figure out if y'all think this idea has any merit [14:39:50] Very awesome skye [14:40:07] I think this would need more attention tho [14:40:28] that is what I implied yes [14:41:14] [1/2] I like that you added this bit because this was going to be my exact question: [14:41:14] [2/2] > Adopting this group is also a strategic move to match the offerings of some of our competitors. [14:42:51] while we can't promise ultra swag custom styling as a service explicitly, we can try to have something [14:42:56] Would being a member of this group with these permissions grant access to viewing private wikis, or would that still be limited to the discretion of those wikis' admins/bureaucrats? (I just don't know how that works) [14:43:10] private wiki access requires NDAs so no [14:43:26] Got it! [14:46:17] So, better thought out global interface admin sorta? [14:46:40] idk if better thought out but yes [14:46:42] Nein unless you’d like to sell your soul for two doubloons [14:46:52] fancier title than interface admin, really [14:46:53] Well I like this more than the last idea so [14:46:57] I def think this has legs and really like the idea! It would make it much easier to investigate/test, although if the intention is more of a design service, I would definitely love to see a formalized intake/request workflow be developed (Although I am a potentially an affected user so take my opinion with as many grains of salt as necessary!) [14:48:03] I could go on but don't want to swirl [14:48:14] i'm not so sure about making it an explicit service yet, since I definitely don't wanna start an experiment for how fast we can burn our initial test subjects out [14:48:25] Nod nod [14:48:41] we'd also need some sort of criteria since we will probably never be able to cater to everyone [14:48:56] and that's a problem for providing an equal service for everyone [14:50:25] in my mind, a very high impact wiki with tons of users would need styling help more than someone's D&D campaign with two and a half pages of content (no offense) [14:51:03] ergo, better to avoid that issue entirely [14:51:48] anyone's welcome to throw in draft sections if they feel crazy enough btw [14:51:56] Yeah, exactly - it would be wise to limit the scope a bit if if was ever offered as an explicit service, maybe color palette/theme, main page/nav + infoboxes + mbox templates... But yeah the scope could scale with wiki size which makes it tough 🤔 anyway!!! I'm causing swirl 🏃 [14:52:34] something very basic could work indeed [14:53:07] especially if someone crazy devises templates for the more popular skins that dont have variables [14:54:38] no keep swirling girl!!! i wanna hear them ideas [14:56:53] 👀 One thought that crossed my mind is that wikis may want a proof-of-concept before having changes applied to their own wiki, so if this group moves forward/is approved, it might be worth offering mirabeta access to be able to request a test wiki 🤔 butttt technically changes can also be made with stylesheets or personal css so, maybe not [14:57:22] test wiki will haunt you [14:58:02] technically out of scope for mirabeta but more testing is more testing so what can i say [14:58:15] not worth including in the rfc explicitly [14:58:30] I could also see a potential pain point where wikis keep expecting long-term support (which I think is fine, the discord kind of offers that already) but there's likely a need for an "okay, we're done" process so they don't keep coming back and requesting endless tweaks [14:58:58] yeah [14:59:04] since we're all volunteers we always have the "sorry we're volunteers" button [14:59:11] disappears [14:59:14] Going back to the dentist chair!! More later!! [14:59:27] haha have fun!!! i hope? please dont die [15:00:01] erm sorry there gonna have to stop surgery here just uh lie here for a few more days and I'll be right w/ya..... [15:00:16] I just feel like there needs to be a stronger definition yk [15:00:33] Not officially part of this role but if you want wiki creation power on beta just ask and I think we’d be down to grant it [15:00:53] we have 0 reason to not accept new wikis on mirabeta [15:00:54] eyebrow raise [15:00:57] mouth gasp [15:01:02] if anyone wants one they can have one [15:01:23] provided there is at least some use case to doing so (faintest smell of testing will do) [15:01:26] tbh like the only time I ever touched mirabeta was ext testing [15:01:33] man that's gonna be fun [15:01:39] when 1.46 is out [15:01:51] coming soon to a mirabeta near you [15:02:33] I'm sure tech appreciated being a little more lazy with me bouncing 'round there [15:11:38] they see me patrollin' [15:11:39] they hate it [15:12:18] Now watch me whip whip, now watch me nae nae [15:12:43] thank you for your thoughtful contributions to the volunteering side of Miraheze [15:13:38] :wikipetan: [15:13:51] what is whip whip [15:16:12] miraheze monthly [15:17:17] https://en.wikipedia.org/wiki/Watch_Me_(Whip/Nae_Nae) [15:17:51] i see [15:55:50] That's good to have in the back pocket 🤌 [15:56:47] Didn't die! Had fun! No cavities 😈 [15:59:17] One more question from me! If succeeds and is offered as a service, would it be limited to new/migrating wikis or offered on an ad hoc basis? (Sorry I know I'm asking a lot of questions that require assumptions) [16:33:12] other than fewer rights, what's the difference between this and Wiki Mechanic? [16:33:43] also like if you want to help out a wiki with their consent why not just ask for interface admin rights [16:33:43] wiki mechanics can touch requests and managewiki in a limited manner as well, this is purely just for interface [16:34:15] inconvenient mostly, lowers the barrier of entry for asking such help imo [16:34:17] hmm okay so sort of like what global patroller is to global admin then [16:34:25] sure, that's one way to put it [16:34:33] fair point [16:34:52] i could also argue that half the users dont know what a special:userrights is [16:34:55] not a strong one [16:35:24] and also its hard to judge on discord if someone can be trusted enough to grant int-admin like that [16:35:58] Wow?? [16:36:47] it can be