[01:04:16] performance issues + security vulnerabilities [01:04:49] it's been mentioned a few times on this server. for instance, here: https://discord.com/channels/407504499280707585/407537962553966603/1550179535763406880 [01:05:08] and iirc, there's a tech proposal in drafting about moving wikis that use pageforms off of pageforms [01:46:49] Iyo, I do wanna know on what do you think how a viable replacement for PF would works like in your use case? [01:49:54] In Vocaloid Lyrics Wiki's case (the wiki Emiliers and I edit on), we never used PageForms and instead used a custom-made page generator hosted on GitHub pages and [[dev:PreloadTemplates]], even before we moved into Miraheze. [01:49:55] [01:51:52] Can I take a look into the page gen site? [01:52:44] https://ccxtwf.github.io/VLW-Page-Generator-v3/#/songs [02:00:54] I do want an native solution that neither requires copy pasting a text wall or going out to an external site for this [02:03:04] There's https://www.mediawiki.org/wiki/Extension:MultiBoilerplate [02:03:18] And there's https://www.mediawiki.org/wiki/Extension:InputBox which has a preload feature [02:03:52] I feel like you could always make a gadget if all you want is a customizable form. [02:08:29] The customizable form part is perhaps the only place where PageForms cannot be replaced. VE's editor coupled with TemplateData does most of it but doesn't have feature parity. [02:09:06] And of course most extensions can be replaced with JS but the point of an extension is an easy way to do something with hassel. [02:10:37] I will wait for other discussion, thank you [02:11:01] @posix_memalign check Meta for new NextTide enrollment [02:15:36] The upgrade is paused for now and will probably resume when the sec release comes out. [02:16:12] i knew something will happen when zippy message me this early in the morning 😭 [03:09:04] The only blocker now is emails are broken. [03:09:59] We won't resume it until I do the upstream patch which I am planning to do tonight. [04:50:16] https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1371362 will fix that issue btw. [10:22:53] Can someone test and pull this PR if possible please: https://github.com/miraheze/mw-config/pull/6619 [13:31:36] [1/2] Talk abt PR, I want some review to this, since some styling tricks that I want to apply needs the responsive flag enabled in the skin itself [13:31:37] [2/2] https://github.com/miraheze/mw-config/pull/6618 [15:05:16] I remember Blue Archive Wiki was using a responsive version of Vector Legacy, it may be interesting how to look into that? [15:08:09] [1/2] Nope - we are all using the default non-responsive version [15:08:09] [2/2] Configs for it were removed at some point before I knew about it [15:09:45] [1/4] btw, something's wrong with dynamic category [15:09:46] [2/4] ``` [15:09:46] [3/4] Parse error: Unexpected: ?? on line 5 in MediaWiki:Gadget-dynamiccategories.js [15:09:46] [4/4] ``` [15:13:46] @posix_memalign you are the current maintainer of that one, so first of all, thank you; currently I just updated the gadget to uses the jsdelivr link and yea its not working now [15:46:56] Code on MediaWiki:Gadget- files can't use `??` because MediaWiki thinks it's too new and the sanitizer bugs out. However if you just have `mw.load(url)` on your Gadget page then it should work. [15:48:28] exactly what i had done, and not worked [15:49:30] I made some changes to the code alrdy, but thank you [17:47:32] [1/2] As ccxtwf said the new version is not intended to be copy-pasted directly into Common.js or a gadget. [17:47:33] [2/2] I'll adjust the linter on my end so that it's possible but the main way to load it is through jsdelivr. [23:16:56] Setting `target: 2018` on Vite is enough to downlevel TS, I think