[04:31:01] Hey Tech folks, what are y’all’s thoughts on https://issue-tracker.miraheze.org/T13261? [04:40:46] as long as it's being used as a slight deterrant for lore, the idea SGTM [04:40:52] i actually should claim it for review lol [04:50:51] my worry is other wikis who use it and don’t get that it can faik [04:51:01] hmm, yeah... [04:51:11] making it restricted sounds like a good idea? [04:51:25] Heavens forbid someone assumes a view restriction extension offered actually works properly [06:34:27] BlankEclair: I'd prefer something that like greyed a page out for that than tried to claim actual read restrictions [06:34:40] wait [06:34:42] i have an idea [06:34:47] It should really be distinct in the way it presents from MediaWiki's own controls [06:34:56] you know the parser function/extension that can output if the user is in a group? [06:35:03] So you can't think oh this is blocking read [06:35:12] You think, this just fuzzes this out [06:35:36] BlankEclair: I think so, not sure if it's core or an extension [06:35:41] But I swear we have that [06:35:41] extension i'm p sure [06:35:48] but, i wonder if they can use that to only output the actual contents if the user has enough clearance [06:36:15] That works [06:36:23] It's defeated by editing the page though [06:36:34] which is probably fine for them [06:36:44] depends if they care if it's trivial to bypass [06:37:16] I hate per page read controls in mediawiki [06:37:20] None of them work well [06:37:36] Which is why I'd prefer something that advertises a hiding or blurring a page [06:37:42] Than actual read controls [06:37:46] wdym hiding a page? [06:38:19] Not really sure [06:38:25] Blurring is best example [06:39:07] It should be a distinct enough experience from what normal read controls on a private wiki look like though [06:41:32] [1/2] thoughts on the phrasing? [06:41:32] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1343472867383447562/Screenshot_2025-02-24_at_17-41-19_T13261_Extension_request_PageOwnership.png?ex=67bd661c&is=67bc149c&hm=9ba03ba3289bb8a3e863674c35cbf1dfd4b4bc5532318b1838449ecc4fd5eae1& [06:43:58] Technically entirely possible through CSS if you don't mind the content being really easy to uncover () [06:48:54] i forgot that mediawiki has built-in support for per-group css lol [07:01:41] Oh nice @orduin [07:01:51] BlankEclair: ye that's cool [07:01:56] oki ty [07:02:29] It's payday this week [07:55:37] > [24/02/2025 18:50] PROBLEM - os151 Disk Space on os151 is WARNING: DISK WARNING - free space: / 23229MiB (10% inode=99%); [07:55:43] chat should we be shitting ourselves? [07:57:32] Not yet [07:57:36] It's only a warning [07:57:58] It should be actioned though [07:58:15] BlankEclair: [07:58:38] so i guess we should only be constipated /lh [07:58:50] okay, in all seriousness, what do we do lol [08:00:12] BlankEclair: actually scratch that [08:00:21] That growth is not what it's supposed to do [08:00:40] oh, um, seems like os161 is full too [08:01:04] getting filled up* [08:01:05] ^^; [08:02:19] BlankEclair: it's known per Mattermost [08:02:26] oh okay then [08:02:28] But that borders on UBN [08:02:47] And we really should separately alert on a sudden huge spike in disk growth [08:02:54] Like that [08:03:00] Compared to the normal pattern [08:03:22] If disk usage is normally stable and suddenly doubles in a week, it should be detected [08:07:40] BlankEclair: cosmic says they are graylog not mw [08:07:46] oh okay [08:07:46] So shouldn't be a user disaster [08:07:55] os is opensearch right? [08:08:13] But it's still badly broken [08:08:13] It's still badly broken [08:09:01] ah okay [08:09:04] hmm, should i go eat dinnya [08:09:12] BlankEclair: yup [08:09:19] oki, bye~ [09:43:00] > but, i wonder if they can use that to only output the actual contents if the user has enough clearance [09:43:52] The problem with using such a hack as a solution means you are probably going to fragment the parser cache and essentially render it useless for articles this is used on (probably not a big deal for one or two articles but if everyone starts doing that then) [12:51:19] Yes fragmented PC could be an issue there [12:51:36] I wonder what our PC hit rate is tbh [22:55:30] how funny would it be if i got an nda just to handle https://issue-tracker.miraheze.org/T13259 [22:56:59] Well you’d need to be onboarded anyways [22:57:03] true [22:57:08] depending on how fast that goes ig [22:59:17] do the funny [22:59:20] get nda [22:59:29] okay cool [23:01:07] do i get started by filing a new task w/ this form? https://issue-tracker.miraheze.org/maniphest/task/edit/form/17/ [23:03:19] No [23:03:35] oh? [23:03:43] For a tech NDA, you’d talk to CA and NotAracham to actually sign [23:03:49] i believe™️ [23:04:02] what do i do first lol? poke CA or make the task [23:04:08] Poke [23:04:22] @cosmicalpha @notaracham can correct me here [23:04:31] Or agent [23:04:35] as ya know [23:04:43] > [25/02/2025 10:04] [Whois] Agent has been idle for 100 days, 6 hours, 33 minutes, and 31 seconds. [23:04:44] former board and DDTech [23:04:49] hell yeah, idle record [23:04:50] the order doesn't really matter [23:04:51] oh no [23:04:59] fair enough [23:05:04] you can make the task right now if you want [23:05:12] We can token bomb it [23:05:13] then email NA the NDA [23:05:13] you would be quite a welcome addition [23:05:26] Totally [23:05:31] Hi hi Cos [23:06:45] well NA would have to email back [23:06:49] we use docusign iirc [23:07:15] Yeah, the NDA is initiated on my end. [23:07:31] oh okay neat [23:07:37] i'll figure out ssh keys w/ yubikeys [23:07:51] and if i can manage to do that in time, i'll file the task now lol [23:07:56] if not, then at like 3 pm [23:08:08] Hi