[03:07:38] I deployed new changes to how ManageWiki cache works (and yes its now truly ManageWiki cache in ManageWiki not CreateWiki lol) if anyone finds any issue where cache doesnt update, settings aren't taking affect, extensions aren't enabling, etc... let me know please. I plan to deploy to production in a couple days if there is no problems at all. [09:21:26] Cargo is enabled in exttest.mirabeta.org ManageWiki but [Special:Version](https://exttest.mirabeta.org/wiki/Special:Version) doesn't show it. [09:21:49] In fact, even templatestyles is gone. [09:23:03] And I can't toggle extensions even though I'm a bureaucrat. It seems that ManageWiki-related user permissions have disappeared on https://exttest.mirabeta.org/wiki/Special:ListGroupRights [09:23:48] [1/2] Settings are probably gone as well. I remember seeing a logo here next to Extension Testing. Rodejong changed it a while ago. [09:23:48] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1404757250928545813/image.png?ex=689c59a3&is=689b0823&hm=2d607ccecf0c0de63d0f3b4fad2daa1ea880080af1cf52e829df18646e147fa0& [11:31:29] Am I missing something here, why is https://github.com/miraheze/mw-config/blob/main/LocalSettings.php#L3952 'read' in the disallowed rights for ManageWiki for *? [11:32:45] additionally, everyone is given the read right here? https://github.com/miraheze/mw-config/blob/main/LocalSettings.php#L3441 [11:35:10] im gonna assume it's to avoid dumbasses making their private wiki readable [11:39:53] but then at $wgManageWikiAdditionalRights, the read right is given to everyone, so surely that negates private wikis? [11:45:57] [1/3] disallowed just means you can't change in mw [11:45:57] [2/3] additional means enabled by default [11:45:58] [3/3] and then somewhere a check for private disables it [11:46:16] maybe its in miraheze functions hmmm [11:46:20] I can't see it in mw-config [11:46:22] my abridged interpretation at least [12:08:50] [1/2] With the risk of Microsoft trashing GitHub, Miraheze might need to start considering alternatives [12:08:51] [2/2] https://arstechnica.com/gadgets/2025/08/github-will-be-folded-into-microsoft-proper-as-ceo-steps-down/ [12:10:05] we'll make our own github with blackjack and hookers [12:11:05] Somewhere there is a hook [12:11:09] I don't know where [12:11:23] That removes read from * if a private wiki and grants it to member and sysop [12:19:23] I think it must be in MirahezeFunctions hmm [12:19:35] today I figured out that Polish by Cloudflare is actually quite detrimental to cache [12:19:36] That’s called Gerrit [12:19:52] didn't you hate it [12:20:03] Hate is a strong word [12:20:16] I'm all about the black and white yo [12:20:26] grey? nuhuh [12:20:50] [1/2] if you have an image, and a logged in user views it, you would totally expect that that image is eligible to be cached if fetched from somewhere like swift/s3. [12:20:50] [2/2] if you have polish enabled, however, polish will not apply the optimisations for images where cookies have been sent along with it. So when the same image is requested by a logged out user, you get a compressed version of it which is cached again, and are therefore maintaining 2 separate caches for each image [12:20:54] what a dumb as fuck system [12:21:47] why'd cookies be sent for static? [12:22:44] huh? [12:23:30] if you request something from static.domain.com from meta.domain.com, then the browser sends the cookies with the request? [12:23:42] ah true... [12:25:06] I wonder if that behaviour can be altered [12:25:08] probably [12:25:47] imagine pavlov conditioning cloudflare [12:26:03] hm [12:26:10] machine learning by pavlov conditioning [12:26:11] i should sleep [12:28:05] i think the E is pavloving you into sleeping [13:36:45] i think MirahezeLSBot is dead again [13:36:56] just upgraded tweeki but nothing got logged [13:41:18] really... [13:41:46] I think it may be like that because the formatter changed [13:42:14] judging by phorge, I think the tech team have bigger stuff to worry about, I may look into it myself [13:42:21] I do like logs working after all [13:42:32] after I install Gentoo of course [13:43:05] @Infrastructure Specialists [14:50:27] done [14:51:04] @pskyechology oi [14:51:33] state your business smh [14:51:36] would you be able to lend me a hand with a SMW activaton [14:51:43] i was typingsmh [14:52:14] [1/2] i think your device is cooked because i didn't see [14:52:14] [2/2] anygay, if it blows up it blows up [14:52:30] excuse me [14:52:50] smw is like arcane knowledge, only the wisest of wizards can defuse that [14:53:07] but idk in most cases it doesn't blow up so [14:53:32] well they asked for it so :wikipetan: [14:53:46] as i understand a techer has to run the script to get it working [14:54:13] and you are techer [14:54:27] as i understand, this hasn't been the case for a while now [14:54:35] is it? huh [14:54:54] i vaugely recall that but also the noticeboard still says tech steward [14:54:56] welp [14:55:09] in that case ill turn it on and ask you to clean it up if it does explode [14:55:47] i mean i'll gladly show up with my mop and bucket to a 7 industrial cleaning machines job [14:58:25] well here goes nothing [14:59:21] didnt explode! [14:59:26] woohoo [15:00:30] does disabling SMW cause explosions? [15:00:39] also shouldn't [15:01:42] oh i forgot that request is on a private wiki anyways [15:06:03] SMW 6.0.0 is tagged and released [15:06:34] oh god [16:07:24] @atxatx https://github.com/SemanticMediaWiki/SemanticMediaWiki/pull/6198 [16:10:09] oh no that means we get to test smw now [16:14:29] Needs to recreate the cache. I broke it on first release but later fixed. Will do so if the issue still exists? [16:17:32] Seems to work now anyway. Cache reset must have been triggered by something. [16:40:17] Thanks for the PR, just merged [16:41:09] Theoretically it should be more stable than the current deployed version on Miraheze... [16:43:29] @atxatx seems tests don't even run on MW 1.44 [16:43:38] it says something about a table then stops [16:46:01] The test is the unstable part... [16:49:02] There are also some issues with the tests on the newer PHP version (>8.2). There is a lot of tech debt in the project, which will likely take significant time and effort to address them [18:56:07] so true [19:47:17] hey - quick question (and feel free to redirect me if this is not the right place) - how do I verify that I am a wiki user on here? [19:52:12] #verify [19:52:53] omg thank you. for some reason i didn't have the channel in my channel list! [19:53:13] @pixldev ^ can you beat that channel into defaults [19:53:43] maybe even make it recommended [19:53:57] i cant remember if we have the silly introduction stuff on [20:28:27] Introductions is off, and the channel is defaulted visible for all users [20:28:38] huh [20:29:02] Yeah, dunno what's up, but verify should always be visible [20:34:01] Tec [20:34:34] h [21:06:54] We have the legacy welcome screen, which might be why