[00:24:30] ????? [00:27:24] y u p [00:27:32] ill look and send when I get home [00:42:41] https://github.com/search?q=repo%3Aenwikipedia-acc%2Fwaca%20en.wikipedia.org&type=code sigh [01:20:45] @blankeclair so [01:21:00] https://cdn.discordapp.com/attachments/1006789349498699827/1364048310557741126/wtf.log?ex=6808407c&is=6806eefc&hm=6fbc894fe7d1607ed47819a6ca469e42108a0c1b7d15c05431713afed30109ac& [01:21:30] let me boot up wireshark to see exactly what the request its sending ti [01:28:17] huh, it seems to fail before sending an outbound request? [01:34:36] removing the oauth requirement lets me login, then trying to add an account via oauth to my tool account errors, but its getting a different page back in the error log? [01:35:11] No,still Main Page but an error [01:35:24] Likely sending something directly to en.wikipedia.org [01:41:31] wait [01:52:17] i think i have any idea [01:52:46] damn constraints [01:52:51] will try in the tmr [02:17:10] If you use Fedora, you could just install podman with dnf and then `alias docker=podman`. One less 3rd party repository to worry about. The CLI is pretty much identical, and my usage is basic enough that I have not found any disparities. [02:18:30] Ha, I do use Fedora actually, although at this point I left the Desktop app and just have the cli running fine [02:19:20] I think I need to change the domain in the database after looking at the source code a bit [02:19:27] will be so annoyed and confused [03:04:56] If you have a large wiki that has slow special pages like WantedPages or WantedFiles, what are you supposed to do to speed it up again? I can't remember other than using APCu or Memcached. [03:43:18] Podman > Docker [03:45:03] Not really much that can be done iirc, if there are that many pages. I know on Tardis Wiki when I was working on that the wiki was so big that WantedPages etc would time out and MediaWiki would close the connection before the result could be returned [03:45:26] Fandom seems to have some solution to this but alas it remains a mystery [03:46:13] Well, turns out the grabber scripts for images I used decided to skip 2,600+ files on the first run. [03:46:20] So of course that many entries just caused it to crash. [03:46:31] But now that all the entries are just Fandom videos, it doesn't seem to care and loads perfectly. [03:46:31] Are you grabbing from Fandom? [03:46:35] Yeah. [03:46:53] The grabbers are really bad for Fandom images, because Fandom's api will return blatant junk which will fuck the script up [03:47:17] Ie sometimes it will return a filename for a file that has been deleted and then the script doesn't know what to do when the file isnt where it is supposed to be [03:47:23] Well, I think all the images I've grabbed are fine, it's just that it grabbed Fandom video files. [03:48:50] Did you pass the --wikia flag? [03:48:57] That skips videos [03:49:05] Yeah, I did. [03:49:26] Sometimes these scripts like to ignore the instructions I give them. [03:49:31] Weird, maybe report it as a bug. Ciencia is really responsife for stuff like that [03:49:47] They haven't updated those grabber scripts since like 2020-ish. [03:50:21] At least I think they haven't. [03:50:35] They were last updated in 2024 [03:51:07] Theres probably a way more efficient way to do it than PHP. [03:51:11] CoughC#Cough [03:51:35] Maybe rust or golang even [03:52:25] Yeah, I ain't gonna mess with that. [03:53:16] Well, I'm using Weirdgloop's fork of the repo. [03:54:21] Which appears to be up to date and a bit more updated than wikimedia's version. [06:37:58] I honestly don't know what else to do with this ticket: [T13532](https://issue-tracker.miraheze.org/T13532), like how am I supposed to force myself to get a catpcha to test if this happens? [06:42:41] New account [06:42:57] Fairly sure it's a known bug though [06:43:48] Solution in that case be use internal not external links [06:49:27] This is a referring issue with Captchas, iirc last time it was Visual Editor? Or DiscussionsTools which was blocking the captcha? [06:52:15] No it's within just plain source editor on vector too sometimes [06:52:54] Must be a hcaptcha issue [06:53:12] It's a known bug [06:53:35] User should be using internal rather than external links though [06:54:12] Can someone upgrade the citizen skin for me please? [06:54:23] Not me [06:54:27] I'm still out today [06:54:31] @originalauthority [06:54:33] It's had some minor patches that are useful, and I wanna rule out debugging issues. [06:56:35] This is why we should give you beta shell [06:56:41] Then you could upgrade it yourself there [06:57:11] I might have a Driver's license by that point. [06:58:20] I don't have a problem with you getting beta now [06:58:33] It's isolated enough that accidental damage to prod is difficult [06:58:37] You can sign an NDA [06:58:42] Then we can mentor you a bit [07:01:54] Do I have to sign my legal name on that NDA. [07:03:21] Yes [07:06:09] Could be because the captcha provider (e.g. Google) is blocked, so captchas can't be fetched. I had similar issues in China where the website itself works but captchas don't. [07:07:12] Possibly, it could be similar to the ticket someone about BilliBilli videos being blocked due to CSP concerns. [07:11:58] Can someone also get me a backtrace for [T13490](https://issue-tracker.miraheze.org/T13490) please? [07:12:12] Who sees the NDAs, I'm assuming Miraheze has a legal officer? [07:13:34] It was @notaracham when I did mine [07:16:12] As long as only one person sees the NDAs then sure. [07:21:19] I'll poke the rest of the team [07:21:24] For opinions [07:21:47] Then tell you to file a task [07:30:26] Following on from this a month ago, Is there any reason a wiki shouldn't have [Extension:ExternalData](https://www.mediawiki.org/wiki/Extension:ExternalData)? [07:30:38] And why is ExternalData managewiki-restricted? [07:36:56] I guess maybe this is why: [T9246#187510](https://issue-tracker.miraheze.org/T9246#187510). [07:37:26] I guess maybe this is why: [T9246#187510](https://issue-tracker.miraheze.org/T9246#187510), but I wonder if the case mentioned here still applies to ExternalData today. @cosmicalpha what do you think? [07:40:31] I forgot I did that review lol [07:40:39] I can't remember exactly [07:41:40] Maybe we should do a new Security review? I'm sure the extension has changed a bunch in almost three years, any maybe we can take `managewiki-restricted` off of it. [07:42:14] Not entirely sure I'd feel completely comfortable completely unrestricting it... [07:42:25] Is it because of how it interacts with SQL? [07:42:47] Or the potentional RCE vulnerability from misconfiguration? [07:43:23] IIRC that was one primary reason. I think there was an RCE capability also but it depended on how it was configured and we always kept those disabled. [07:44:15] Well, I'm asking those two people why they want it on those two wikis, if their answers aren't good enough I might just recommend alternatives instead. [07:45:24] If there is no valid use or misunderstanding the extension for what they want they dont need it enabled. You can recommend alternatives but in reality the decision to enable restricted extensions is up to Stewards. [07:45:57] Mostly I just want to keep ExternalData not enabled on wikis unless exceptional circumstances and restricting it does that but Stewards can enable it as they desire to. [07:46:28] Yeah, which confuses me as to why Stewards told them to go to the Issue Tracker. [07:47:22] There may have been a mistake/misunderstanding/miscommunication here. [07:48:53] In which case avoid confusing the user by pointing them back to Stewards just ping Stewards to handle it so we dont throw the user for a whirlwind. [08:41:06] [1/6] ```php [08:41:06] [2/6] $wgVector2022DefaultSkinMode = "dark"; [08:41:06] [3/6] $wgVector2022DisableSkinPreferences = true; [08:41:07] [4/6] $wgVectorLayoutMode = "wide"; [08:41:07] [5/6] ``` [08:41:07] [6/6] Why aren't these options people can set via ManageWiki? [08:56:22] Good question [08:57:06] They can be added. [08:57:35] They are poorly documented for a start [08:59:41] (Also not listed in skin.json) [09:04:24] We love Vector. [09:04:32] I'll make the PR then. [09:04:44] Also, hello LoneWolf. [09:04:55] <__lone_wolf__> [1/2] no sure but is this not the same question and resolved? [09:04:55] <__lone_wolf__> [2/2] https://issue-tracker.miraheze.org/T13504 [09:05:15] Yes, I can set it via LocalWiki.php, but we don't need to do that for simple config stuff. [09:05:43] So, I'll make the PR to add it to ManageWiki and I'll remove it from LocalWiki.php, but I'll let the people know who had it set to configure it via ManageWiki instead. [09:05:55] For the record the ManageWiki upgrade should theoretically make it so the configs dont need to be in LocalSettings anymore as long as the override default matches the extension-defined default. [09:06:32] We have a script to migrate existing configs to ManageWiki [09:07:00] Ah, okay. So, if the value for something is by default true, but we want it to be false for security etc., we have to define it in `LocalSettings.php`? [09:07:10] Yes. [09:07:33] Alrighty, can you run that migrate script and merge the PR when I'm done please? [09:07:38] Are you sure these config variables are valid? I don't see them being used in the Vector repo at all? [09:07:46] They work. [09:07:57] Were they removed in 1.44? [09:08:01] Lemme check. [09:08:10] Not on the 1.43 branch. [09:08:17] oh huh [09:08:31] maybe they were removed in 1.43? [09:08:38] And no one noticed... [09:08:54] Not in the skin.json for 1.39 either [09:09:02] I know they existed at one point [09:09:14] Well, as far as I know they still work? [09:09:29] I don't even know anymore though. [09:14:33] Have you tested it? It seems impossible for them to work because the Vector skin never references any of those config variables. [09:15:18] I'm pretty certain they existed at one point [09:15:30] I can't test anything as a user. [09:15:53] But, when I made a local wiki on my server, it seems the config options didn't do anything. So, maybe they're provided by another extension? [09:16:03] They were never defined in extension.json for any branch, unless they were introduced in a patch version and then removed in a subsequent patch version. [09:16:10] Skin.json even [09:20:30] I have no idea lol. I remember I saw them a couple years ago somewhere. [09:21:05] Anyway it's 3AM so I should probably sleep a little bit. [09:23:03] <__lone_wolf__> [1/4] https://www.mediawiki.org/wiki/Skin:Vector/2022#Night_mode [09:23:04] <__lone_wolf__> [2/4] maybe this? [09:23:04] <__lone_wolf__> [3/4] ```$wgDefaultUserOptions['vector-theme'] = 'night';``` [09:23:04] <__lone_wolf__> [4/4] the settings i provided where given to me by another person saying that need to bechanged, maybe he was wrong... [09:23:20] Yeah, I set that value for another wiki recently. [09:23:26] So maybe that's what people got confused with, idk. [09:24:38] Also, `$wgVectorLayoutMode` does nothing. [09:45:06] <__lone_wolf__, replying to aeywoo> [1/15] Maybe this helps for the wide mode [09:45:06] <__lone_wolf__, replying to aeywoo> [2/15] found that this is controlling the width/standard i think... [09:45:06] <__lone_wolf__, replying to aeywoo> [3/15] when switching between standard and wide the value changes [09:45:07] <__lone_wolf__, replying to aeywoo> [4/15] ``` [09:45:07] <__lone_wolf__, replying to aeywoo> [5/15] "DefaultUserOptions": { [09:45:07] <__lone_wolf__, replying to aeywoo> [6/15] "vector-limited-width": 1, <-- 1 is standard, 0 is wide then? [09:45:08] <__lone_wolf__, replying to aeywoo> [7/15] "vector-page-tools-pinned": 1, [09:45:08] <__lone_wolf__, replying to aeywoo> [8/15] "vector-main-menu-pinned": 1, [09:45:08] <__lone_wolf__, replying to aeywoo> [9/15] "vector-toc-pinned": 1, [09:45:09] <__lone_wolf__, replying to aeywoo> [10/15] "vector-appearance-pinned": 1, [09:45:09] <__lone_wolf__, replying to aeywoo> [11/15] "vector-font-size": 0, [09:45:09] <__lone_wolf__, replying to aeywoo> [12/15] "vector-theme": "day" [09:45:10] <__lone_wolf__, replying to aeywoo> [13/15] }, [09:45:10] <__lone_wolf__, replying to aeywoo> [14/15] ``` [09:45:11] <__lone_wolf__, replying to aeywoo> [15/15] https://cdn.discordapp.com/attachments/1006789349498699827/1364175170255720559/image.png?ex=6808b6a1&is=68076521&hm=8e8dc803c63c1f07c804ba3aa53ec7748241286951095f3889a5940029cda475& [12:21:40] [1/2] To confirm, NDA paperwork is distributed and stored securely by the board secretary (me) [12:21:40] [2/2] I am the only one who can view by default, the only situation where that changes is if someone else becomes secretary or the extremely unlikely situation of a legal action. [12:29:33] [1/2] Regarding externaldata, stewards will pretty much enable it without question if asked. [12:29:33] [2/2] However it doesn't really have anything available via managewiki once enabled and we've had multiple folks ask stewards to do specific things w/r/t that extension that are tech domain. [12:30:43] The 'if you need additional help file a Phorge ticket' generic guidance is probably overbroad and suggested that they needed to do that to complete setup. [12:31:13] yeah, the rainverse wiki now heavily relies on externaldata, whilst not having a custom ED config [13:58:13] [1/2] :ThinkingHardMH: [13:58:13] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1364238869943550034/4bc2c50f-f931-43a9-94ac-3c8e6e6603ff.png?ex=6808f1f4&is=6807a074&hm=66fae4c70185e2463c8f2fbe946b542c478c6a065f99a609253c8d1f777fe26f& [16:53:12] is there a way to make images not hover on the infobox? [23:51:13] I deployed a new version of ManageWiki with a lot of validation work primarily targeting ManageWiki permissions and namespaces to ensure random problems are less likely to happen.