[02:50:06] @cosmicalpha bump on the managewiki-privacy right (since you said you wanted to get to that today, if you want me to bump later on just lmk) [02:50:49] I was just about to look into this more literally just opened the ManageWiki repo lol. Probably won't actually implement till tomorrow but looking into it now. [02:51:19] Not even 5 seconds before you sent the message I opened the ManageWiki repo lol. [02:52:41] Maybe I can just implement now. It is one line lol. [02:56:07] :grin; [02:56:18] I know [02:56:45] Is it? I thought it’d be more ngl [02:57:02] A little more lol [02:58:07] [1/2] ooooo [02:58:08] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1469165233539907795/image.png?ex=6986aa3f&is=698558bf&hm=0ee903d6c024dcd3bede08570a2614537697bf6f79ddac96adfca918e9441263& [02:58:26] Heh, I see that I can't do some minor things in Phorge because I'm not verified. https://issue-tracker.miraheze.org/project/view/84/ [02:59:16] Do you still remember my experience years ago at Phorge as Hispano76? 😅 [03:06:47] I’ll add you soon as I figure out how the hell I do that [03:07:42] Yes, we will eventually deploy that to replace CookieWarning to prod for GDPR. Been planning for months. [03:08:24] https://github.com/miraheze/ManageWiki/pull/763 untested though. [03:17:24] can you toss it on beta [03:17:59] And give me the perms to test it lol [03:20:05] We need to make sure we add it to `$wgManageWikiPermissionsDisallowedRights` also btw. [03:20:14] Might not get to that tonight. [03:20:31] Can tomorrow afternoon. [03:21:12] Good call [03:21:31] Eh I can poke someone else in tech with beta rights [03:21:49] Sure works for me. [03:22:29] @blankeclair hiiiiiiii girlypop [03:22:37] meow? [03:23:13] Yeah for some reason im very tired tonight and its not even 9PM I just dont feel like logging in to test and think I'm going to call it in very early tonight lol. [03:23:35] Maybe because I was up until 5:30AM the last 4 nights in a row. [03:23:43] [1/2] finally [03:23:43] [2/2] CA sleeping early [03:23:50] i still haven't bothered to reenable shell lol [03:38:19] May be.. [03:38:22] now go [03:38:27] Not shell [03:38:35] meow? [03:40:04] Need to test global managewiki core (and restricted) and the new privacy rigjt on beta [03:40:44] but I either need to make a second account or a way to control my global rights bc i need to test with and without -privacy [03:43:56] so essentially, give you managewiki-core and/or managewiki-privacy for two accts? [03:47:15] The new PR doesnt require managewiki-core to change private remotely. Was more complicated to do that. [03:47:29] ig? idk im tired and a bit grumy rn so not super thimk thinking [03:47:30] It just requires managewiki-restricted and managewiki-privacy [03:47:38] thats what i thought [03:47:47] wait also restricted? [03:48:02] is restricted used to access remote [03:49:11] I dont think typically but wanted to here for a bit extra consistency (most other truly restricted fields do need it) and protection. [03:49:59] i need a name for an alt mmmm [03:50:18] eh Notadev hell with it [03:50:28] Mostly because once deployed managewiki-privacy could end up selectable in MWP, until cache is cleared on all wikis so for now at least, we double protect behind another right also. [03:50:43] Just in case. [03:50:44] 💯 [03:52:50] PixlDev [03:52:56] make it as confusing as possible [03:52:56] forgot beta is closed registration lol [03:53:05] actually i do go by that [03:53:22] oh yeah, what wiki? [03:53:23] when i my name has to be lowercase i find it looks betters as pixldev than pixdevl [03:53:31] check my discord [03:54:36] A friend of mine once said that a friend of hers saw my username as read it as PixDeVI, aka Pix De Six [03:54:37] exttest is technically accurate lol [03:54:40] idk, my brain isn't braining [03:54:54] just numb, cycling through the days until i can get hrt to hopefully cope [03:55:25] my ass can't even worry anymore, i'm just too dead for it all [03:55:34] anyway, is exttestwikibeta okay? [03:56:29] preferably global because id also wanna test on meta remote [03:56:31] [1/2] actually, are you sure it's even deployed on mirabeta? [03:56:32] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1469179930444304606/1770350191012.png?ex=6986b7ef&is=6985666f&hm=f6cffcba36a8f27171e9c02d589067b0be447763fb27245231291b661e97d2a2& [03:56:38] ah oki [03:57:17] CA may have set that for tmr [03:57:25] feel free to checkout the PR [03:57:26] i think [03:57:27] why not ask him for rights lol [03:57:37] i assume code wise, because no shell [03:58:00] oh right forgot about that uh [03:58:12] want me to poke petra [03:58:54] new alt https://meta.mirabeta.org/wiki/User:Elliot [04:00:49] @petr [04:00:51] oh wait [04:01:08] so the impl is that you have the managewiki-* rights in the central wiki, and you remotely config the wiki? [04:02:00] if so, yea i +1 it [04:02:05] cba to grab yurikey tho [04:02:21] what [04:05:48] like [04:05:56] let's say you wanna touch clairewiki [04:06:16] do you only have the local rights for managewiki-* on metawiki, and can touch clairewiki via metawiki? [04:06:29] or is it a global group where you have managewiki-* everywhere [04:07:36] no idea on the former this is for WM/Tech/A[S] so global [04:08:20] if you have the rights on a global group, you can still touch the private flag if you go to managewiki on-wiki lol [04:08:38] at least, that's my interpretation [04:09:18] maybe i'm logicing wrong, or wrongly inferred $ceMW [04:10:44] onkly tech and S will have private [04:11:21] TS also [04:11:34] yea yea [04:11:46] im in a mood and its not one for thinking sorry [04:12:03] No worries, I'm deep into day 4 of work march, so right there with ya [04:12:04] fuck that sink [04:12:24] On bright side, I am writing some of the best code i've ever written, so yay that. [04:12:28] https://github.com/miraheze/ManageWiki/pull/763/files#diff-23b114b2839b985259d6b68086cdc6599e49af5187a589b0510eb6f3deab7470R183 [04:15:14] i assume this is `$canTouchPrivate = $isRemote ? ( has restricted and has private ) : has core` [04:15:18] i'm eating lunch rn [04:15:53] hell yes [04:16:25] private and restricted should still be needed on remote [04:17:57] you would have managewiki-core via a global group, yes? [04:18:18] correct [04:19:34] get out. go to bed. [04:19:57] I was then I had to do something else and saw this lol. Yeah I need to. [04:20:26] So do I... [04:21:38] visiting https://claire.miraheze.org/special:managewiki would let you touch core, correct? [04:21:58] yes.. i think [04:22:09] what does this evaluate to? [04:22:23] AS can't change privacy but it has to be able to changed DPE and such [04:22:48] WM should prob also have the ability to change domain/path stuff and just not touch DPE by policy [04:23:14] idk im out i need to sleep the grumpy is getting worse and theres no reason to make that y'alls problems [04:23:24] Good night [04:24:55] fair lol [04:26:28] [1/6] ```php [04:26:28] [2/6] $canTouchPrivate = $isRemote ? ( has restricted and has private ) : has core [04:26:29] [3/6] $canTouchPrivate = false ? ( has restricted and has private ) : has core [04:26:29] [4/6] $canTouchPrivate = has core [04:26:29] [5/6] $canTouchPrivate = true [04:26:30] [6/6] ``` [04:26:32] oops, wrong reply [04:26:36] meant for ^ [04:30:09] you know my ass is brain foggy when i thought that meant Data Protection Execution [04:30:19] but no, Dormancy Policy Exemption :p [04:30:37] Dumpy property exfiltration [04:31:05] Dumpty humPty sat on the wall, dumpty humpty had a grEat fall [04:31:06] Durango Pear Embargo [04:31:16] I am very tired [04:31:30] i'm not tired, but my brain is [04:31:31] idk [04:31:39] i just want my medsssssssssss [04:51:42] don't...overdose... [04:53:31] it's kinda hard to overdose on estrogen [04:53:54] wait what, i thought you were talking about autism ones [04:53:58] i wish [04:54:00] are you trans then? [04:54:02] well, dunno what autism meds there are [04:54:08] but i wish i had adhd meds [04:54:11] yep [04:54:15] col [04:55:13] i probably could overdose on cyproterone acetate, but even my brain knows that > 12.5 mg/day has diminishing returns, so i don't bother lol [04:55:45] [1/2] it also appears i have been unfortunately reminded of this video exists [04:55:45] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1469194834530009190/59C78F6B-BDE4-4929-BEC1-4CC8473C47C6.png?ex=6986c5d0&is=69857450&hm=7ba404278df13ad6531668bc3bef833b647610ea10fd80522b22d85f34405391& [04:56:29] [Do it yourself](https://media.discordapp.net/stickers/1313915677588848790.png?size=160&name=Do+it+yourself&lossless=true) [08:06:24] [1/3] https://meta.miraheze.org/wiki/Special:Contributions/PetraMagnaBot [08:06:25] [2/3] The bot now automatically records Cloudflare and Matomo analytics on-wiki. With a few months time we should be able to get some trend charts. [08:06:25] [3/3] Unfortunately Extension:Charts doesn't seem to receive any attention so I took a stab at it without knowing what I'm doing https://issue-tracker.miraheze.org/T12839#298255. [08:07:18] I'm not sure if we want npm on MW servers. The current puppet PR assumes that it exists. But it could also be built elsewhere like eventgate. [08:22:58] hmm, femiwiki? [09:05:00] [1/3] After some DMs with CA I think this follows the standard for nodejs deployments: [09:05:00] [2/3] https://github.com/miraheze/chart-deploy [09:05:01] [3/3] https://github.com/miraheze/puppet/pull/4746 [09:06:52] I did see femiwiki-deploy but it seems to be abandoned? [09:26:49] Is that still enabled [09:28:33] We should have fixed uid + gid @posix_memalign [09:28:50] For future sanity reasons [09:32:22] The femiwiki skin is still enabled and usable. I guess upstream never pushed breaking changes. [09:33:14] Probably [09:33:40] [1/2] Do you mean uid/gid in puppet configs? [09:33:40] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1469264773785981096/image.png?ex=698706f3&is=6985b573&hm=e598e77212593c0f185f22f00c2b2e54f3d4d8abff2db61920b605a331c40db1& [09:33:56] Ye [09:56:06] [1/7] So we would replace the string with a fixed numeric value, having the same layout as mattermost except with a different uid (1501?). [09:56:06] [2/7] ⁨``` [09:56:07] [3/7] modules/mattermost/manifests/init.pp [09:56:07] [4/7] 16: $uid = $mattermost::params::uid, [09:56:07] [5/7] modules/mattermost/manifests/params.pp [09:56:07] [6/7] 19: $uid = '1500' [09:56:08] [7/7] ```⁩ [09:58:01] Ye [09:58:17] gid & uid can be the same number [09:58:27] Just check it isn't using by running the id command [10:09:55] 1501 is not used on test151, mwtask181, and mw181. I would assume those are the only ones that matter because the service will only be deployed there (and other servers with the same setup). [10:12:22] Sounds good [10:25:19] [1/2] https://github.com/miraheze/puppet/commit/0aeaf7cbdbb896d6f2250cd26d602a617f97c9de [10:25:19] [2/2] The mattermost config is pretty cryptic, so this is mostly a guess at what should be done. [10:30:04] That should work [10:30:16] I wonder if the user should require the group [10:30:27] I can't remember if puppet is deterministic enough for that [10:32:01] I think it might be better to move the require group to the user but @posix_memalign [10:32:14] Or add it [10:32:36] Because User does depend on the group existing [10:37:52] Done. If puppet does perform some parallel initialization mathoid and such will be affected too, though one more rule won't hurt. [10:40:52] [1/2] My hypothesis (having no experience with puppet) is that intra-module parallelism is usually sufficient. If something within a module is taking too long, it might then be worthwhile to run the rest in parallel. [10:40:53] [2/2] With that said, since most of these setup steps require spawning a process (e.g. run git), the overhead of parallelism (spawning a process/thread) should be negligible. [10:58:55] @posix_memalign I can merge in like an hour [11:03:45] [1/8] CA said in a DM that he can deploy it on the weekend, though it's probably fine if you do it earlier. [11:03:45] [2/8] This change in ⁨`manifests/site.pp`⁩ uses ⁨`role`⁩ and ⁨`include`⁩ in the same node, and we weren't sure if this is valid. I guess we'll find out once you deploy. [11:03:45] [3/8] ⁨``` [11:03:45] [4/8] node 'test151.fsslc.wtnet' { [11:03:46] [5/8] role(mediawiki_beta) [11:03:46] [6/8] include role::chart [11:03:46] [7/8] } [11:03:47] [8/8] ```⁩ [11:04:54] It's only test [11:05:00] That's fine for test [11:05:04] We should clean up before prod [11:05:24] I won't deploy to prod without @cosmicalpha [11:05:32] So he knows what's going on [12:18:17] [1/9] https://meta.miraheze.org/wiki/Tech:Noticeboard/Removal_of_ImageRating_extension [12:18:17] [2/9] Draft page for the proposed removal of a few SocialProfile-adjacent extensions that [12:18:17] [3/9] (1) Don't seem to be used in a serious capacity by any wiki [12:18:17]