[00:00:36] we reached 10k because of the big planned maintenance lmao [00:01:13] Event of the year [00:02:10] Just in general [00:08:22] You could replace all the content on every wiki with "We are doing maintenance at [time]" and people will still join asking about why it's down I think [00:12:24] big notice that says it in bright bold letters [00:23:07] -# I mean tbh... People don't really read much. [00:41:38] God if I ever want to create a website I'll have to make lots and lots of research regarding that [01:00:30] [1/5] no that's not how the template works. it adds everything in a single element like so: `{{Ruby|私はあなたに、このような現実への帰還を捧げます|エーセシノー・ディー・イラシアネズ}}` -> `私はあなたに、このような現実への帰還を捧げますエーセシノー・ディー・イラシアネズ/rt/ruby` [01:00:31] [2/5] Split these long ruby templates into multiple sections like this: `{{Ruby|私|わたくし}}はあなたに、このような{{Ruby|現実|げんじつ}}への{{Ruby|帰還|きかん}}を{{Ruby|捧|ささ}}げます so the` and the problem fixes itself (plus the annotations are probably aligned to the Kanji which did not happen previously) [01:00:31] [3/5] before and after shown: [01:00:31] [4/5] https://cdn.discordapp.com/attachments/407537962553966603/1501750541112574105/Screenshot_2026-05-07_at_7.57.37_AM.png?ex=69fd35ae&is=69fbe42e&hm=4e8ef3d10c849560240335a7e35621e285babd91ee26294696484b7f641b6fcc& [01:00:32] [5/5] https://cdn.discordapp.com/attachments/407537962553966603/1501750541481545908/Screenshot_2026-05-07_at_7.57.27_AM.png?ex=69fd35ae&is=69fbe42e&hm=579346c81eae641203a1efcc175b225ccd6ebb99d649baa377f022a96d08e4de& [02:09:34] So putting `* GROUP-SIDEBAR` in `MediaWiki:Sidebar` should the group sidebars there? [02:20:05] Hey guys, any easy way to reset group permissions to default values? Was fiddling with it and just ended up confusing myself so :p [03:51:11] Make the request on [[SR/M]] and we're happy to get those wiped back to default [03:51:11] [03:51:25] Ah thanks so much didn't know about that [03:54:59] is this the wrong channel for this sort of question? [04:01:16] We generally don't encourage soliciting paid work here, this is more of a general support channel for the Miraheze project [04:01:40] [1/2] The semi-official MediaWiki discord server does have a paid services section you might find useful: [04:01:41] [2/2] https://www.mediawiki.org/wiki/MediaWiki_on_Discord [04:02:28] thank you sir [04:44:03] <18.748.837.46> is the images issue fixed yet because using is now broken for me [05:00:03] [1/2] Is it feasible yo make tetris in miraheze [05:00:03] [2/2] Asking for a friend [05:00:25] Yes [05:00:42] h okay ill look on it [05:11:56] You could just use something like https://github.com/llop/classic-tetris-js. Recreate the HTML with JS and then load `classic-tetris.js`. [05:12:33] Thank you petramagna [05:12:37] Is there any template/way to insert a link to the user's own page? [05:16:58] Isnt it possible with [[User:(user)/(page name)]] [05:16:59] [05:17:03] [[Special:MyPage]] [05:17:04] [05:17:36] Ahh Special:MyPage is what I want yes [05:17:38] Thanks [05:21:02] another thing: is there a way to prevent case-based redirects (preferably not everywhere)? such as `/abc` redirecting to `/Abc` [05:23:15] It's the `$wgCapitalLinks` setting which is available on ManageWiki [05:24:46] Or $wgCapitalLinkOverrides if you want to set it per namespace [05:25:14] It'll make an entire namespace case sensitive [05:26:10] hmm.... alright. Not sure if a whole namespace would be suitable for this, but possibly (I've avoided creating namespace thus far but maybe this is a case where it makes sense) [05:27:18] I usually don't do that and just use displaytitle whenever a page is have to have a lowercase title [05:28:00] <18.748.837.46> [1/2] Is it possible to get pixel fonts such as terminal to render? i put it in the font-family field of html but it shows as times new roman or some similar font. [05:28:00] <18.748.837.46> [2/2] also i am looking for something explicitly pixelated rather than code-like such as consolas [05:29:05] it's a case where everything that fits this criteria ("be case sensitive") are all the same "type of thing" - maybe displaytitle works too? Not sure. I didn't quite wrap my head around that yet [05:41:54] <18.748.837.46, replying to 18.748.837.46> yo [05:44:52] Would recommend this as a #support thread, niche questions usually require an async response by someone not currently around. [06:38:54] Hi all, approximately how long does it take for a wiki to get approved? [06:59:47] The AI shouldn't take long at reading your initial wiki request [06:59:56] if it is approved, you can go ahead and start editing your new wiki! [07:00:27] if not, then you'll need to wait for a human volunteer to look at your request. the waiting time can be anything, from a couple of hours to like several days, give or take [08:51:23] <_arawynn, replying to simplex.ify> You're welcome. Usually it's between 2 and 3 days, depending on volunteer availability and backlog. [12:56:48] Me when brainfart [13:22:41] me all the time tbh [13:27:44] Hey... [13:28:26] [1/2] I'm incredibly sorry, but do you think I could have permission to move notifications like these down a little? The search bar covers the X to close them [13:28:26] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1501938764883165314/image.png?ex=69fde4fa&is=69fc937a&hm=e533d344ae37cbd660fadbbf1a17096d5ede948468da974c1194bf34ffd11b1e& [13:29:24] I'm pretty sure it's using the same placeholder as your regular site notices [13:29:39] Where is it located though? [13:29:39] So if you had a regular site notice it would've interefered with your styles as well [13:29:53] So yeah I don't think anyone would mind if you fix it [13:29:59] Okay [13:30:08] Since it was a miraheze system message in this case I wasn't sure [13:33:56] I can't find the template it uses, sorry [13:34:23] It's not a template, you'll have to move the sitenotice container down using CSS [13:34:28] Oh [13:41:07] Ugghhhhh!!! [13:41:23] The change didn't save?? Even after using ctrl+shift+R, it hasn't updated [13:41:58] [1/2] should look like this now [13:41:58] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1501942169060118688/image.png?ex=69fde825&is=69fc96a5&hm=d76775830d69d7e0526507ddd84bab197f8af886b14bcf78fcd57aa1941d7778& [13:43:06] Try ?debug=2 [13:43:08] Even after clearing the cache in my browser [13:43:19] That worked [13:43:23] What's going on then? [13:43:32] ResourceLoader cache [13:43:37] Give it a bit of time [13:43:47] Okay [13:43:56] Thanks [13:48:16] [1/2] I'll go ahead and mention that I put the search bar where I did in an attempt to fill some of the empty space left by the title [13:48:16] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1501943756528549898/image.png?ex=69fde9a0&is=69fc9820&hm=14c86104065a80502555e4db648c6ba910d7d4eb2bb87a3bfc93def2909d8acd& [14:09:28] what would be the procedure for taking action against unwanted edits? Someone apparently posted generative text that isn't accurate whatsoever, on my wiki's homepage. [14:09:47] Go to page history and click on the undo button [14:10:17] Right, but should I block them, message them if possible first, what's standard procedure [14:10:47] I'd message them first if they seem like a good faith editor [14:26:30] Being that they're not found in my server, should I just create a user page for them on my wiki and message them that way? I wouldn't know how else to reach out. [14:26:51] Leave a message on their talk page [14:26:57] Gotchya [14:48:22] The first comment on my wiki came out before I wanted to promote it) [14:53:11] Happens sometimes, not much to do about it [15:08:30] is there a way to make links case insensitive without having to make redirects [15:09:05] If you mean [[something]] --> Something, there's no need for redirect [15:09:12] [15:09:35] yeah but what about ``[[Something something]]`` -> ``Something Something`` [15:10:07] Ah yeah every subsequent letter is senstiive [15:10:28] I've thankfully not had any issues on my wiki for now, just slowly filling it up here and there. [15:11:24] There is a [SaneCase extension](https://www.mediawiki.org/wiki/Extension:SaneCase) which probably does what you want. [15:11:35] Would vanity titles (ergo`[[Something something|SoMeThing Else]]`) suffice? [15:12:32] i'm trying to cut down on those [15:13:02] I see. [15:13:12] thanks [15:14:33] oh i already have samecase enabled [15:58:26] [1/2] Is there a way to prevent Miraheze from automatically reformatting a redirected link? Like, I'm making a template automatically format both a link and category based on a single attribute. so i get this behavior even though the other one should say Missquito. Even though they both go to the same page, I want the categories generated to reference each of these entities individually [15:58:27] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1501976514378600539/image.png?ex=69fe0822&is=69fcb6a2&hm=a7d6454996fc53254f5dfa17e13cdf53c816328bbfd54f864f9e19be70939b32& [15:58:57] I even tried making the link [[Missquito|Missquito]] and that doesn't work [16:01:05] Do you have "Display Title Follow Redirects" turned on in additional settings in ManageWiki? [16:01:14] If so, turn it off lol [16:01:53] that was it. thank you. didnt know that setting existed. [16:02:09] I'm a FANDOM native so Miraheze is a learning curve [16:02:10] yeah, we had the same issue on our wiki when we first migrated [16:06:54] uhhhh...have you had the issue with it bouncing back and forth between the actual linked page and target page? [16:07:25] if i just sit here and click purge a bunch, it like flips between Mansquito and Missquito [16:08:01] ....or it would stop when i ask about it [16:08:09] caching issue maybe [16:09:36] it's probably cache? [16:10:26] we haven't had any issue with it displaying the wrong title since we turned the extension off, so it might just be taking a bit to actually register the managewiki changes on your end [16:10:49] i'll hope that's the case. thanks for your help [16:15:44] np! if you're still having problems after a while, feel free to ask again. i'm sure someone on the tech team will be able to figure out the issue if there is one, haha. [16:17:39] from what i know, this SHOULD be the fix so i'm going to give it some time. my real issue now is achieving a proper end result for this template [17:25:32] [1/3] So... $wgCapitalLinks can be set to true or false, by default. Having $wgCapitalLinksOverride unchecked for a namespace's settings means that it adheres to $wgCapitalLinks. Checking this box would force it to be true, regardless of the setting of $wgCapitalLinks. But there's no way to force it to be false, regardless of the setting of $wgCapitalLinks, is that right? (i.e. no way to s [17:25:32] [2/3] et `$wgCapitalLinksOverride[NS_ID] = false;`) [17:25:33] [3/3] https://cdn.discordapp.com/attachments/407537962553966603/1501998432498356325/image.png?ex=69fe1c8c&is=69fccb0c&hm=628a8e3ad0233ee4abb892cbf0a686ec33696e7a0eb61ee9b8f1d6cca8b62a2f& [17:36:14] @kacii can you file a task on phone [17:37:45] sure, any particular form I should use? [17:39:22] https://issue-tracker.miraheze.org/maniphest/task/edit/form/7/ [17:40:15] Someone is using a wiki they recently got up to impersonate me and to make it seem like I’m using the wiki to log IP addresses [17:40:28] [1/2] 🧌 [17:40:28] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1502002191551172668/IMG_6731.png?ex=69fe200c&is=69fcce8c&hm=568b0475483ac982f8d6dcbc72537ed35ceafe79957aad40dd17aa4e1a9b9aad& [17:40:41] The fact this isn’t even my wiki makes it funnier [17:42:01] Is it a Miraheze wiki [17:42:20] Yeah [17:42:31] https://moviestarplanet2.miraheze.org [17:42:41] So he's claiming you're doing things on Miraheze wiki that's not yours [17:42:44] And posting that on Reddit [17:42:49] And the main page is some stupid talk about me [17:42:52] yeah [17:43:02] I only own https://blockstarplanet.miraheze.org [17:43:40] I’m pretty sure I know who’s behind it, but that wouldn’t be in interest for you guys [17:43:46] @kiju1108 I think we might need a CU here then [17:43:54] That's just the latest edit though? [17:43:56] To see if the IPs being used are connected to anyone [17:44:07] like this guy is the vandal [17:44:18] The IP edits are vandal from a random range [17:44:21] It’s a deliberate act to make me look bad, though I’m very easily able to prove that I’m not the owner of the wiki [17:44:23] And the Reddit post seems just Reddit being Reddit [17:44:48] [1/2] I looked into the phorge request [17:44:48] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1502003279628996729/IMG_6734.png?ex=69fe210f&is=69fccf8f&hm=2562e96bad92d1ff94afbc9779e9b67ce01f53e79e3b9815ed0e471ddf34c1ed& [17:44:49] If a miraheze user is taking actions on Miraheze to make another look bad then I think we can step in [17:44:59] Can we move to #support though [17:45:02] Awesome then I really appreciate it [17:45:03] alright [17:46:17] why r u banned from the subreddit lol [17:47:05] That's #offtopic [17:48:09] that’s because of another very complicated situation, I’d be able to explain it to you in DMs not here since it’s long and off topic [17:48:20] dont worry im not that interested [17:48:23] https://discord.com/channels/407504499280707585/1502003983181680814 [20:54:05] Hello [20:54:19] Hi [20:54:36] Can I speak to someone about migrating from Fandom [20:55:30] What help do you need [20:55:45] Are you a steward? [20:56:04] I am not a steward. I am tech team. [20:56:52] Sweet, what is your advice for fandom software like message walls? [20:57:03] What is the best way to preserve that? [20:58:59] Have a look at https://meta.miraheze.org/wiki/Help:Moving_from_Fandom#Understanding_what_is_and_isn't_preserved_in_your_data_dump [20:59:25] Talk pages with DiscussionTools come a long way tbh [20:59:52] But unfortunately there aren't great message wall extensions [21:00:37] Sweet quick question, How to convert message wall content to talk page content? [21:01:03] No scripts I know of for that [21:01:29] I know WikiOasis does it I don’t know much more [21:01:42] Though I wonder if it's even legal to do it? Since message walls are not wiki content and may not necessarily be under the same license [21:01:59] @zipppee What do you do [21:02:20] I’ll have to look into that. [21:04:31] [1/2] Okay maybe it's just Discussions and comments that they restrict [21:04:31] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1502053540171087962/Screenshot_20260507_230410_Firefox.png?ex=69fe4fde&is=69fcfe5e&hm=e462e4a0218d009ec14ef15c1feeb7d2573e654650233b56e34ec8bcab9f8541& [21:24:35] I don't do it iirc [21:24:54] Does anyone do that on WO [21:25:15] I know some people just switched to DPLForum but I don't think we ever had a way to replicate message walls [21:35:03] Hmm then idk what ItsLido was referring to I guess [21:51:12] Theoretically couldn't be that hard right? Since they're just fetching it over API? [22:08:08] I guess there's the question of do they still automatically create Message Wall namespace pages for every user who has a message [22:08:19] And if not how do you find the users who have messages [22:10:19] And then there's the conversion from ADF or whatever the fuck to Markdown [22:10:43] And also HTML to wikitext for the prerendered posts [22:11:15] And then handle the indentation on talk pages [22:12:10] Warframe Wiki imported those so WG folks probably know how to do the export part. Wikitext conversion is harder and I [22:12:33] WF did it for comments [22:12:56] And yeah I mean pandoc is right there [22:13:16] It's not hard it's just a bit tedious and with some edge cases [22:13:42] Oh yeah that's right [22:17:01] So until there happens to be someone who is both very insistent on retaining the contents of walls of their migrated wiki and technical enough to understand the Nirvana API endpoints for walls, the models involved, and also talk page standards, I don't think we're getting a comprehensive migration script for those [22:17:22] Though maybe there should first be a message wall extension [22:18:18] Do wikis need them? [22:19:46] It's the second time I hear requests about them in like a month [22:20:53] DiscussionTools goes a long way I guess but the message wall interface is undoubtedly more familiar [22:21:37] I wonder if you could ride on whatever DiscussionTools is doing to build a Reddit-like interface for talk pages? [22:23:37] Interesting. Considering the initial reception /d got, it surprises me a little [22:23:57] Oh yeah, for user messaging, message walls were nice [22:24:29] Yeah message walls didn't really change that much on the user-facing side [22:25:02] The biggest complaint was that there's no wikitext which like [22:25:21] I've heard nobody complain about that post-migration tbh [22:25:57] Well I guess the existence of DiscussionsTemplates is a complaint in and of itself but [22:27:11] For Discussions I'd rather go with actual forum software and not MediaWiki [22:27:43] But message walls I guess make sense [22:28:02] Right, although that was a bigger issue for Special:Forum (and made some wikis stay away from it and keep using DPLForum). I don't recall ever needing wikitext for message walls [22:29:31] Probably, the backend is already there. Need some interface tweaks here and there so it doesn't look like a talk page. Could be a fun weeekend project [22:38:02] yeah it's not going to be possible to get something 1:1, especially when it comes to the opengraph stuff [22:38:52] OpenGraph is probably unimportant [22:39:07] You could generate those snippets on the fly [22:41:25] I'm more concerned about replies on message walls being linear like on most forums, whereas replies on talk pages are threaded like on Reddit or Twitter [22:41:39] it might be the case that someone e.g. links a youtube video which then creates an opengraph snippet, then removes the link but keeps the graph [22:41:44] So you have to pick a style and there's a tradeoff to both [22:41:50] but yeah probably not important for most cases [22:42:20] Hmm yeah I guess [22:43:20] [1/2] hmm ig comments/commentstreams could fill this niche [22:43:21] [2/2] or you could have replies unindented [22:43:54] what happened with flow, was that like reddit threading or was it like forum posting? [22:44:37] I think I remember it being forum posting [22:45:06] But I only viewed like 20 Flow posts in my life so I don't remember them well [22:55:06] I forgot that existed lmao [22:56:10] [22:56:21] Forum posting. Now that I think about it Flow is not too much from Message Wall? [22:56:52] Besides Flow being much worse in terms of technical debt. [22:58:04] E.g. https://www.mediawiki.org/wiki/Talk:Discourse/Flow [23:00:24] Wait no I think it had some sort of nesting on for example https://allthetropes.org/wiki/Forum:Wiki_Updates [23:03:02] Hmmm either Flow supported nesting or the wikitext converter inserted indents for back-and-forth conversations on its own. I lean toward the latter. It's surprising how much about Flow I have forgotten after undeploying it in January. [23:03:46] Oh boy do I have things to say about the pre-UCP message walls [23:05:52] I forgot the WMF had experimented with Discourse and went nooo did they take my extension name [23:06:00] I should document it sometime [23:07:44] Yeah there was some confusion with the Discourse extension request. [23:14:50] for some reason, our wiki never switched over to having message walls during our entire time on fandom. we had regular old talk pages up until we finally migrated last year [23:15:29] so the switch from fandom talk pages to DiscussionTools talk pages was a big step up for us just in general, and we never had to even worry about the message wall thing that seems to be common with fandom migrations nowadays [23:15:53] A lot of older communities were like that [23:16:45] I think it's probably because they refused to move to Message Walls when they were first introduced, because the editors were too used to talk pages, and it just stayed that way [23:17:20] I have two Fandom wikis I admin still use talk pages and they're both pretty old [23:18:19] yeah probably [23:18:44] though it also used to be a huge headache dealing with unsigned userpage comments [23:18:58] so glad we have discussiontools now to (mostly) prevent that [23:24:30] [1/2] I like DT so much that I'm willing to enable VE. [23:24:30] [2/2] DT is also the least used extension among those proposed for enabling by default in the recent RfF. [23:25:50] In the last RfF I think it was TemplateSandbox which was least used. Also because its usefulness is not widely known I think. [23:27:34] I never used it tbh [23:28:47] Wait how do you preview Lua module output then? With the Lua console? [23:29:48] I fuck around and find out [23:29:58] But yeah usually with the console [23:30:36] I feel like WWR said the same thing a while ago. Not sure if he still does it that way. [23:30:57] I thought breaking the entire wiki when you're playing with Lua modules is standard procedure [23:31:34] 7000 edits to the module page duh [23:31:42] Besides how would you test out a Bucket-using module if you don't deploy it immediately to populate your data [23:31:53] you have shown me the light of templatesandbox and I now bask in its glory [23:32:09] deploy the data-populating part first? [23:32:44] Yeah for modules with side effects it's not too helpful, but in readonly workloads TemplateSandbox works very well. [23:33:18] Yeah but that's also the part that can break the whole wiki lol the other one breaks a couple pages at most [23:33:59] I should check out TemplateSandbox [23:34:29] you can check it doesn't break the entire wiki though? [23:34:34] I was thinking about Produnto sandboxes the other day and how they seem limited in utility [23:35:20] or at least check a few pages [23:39:50] [1/2] VisualEditor is the most used non-default extension (excluding DarkMode which is a former default), but by the current votes it'll become a default soon. The next in line that we haven't discussed are EmbedVideo, TemplateData, UploadWizard, CSS, AdminLinks, ShortDescription, TabberNeue, EditCount, and Citizen. [23:39:50] [2/2] It's not obvious to me whether any of these will be a huge improvement to the new user experience. Either getting TimedMediaHandler out of deployment jail or making EmbedVideo a default will improve the audio/video-handling experience. And maybe some form of AdminLinks is helpful, though I know that the current version is seen to be lacking. [23:41:22] I really want to propose disabling MobileFrontend by default: just throwing it out there and watch the ensuing bloodbath. Maybe next time. We are running out of the "obvious" changes pretty quick and I expect future endeavors of this nature to be more controversial. [23:41:29] TemplateData isn't default???? [23:41:52] Nope. Looks like we can start another RfF right after this one lmao. [23:42:07] I guess since VE wasn't default but holy shit [23:43:48] TemplateData's parameter presentation has a lot of issues but even if you don't use VE you could make use of TD's parameter table if you don't want to build your own [23:44:22] if vector 2022 with responsive mode looks alright on mobile by default then sure [23:44:38] What's the difference between CSS and TemplateStyles? I guess the former doesn't have a sanitizer? [23:44:55] you basically need templatedata to make visualeditor more usable imo [23:45:20] [1/2] I rarely use TemplateData because I don't use VE. I also maintain very small wikis where I don't bother to document most templates: I know how to use something by looking at it and other editors can copy-paste. [23:45:20] [2/2] In general it could be helpful, though I've also seen editors misled by it and think they made a template when in practice they're only filling in TemplateData fields. [23:45:45] both have sanitisers, css allows you to write hte css directly on the page instead of having it somewhere else [23:45:55] afaik that's the main thing [23:45:55] Ah [23:46:42] i would support this. mobilefrontend kind of privileges a streamlined viewing experience in exchange for making it feel awful to edit on mobile. [23:48:27] tbh the mobile editor actually has a lot of improvements for the mobile experience over WikiEditor [23:49:04] It's more that MF hides a lot of other stuff that feels useful to editors [23:50:36] I was using the mobile editor on mw.org last month and previewing and saving changes is a lot easier [23:50:40] [1/4] I have some gripes about it. Let me look it up on phab. [23:50:40] [2/4] https://phabricator.wikimedia.org/T365631 -> pretty serious issue but it only happens when UniversalLanguageSelector is activated [23:50:40] [3/4] https://phabricator.wikimedia.org/T405314 -> more of a personal preference but the lack of mobile-specific padding annoys me [23:50:41] [4/4] There are probably many more issues. In general as long as WMF wikis still use MobileFrontend (all of them do except for WikiFunctions) Vector 2022 will have rough corners on mobile. [23:50:49] I wish we could bring those to WikiEditor [23:51:19] I guess we could submit patches [23:51:27] <_chrs_, replying to unai> it does have a sanitizer but I'm not totally sure if it scopes the styles to page content [23:51:48] I forget if we had to do many changes to the UT/DR skin to support mobile [23:52:44] The one from Extension:CSS is a lot less restrictive (operating on a blacklist that filters external urls) unlike TemplateStyles which checks your CSS based on a whitelist. [23:56:40] I believe neither issue is applicable to UT/DR. The first one doesn't apply because the UniversalLanguageSelector button is hidden on mobile. The second doesn't apply because the padding is 0.75rem instead of the default 1.5rem on narrow screens. [23:56:56] is this what you meant about the padding [23:59:12] The neat thing about our skin is that you can easily tell what exact changes we made [23:59:22] [1/2] Yep. I sent a [patch](https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/1191561) for it a while ago but it was deemed as not having a clear enough benefit. [23:59:23] [2/2] As long as Vector 2022 is not used on mobile by default I don't think this situation will easily change. Only a very small fraction of WMF readers have this use case due to MobileFrontend dominating WMF wikis. [23:59:27] The less neat thing is that it makes for some cursed development