[04:41:07] Alright, the Citizen upgrade works for both anons and logged-in users on mirabeta. I'm going to deploy on prod soon. Hopefully nothing explodes. [04:46:50] something will explode and it will be very, very unoticeable trust me [04:46:58] Crap I forgot the l10n cache. [04:47:14] localization strikes again! [04:47:27] [1/2] The menu is going to look like this for a while. [04:47:27] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1533697786749648977/image.png?ex=6a716edf&is=6a701d5f&hm=8e77f2203b0ce2ecd88685b28d1491b4ea971363b675bfdd94839c91867c3c3c& [04:47:53] Fortunately nothing in the main interface broke. [05:06:14] The interface messages work fine on Battle Cats Wiki but somehow Stella Sora Wiki's interface is still broken. tagging.wiki is also fine, so I guess it was a local wiki caching issue. [05:16:02] [1/19] ``` [05:16:03] [2/19] mwscript purgeParserCache stellasorawiki --age=0 [05:16:03] [3/19] Will execute: [05:16:03] [4/19] sudo -u www-data php /srv/mediawiki/1.45/maintenance/run.php purgeParserCache --wiki=stellasorawiki --age=0 [05:16:03] [5/19] Type 'Y' to confirm: Y [05:16:04] [6/19] Deleting objects expiring before Tue, 18 Aug 2026 05:08:20 GMT [05:16:04] [7/19] ... 0.0% done (+1 iterations in 0.0s) [05:16:04] [8/19] ... 1.0% done (+2861 iterations in 31.8s) [05:16:05] [9/19] ... 2.0% done (+2875 iterations in 31.7s) [05:16:05] [10/19] ... 3.0% done (+2840 iterations in 32.6s) [05:16:05] [11/19] ... 4.0% done (+2867 iterations in 30.9s) [05:16:06] [12/19] ... 5.0% done (+2855 iterations in 35.5s) [05:16:06] [13/19] ... 6.0% done (+2861 iterations in 46.1s) [05:16:07] [14/19] ... 7.0% done (+2885 iterations in 32.8s) [05:16:07] [15/19] ... 8.0% done (+2840 iterations in 31.4s) [05:16:08] [16/19] ... 9.0% done (+2902 iterations in 30.5s) [05:16:08] [17/19] ... 10.0% done (+2845 iterations in 37.3s) [05:16:09] [18/19] ``` [05:16:09] [19/19] 10% done after 6 minutes on a medium-sized wiki. It seems that we should just wait for the parser cache to expire by itself considering how slow this is. [06:38:09] L10n messages are also broken on bandoriwiki [06:48:10] fixing the css was a little bit of a pain for this update, cant wait for citizen 4 [06:54:58] Was it necessary to apply additional CSS fixes on your wiki? [07:01:01] needed for pure dark mode [07:01:31] apparently i needed to specify i was not on citizen 4 for it to be fixed [07:11:01] That's odd. I don't think any wiki is using the citizen v4 preview. [07:22:52] How do we feel about the PR https://github.com/miraheze/ManageWiki/pull/792 for https://issue-tracker.miraheze.org/T15460 ? It's blocking DiscussionTools rn and I think it'll be nice to have it enabled by default on new wikis. [07:24:02] I think that would break other things, no? Wouldnt the better option be to defer it until the wiki is actually created then automatically run the SQL? [07:52:09] Yeah I had this issue too [07:52:12] not with manage wiki but [07:52:33] the trick is to run the SQL in a deferred update, at which point the database write to create the wiki would have been committed. [12:11:21] Is it possible to allow subdomains to be requested on a wiki? [12:27:36] Okay, do you mean are you allowed to have another wiki on the same domain? As in a wiki on `example.com` and you want another wiki like `game.example.com`? [12:28:20] no, i have a wiki (upgxwiki.com) and I have recently created an API for the game its made for to be able to view live leaderboards from in game on the wiki (api.upgxwiki.com) [12:28:26] although it is blocked by the CSP [12:31:21] I have filled out the CSP request form [12:31:33] but I'm unsure if I'm supposed to do that for this situation [12:32:43] Yeah, you are supposed to fill out a CSP Request. [12:34:13] Are there wiki specific CSP requests? [12:34:21] or is there only one for like [12:34:23] global [12:55:50] I'm not sure, you'll have to ask that in the ticket. [12:57:23] Is there a way for us at maille.wiki to push for https://issue-tracker.miraheze.org/T14053 to be implemented? we have someone in scope for our wiki who rendered several hundred models we'd like to use. [13:12:31] per #general though a tech eye to confirm would be best [13:14:50] would if be possible to add .glb to accepted formats, then, so we can write our own render? [13:18:39] does not appear to be a supported format but if that has to go through phorge it should at least be much quicker to process [13:28:08] was this enough? https://issue-tracker.miraheze.org/T15103 or do we need to say that we also want it? [13:42:41] Extension has not been updated in over a year by the looks of it [13:43:47] On first look doesn't appear to be anything nefarious or what not though [13:58:39] [1/2] this should be enough, it is possible it simply fell through; I don't generally encourage bumping because that creates a whole mess since everyone wants something and it collapses quickly into noise, but in this case I would say it might help to put a status update; we are still interested, we would like the extension but this option would solve our needs for now [13:58:40] [2/2] when you're available, something like that [13:59:19] and if someone does have words to say about that feel free to blame me for suggesting this, or note the topic came up in #tech on discord in advance [14:04:40] @raidarr like so? https://issue-tracker.miraheze.org/T15103 [14:05:39] I tried to explicitly frame against it being a typical bump, but I'll take the L for any confusion there, and that works [14:07:27] commented with additional context, it is now a wait game [14:26:21] I am sorry, I never submit things on phorge [14:28:39] Is this a good request? https://issue-tracker.miraheze.org/T15758 [14:53:09] yeah that sounds like it should work [14:53:48] that pull is otherwise a hacky fix which is probably harder than just making it a deferred update [14:57:23] nah you did well [15:03:33] Reading through the triage guidelines, I believe it to be medium rather than lowest. Is there anything I can do? [15:04:40] it should only be determined by current tech, who may weigh in abstract terms relative to what else is going on that needs to be dealt with [15:05:20] it is kind of sucky to have your concern be slapped on lowest as a user but the feature is essentially there for tech purposes and there's little a user can do with that [15:10:13] Oh? The same person who uploaded is the same who triaged? [15:19:02] oh if you're saying tech didn't touch that at all then what I'll do is update to needs triage [15:21:05] updated, which will also put it in a pretty visible queue that if someone can clerk it then and there it may be seen faster [15:56:57] tbh I never set anything lower than medium [15:58:53] The privacy policy and data protection bits are there for data that the service collects about the person using the API, not the source data. eg, a privacy policy is needed so I know if my personal data (IP, user agent, etc) is being recorded, for long, how it’s being used, etc [15:59:17] oh, it collects nothing [15:59:22] absolutely nothing [15:59:34] other than the stuff the cloudflare collect themselves [16:00:11] Good to know, but that’s the kind of info that needs to be included in the privacy policy or equivalent, so we can know that as part of a review [16:00:32] ohhh alright [16:00:47] i mean im currently unable to add a privacy policy [16:00:55] but ill see [16:10:16] even that clarification could be useful to edit in [16:15:35] It explicitly avoids a code path that breaks during wiki creation, and other code paths should proceed as usual. The only issue is that it is too hacky. Will probably use deferred updates as OA suggested. [19:22:38] [1/5] @atxatx @posix_memalign I've made a PR for new Citizen configuration, just some questions about the options I haven't done: [19:22:38] [2/5] - wgCitizenCompat/wgCitizenPreview: I'm assuming I don't touch these [19:22:39] [3/5] - wgCitizenEnableManifest/wgCitizenManifestOptions: are these relevant? [19:22:39] [4/5] - wgCitizenEnableShare/wgCitizenShareMode: does ShareMode rely on EnableShare being enabled [19:22:39] [5/5] - wgCitizenEnablePreferences: what does this actually do? [19:23:03] Forgot to link the PR: [19:24:30] oh also `$wgCitizenThemeDefault` might need to become a text field with citizen's new theming system, or could that just be done with preferences.json? [19:39:43] Yes for compat but preview should be available for wiki admins to enroll into the preview channel [19:40:45] EnableManifest and ManifestOptions are for customizing the webapp manifest. They should be available to the wiki admin [19:41:56] Same for the share stuff as well. The EnableX config is just config options that allows admins to disable the feature entirely [20:25:44] Alright, I have updated it: https://issue-tracker.miraheze.org/T15758 [20:26:22] Preview should probably only be available after we get rid of the old compat CSS. I loaded legacy tokens for compatibility purposes. Loading it twice wouldn't hurt but that might break things when a wiki transitions to v4. [21:01:05] @pixldev would you be able to review this? [21:02:13] I can look at it sure but I'm not Tech proper and don't have the knowledge or authority to approve [21:02:27] alright! [21:03:01] who would be able to? [21:03:20] Still not sure what the reason for needing this API is though [21:04:18] we want to have a live leaderboard on the wiki [21:04:50] CSPs have to be revieweed and approved by a Tech Team member and then greenlit by the Director [21:04:55] and I can't just put this on the wiki as it will expose the api key [21:05:00] alright [21:05:26] Hm [21:05:44] and also [21:05:48] May have an alternative for yoh [21:05:49] there are rate limits [21:06:11] this will allow me to have greater ratelimits for the roblox api [21:06:30] because the api reached is mine not roblox [21:06:38] what is it? [21:07:33] https://www.mediawiki.org/wiki/Extension:External_Data, this extension lets you make HTTP requests and access the results in the parser layer or work with them in Lua. It also lets you set API secret keys in settings that isn't made public if I recall correctly [21:08:19] but this would make a request to the roblox api each time its called [21:08:32] instead of the like 1 api call per minute my api makes [21:08:49] You could point it to your API :shrug: [21:09:01] It also caches results [21:09:13] ohh [21:09:35] this is interesting [21:09:41] Wait actually thanks [21:09:48] so much I'll check this out [21:09:55] 👍 [21:10:17] Course, better for all of us if this works for you, saves both of us the review process, saves time, and is nicer for non JS users [21:11:36] can I access the data from JavaScript? [21:12:25] that's gotten from the extension [21:13:40] ED not really, it exposes data in Lua and wikitext, but you could access that with JS if you really want, put it on a page to access or load lua via js idk [21:14:47] alright [21:14:49] thanks so much [21:33:38] @pixldev so I went to go enable it and it says I need managewiki-restricted? [21:34:11] Oh, right [21:34:17] Forogt about that [21:34:38] [[SR/RC]] put a request here and ping me [21:34:39]

[21:36:36] gimme a few mins [21:44:45] @pixldev https://meta.miraheze.org/wiki/Steward_requests/Restricted_changes#Upgradex [21:45:02] There was a change already requested [21:45:13] so I just edited it to also include the extension [21:51:04] done [21:51:43] thanks [21:51:59] it doesn't look like ManifestOptions would be configurable with ManageWiki, but does this look correct for them in LocalSettings? [21:54:42] @abaddriverlol if you're free one of these days could to rereview https://github.com/miraheze/MirahezeMagic/pull/650 so we can merge and close the task [22:45:37] Yeah it's correct [22:48:15] Oops forgot to reply, yes it needs to be a text field now. The preference JSON doesn't govern the default theme since it is more render critical