[00:40:16] <MirahezeRelay>	 <blankeclair, replying to astor.pastor> dw, it's not bs
[08:35:08] <MirahezeRelay>	 <aeywoo> Can someone give me a backtrace from [T13483](https://issue-tracker.miraheze.org/T13483) plese?
[08:48:45] <MirahezeRelay>	 <astor.pastor, replying to blankeclair> 😭
[08:49:55] <MirahezeRelay>	 <aeywoo> @blankeclair we're not allowed to disable `$wgNativeImageLazyLoading` for wikis are we?
[08:50:10] <BlankEclair>	 why not?
[08:50:27] <MirahezeRelay>	 <aeywoo> I'm assuming it could cause server load issues since it's not slowly loading all images for users rather its loading them all at once.
[08:50:59] <BlankEclair>	 hmm, good point
[08:51:01] <MirahezeRelay>	 <aeywoo> And per request by each user it could take up quite a bit of server load.
[08:51:03] <BlankEclair>	 dunno actually, try poking infra
[08:51:12] <MirahezeRelay>	 <aeywoo> `@Infrastructure Specialists`
[08:51:35] <MirahezeRelay>	 <aeywoo> @paladox what do you think?
[08:52:05] <MirahezeRelay>	 <aeywoo> This is the wiki that wants it disabled: https://scpclassified.miraheze.org/wiki/Anomalies
[08:52:14] <MirahezeRelay>	 <aeywoo> krab
[08:52:22] <MirahezeRelay>	 <aeywoo> a:crabrave:
[08:52:22] <BlankEclair>	 backtrace: retrieved
[08:53:17] <MirahezeRelay>	 <aeywoo, replying to BlankEclair> Could you purge all users skin preferences on that wiki of vector-2022 if you can please? Only if you want to or can of course.
[08:53:19] <BlankEclair>	 up to you to debug now :3
[08:53:22] <MirahezeRelay>	 <aeywoo> Don't wanna burn you out anymore.
[08:53:30] <MirahezeRelay>	 <aeywoo, replying to BlankEclair> :NOOOO:
[08:54:02] <BlankEclair>	 it's usually triggered by hiding a setting that is depended upon by `hide-if`
[08:54:29] <BlankEclair>	 typical culprit is hiding `skin`, since vector-2022 preferences uses hide-if to only display if skin is set to vector-2022
[08:54:58] <MirahezeRelay>	 <aeywoo> Yeah, they don't have that hidden.
[08:55:13] <BlankEclair>	 up to your poor soul now <3
[08:55:29] <MirahezeRelay>	 <aeywoo> I'm gonna cryyyyyy
[08:55:33] <MirahezeRelay>	 <aeywoo> :puffer_cry:
[08:55:43] <MirahezeRelay>	 <aeywoo> Oh well, I'm sure it's something stupid.
[08:57:39] <MirahezeRelay>	 <aeywoo> Oh, they might just have to reset default skin.
[09:32:50] <MirahezeRelay>	 <aeywoo> @reception123 [T9287](https://issue-tracker.miraheze.org/T9287) is reopened following three more requests for [Semantic Results Formats](https://www.mediawiki.org/wiki/Extension:Semantic_Results_Formats) to be installed.
[09:32:58] <MirahezeRelay>	 <rhinosf1> @aeywoo o/
[09:33:10] <MirahezeRelay>	 <aeywoo, replying to rhinosf1> https://tenor.com/view/miles-edgeworth-ace-attorney-capcom-gun-minigun-gif-25057292
[09:33:25] <MirahezeRelay>	 <aeywoo> Hello.
[09:35:32] <MirahezeRelay>	 <rhinosf1> @aeywoo you had Qs about lazy loading too
[09:36:36] <MirahezeRelay>	 <aeywoo, replying to rhinosf1> Yes I did, can we disable it for https://scpclassified.miraheze.org/wiki/SCP:_Classified_Wiki
[09:37:24] <MirahezeRelay>	 <rhinosf1, replying to aeywoo> If the use case is valid, sure
[09:37:48] <MirahezeRelay>	 <aeywoo, replying to rhinosf1> Well, per [T13502](https://issue-tracker.miraheze.org/T13502) the user is complaining about the lazy loading effect that is produced on mobile and such.
[09:38:37] <MirahezeRelay>	 <rhinosf1> It sounds okay so I think it's appropriate
[09:39:01] <MirahezeRelay>	 <aeywoo, replying to rhinosf1> Alrighty, I'll make the PR to add it to LocalWiki.php for their wiki, would you be okay with approving it?
[09:40:48] <MirahezeRelay>	 <aeywoo> Wait a second....
[09:40:54] <MirahezeRelay>	 <aeywoo> It's an option in ManageWiki.
[09:41:47] <MirahezeRelay>	 <aeywoo> It's not even enabled on their wiki, I wonder what they're talking about then.
[09:42:55] <MirahezeRelay>	 <aeywoo> But why is lazy-loading enabled on their wiki if it's disabled?
[10:00:52] <MirahezeRelay>	 <rhinosf1> Hmm
[10:26:03] <MirahezeRelay>	 <blankeclair> imagine if all they needed to do is purge the parser cache
[11:55:09] <MirahezeRelay>	 <aeywoo> @rhinosf1 are you available to do a quick test for [T13513](https://issue-tracker.miraheze.org/T13513)?
[11:55:52] <MirahezeRelay>	 <rhinosf1> What is the test?
[11:56:15] <MirahezeRelay>	 <aeywoo> merging and pushing a PR with a single wg override.
[11:56:24] <MirahezeRelay>	 <aeywoo> https://github.com/miraheze/mw-config/pull/5907
[11:56:53] <MirahezeRelay>	 <aeywoo> If it fixes it, I get to make an Upstream ticket. yay a:yaya:
[11:57:43] <MirahezeRelay>	 <rhinosf1> @blankeclair can @aeywoo bribe you?
[11:58:30] <BlankEclair>	 rhinosf1: nya?
[11:59:04] <MirahezeRelay>	 <rhinosf1> @blankeclair merge Aeywoo's PR and deploy pls
[11:59:09] <BlankEclair>	 ah okay
[11:59:40] <MirahezeRelay>	 <aeywoo> tank chu
[11:59:46] <MirahezeRelay>	 <aeywoo> :Tankzzzz:
[12:00:14] <BlankEclair>	 think we're gonna break prod?
[12:00:41] <BlankEclair>	 done and deployed
[12:00:57] <BlankEclair>	 and you technically don't need to bribe me
[12:03:48] <MirahezeRelay>	 <aeywoo> Puppet and Grafana are doing fine I see....
[12:10:01] <RhinosF1>	 Nothing is actually wrong
[12:10:07] <RhinosF1>	 They are just reminding us they exist
[12:27:35] <MirahezeRelay>	 <aeywoo> Alrighty, @rhinosf1 that fixed their problem, I should probably make an upstream bug with WM right?
[12:28:33] <MirahezeRelay>	 <aeywoo> All they did was `{{#tag:pre|test-{0}?}}` and that was escaping it which isn't what it was supposed to do, it was supposed to print out as `test-{0}?`.
[12:38:01] <RhinosF1>	 Ok
[12:40:15] <MirahezeRelay>	 <aeywoo> "Ok", you're fired.
[18:21:11] <MirahezeRelay>	 <songngu.xyz> Hmm, I'm thinking about an User Avatar Finder JS script for those wikis who uses UserProfileV2, but as far as I look into the script, the URL that it get the image from are really difference as of the way Fandom implemented user profile, compared to UPv2 as it have an pretty odd way of saving avatar images
[18:23:02] <MirahezeRelay>	 <songngu.xyz> Anyone have an idea on how we can have that working? More details here <https://dev.fandom.com/wiki/User_Avatar_Finder>
[18:30:09] <MirahezeRelay>	 <aeywoo> I wouldn't have a clue right now, but UPv2 pretty much just copies what Social Profile does.
[19:12:13] <MirahezeRelay>	 <originalauthority> No, there is no way in JS to get the avatar. Fandom exposes that information to JS because the entirety of the Fandom profile is written in JS. I haven't needed to access the avatar from JS so that hasn't been implemented.
[19:12:45] <MirahezeRelay>	 <originalauthority> But the filename will be avatar-<USERID> so you can do with that what you will
[19:13:04] <MirahezeRelay>	 <originalauthority> (although constructing your own file path is dependent on knowing the file path allocated to the repo group
[19:15:53] <MirahezeRelay>	 <originalauthority> Notwithstanding, if you're looking to be able to show the avatar on a page it would be preferable to use a parser hook rather than do it in JS. Maybe I can add that
[19:42:37] <MirahezeRelay>	 <pixldev, replying to originalauthority> Remind me how parser books work again
[19:42:49] <MirahezeRelay>	 <originalauthority> parser books?
[19:42:54] <MirahezeRelay>	 <originalauthority> my favourite kind of nbook
[19:43:10] <MirahezeRelay>	 <originalauthority> I meant parser tag though lol