[01:03:44] [1/4] wanted to compare between miraheze and fandom on the main page [01:03:44] [2/4] rough [01:03:45] [3/4] https://cdn.discordapp.com/attachments/407537962553966603/1541251630325039146/image.png?ex=6a8ce9ef&is=6a8b986f&hm=490986d702ca55d93f5f1c5f864f6b44b8a729d73199976b34a268409c86c3e2& [01:03:45] [4/4] https://cdn.discordapp.com/attachments/407537962553966603/1541251630656397393/image.png?ex=6a8ce9ef&is=6a8b986f&hm=68b0704e19578f0fd8a4e027c83a0dfe51dd1337b0aeaf2565b79f9082d239d8& [01:04:12] 90 on accessibility I'll take it [01:04:50] (granted the seo is lying since fandom's is obviously better, but performance is definitely a LOTTT worse) [01:04:59] I do want to improve on our WCAG compliance, it should really be 100, but with so many options for customization it's hard to achieve. [01:13:02] tbf it could be slightly higher in that example, like 93-ish probably, our link color isn't 3:1 (like 2.7 iirc) [01:13:53] [1/3] the rest of the complaining from the site is just whatever bullshit's being pulled here and the banner image not having link/alt text [01:13:53] [2/3] https://cdn.discordapp.com/attachments/407537962553966603/1541254184974819378/image.png?ex=6a8cec50&is=6a8b9ad0&hm=c66df69c679f5ea02bb7f425ebda3da00470edc4d7bbf8a84fbb0ba5a50e5014& [01:13:53] [3/3] https://cdn.discordapp.com/attachments/407537962553966603/1541254185314689114/image.png?ex=6a8cec50&is=6a8b9ad0&hm=5576b419a7b4fa288182de2cf8c60558cc6374f3c660f2aca1ddb3f4f6acea7b& [01:23:14] [1/2] best I can do for now [01:23:14] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1541256536964206642/image.png?ex=6a8cee81&is=6a8b9d01&hm=e2c9e104b9ee9db6e4222b8dbb4859efa3c25a15e43046ecc96681ab8fe55797& [01:34:02] hey smallam.... check dms.... [01:37:00] i genuinely love https://meta.miraheze.org/wiki/Special:RandomWiki [01:39:49] Meh why do I have to fill out a form, I want an actual random wiki button. [01:40:27] When I was a kid, I created this "random web page" button. The algorithm was, get a random page on Wikipedia, then search whatever search engine had a free API (I think it was Yahoo search), go to like the 100th page of results, and get whatever was there. [01:40:28] almost ALL of these music wikis are using VECTOR 2022!!!! [01:40:35] I WANT VARIETY!!! [01:41:57] [1/3] complaining about an element that ISNT EVEN THERE [01:41:58] [2/3] https://cdn.discordapp.com/attachments/407537962553966603/1541261249306824826/image.png?ex=6a8cf2e5&is=6a8ba165&hm=5c1a6ec76e85e60c3828cc6be0efc082f546610613eee9f5cf1d915bcf730690& [01:41:58] [3/3] https://cdn.discordapp.com/attachments/407537962553966603/1541261249633849365/image.png?ex=6a8cf2e5&is=6a8ba165&hm=25519b8ff294aa5ea4029d0fb830885ba47fe025a9d85703fcb34fcae5ea8185& [01:42:13] oh it for SURE is there, smallam [01:42:17] mediawiki is likely hiding that [01:42:27] or timeless [01:43:29] it physically doesn't even exist in the DOM, it's complaining about something that doesn't exist [01:43:38] :iseeyoursoul: [01:44:11] whats dom again [01:44:40] document object model [01:44:44] [1/3] thank you mobile [01:44:45] [2/3] https://cdn.discordapp.com/attachments/407537962553966603/1541261950611357708/image.png?ex=6a8cf38c&is=6a8ba20c&hm=e63bc0dd393aadf0f5a7dfdf0b1ee3a5f615317e744dd87f5b71d861f227c5bd& [01:44:45] [3/3] https://cdn.discordapp.com/attachments/407537962553966603/1541261950925676595/image.png?ex=6a8cf38c&is=6a8ba20c&hm=c84c3871315425a3435dfb972b1bda9805a3771f4643d87edd189adee2f72991& [01:45:45] render-blocking time on desktop is 120ms [01:45:52] the DOM is basically the HTML of the page as interpreted and parsed by your browser, translated from linear text into a structured data object that can be manipulated. I think. Something like that [01:48:08] [1/2] I'm like 99% sure this is just the fault of mobile frontend probably [01:48:08] [2/2] you never stop wanting to beat mobile frontend to death with your bare hands [01:49:54] MobileFrontend is the bane of my existence. [01:55:16] Over a decade ago I had this wiki I refused to use MobileFrontend on so I hacked Vector to make it mobile-responsive, something they since added to the skin possibly before removing it [01:55:25] The new vector is mobile responsive anyway, solving the underlying problem [01:56:03] Like I just added a bunch of common.css stuff (or vector.css I guess) with media queries [01:56:40] then why do you still have it enabled [01:57:17] cuz I think timeless' default responsiveness kinda sucks ass but I'll have to double check that [02:01:23] so... Developer Tools? [02:23:41] [1/2] okay mobile frontend has nothing to do with it, it's just random lol [02:23:41] [2/2] sometimes I get like 76 and sometimes I get 94 [02:26:02] Got 97 accessibility by using a proper wordmark (was using a background image since I didn't know the wordmark field existed lol), would be 100 if the random void button didnt exist [02:26:11] [1/2] very nice [02:26:12] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1541272381677641789/image.png?ex=6a8cfd43&is=6a8babc3&hm=94183135a7c4519a38d82956445cce89db6a20b2c6b495f9fc26787c25aaa2e8& [02:35:43] Which tool is this? [02:45:16] https://pagespeed.web.dev/ [04:27:57] It might just be me but I'm feeling like the "Contents" tab on the right side of a page using Citizen skin lags the page significantly? [04:53:15] Backed up all the wikis I could that I still have [06:51:11] I was checking on a wiki that I reported that was rightly yeeted off of miraheze; now the miraheze is a redirect to their new hosting; is this something I can raise an objection to? [06:52:00] which wiki is this? [06:53:22] You are certainly welcome to raise your concerns, can't promise anything coming of it but depending on the situation you may want to consider emailing the [[Stewards]] [06:53:23]

[06:54:07] I suspect I know which wiki you're referring to but not sure [06:54:25] If it concerns a report that should be discussed less out in the open email is the best bet [06:57:21] Could I just use the report on the steward page I used before? [06:57:32] Eh [06:57:56] If the wiki on Miraheze itself is already removed, I don't think SR/WR is quite the appropriate venue [06:58:21] For requesting reconsideration, Sr/Misc is prob also fine [07:25:43] Is there a reason Special:ThemeDesigner isn’t accessible to anyone? (Specifically for Cosmos?) [07:26:35] Documentation says it’s supposed to be accessible to Admins, but not even Bureaucrats can seemingly touch it [07:27:23] [1/2] It also specifies that it’s supposed to create this special right for accessing it, but I’ve checked the list of available permissions and it just doesn’t exist [07:27:23] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1541348179168202842/image.png?ex=6a8d43da&is=6a8bf25a&hm=4b159ede55c9396d3606a05b10ebd48ffb0e52bfa1f74ed3ddde339f569ff087& [07:28:31] It’s not reconsideration, as much as, I don’t want to link. [07:43:16] It conflicts with ManageWiki, everything the ThemeDesigner does for Cosmos is available in ManageWiki. [07:44:38] Understandable [07:46:33] I’m trying to help with some ThemeToggle stuff and was told it was fine to poke at the main colors temporarily while I work on it [07:47:23] Thing is I’m not a Bureaucrat and therefore can’t touch the ManageWiki Styling tab [07:48:10] If ThemeDesigner was functional then it _would’ve_ given me the opening to do what I’m trying to do as an Admin [08:05:59] I will try and make it functional sometime in the nearish future. [08:06:52] I’m assuming there’s not a way to split up permission levels in ManageWiki right? [08:07:35] At least to reach the stuff in the Styling tab [08:08:25] No big deal, just curious [08:10:23] There is not currently [10:15:56] is the near future called "Remaking Cosmos from Scratch"? 🥹 [13:04:38] cosmos is uh fun [13:05:04] I'm pretty sure it's still broken if you remove echo-read-notifications permissions from a group unless someone fixed the task I made lol [13:18:16] Im working on more infoboxes for my miraheze wiki. I know that classic wikitext uses parameters (enclosed in triple-brackets e.g. {{{color}}} {{{height}}}} ) ..... but has anyone worked with TemplateData style parameters? I noticed this extension enabled on my Miraheze wiki (upon install) and wondered if it has any advantage over just your basic triple-bracket declared parameters: https://www.mediawiki.org/wiki/Extension:TemplateData [13:35:37] does anyone knows how to change the icon of the tabs of the wiki? I wanted to put the icon of the game instead of mirahezes logo [13:36:02] change $wgIcon & $wgLogo [13:36:26] if you're talking about the top part in the browser only [13:36:41] if you also want to change the miraheze icon in the sidebar you need to change $wgIcon and $wgLogo [13:37:04] lots of thank!!! [14:00:42] Sorry for the @ on relay but TemplateData doesn't change the way template parameters are used or formatted, it provides extended functionality to be able to select templates/parameters in the Visual Editor [14:19:40] @janebuzjane Yeah. Thats the impression I got was that it was more or less adding more to the visual experience of creating a page and giving values for the template/page's parameters. I do think about making sure things are user friendly (large variety in wiki editors/contributrs re: technical and visual learning) so TemplateData has that plus [14:21:09] would TemplateData add more "bulk" to pages/templates that use it?. I did notice a template/doc which I had imported into my wiki....and the /doc template used TemplateData parameters [14:22:26] [1/2] For sure; I enabled it on the wiki I admin and I'm currently in process of doing a template overhaul and trying to make sure all but the most complex templates have TD set up - we don't get THAT many editors and I hate VE butttt if it helps newbies then sure, why not [14:22:27] [2/2] I think there's a preference amongst those who know more about templates than I do that the TD table be on the doc page (instead of the template main page) so that there's less to retrieve when the template is invoked, yeah [14:24:00] Yeah. I can have a similar feeling about visualEditor (and WYSIWYG type editors, overall) . I mostly work in the source editor [14:26:28] sammeeee [14:26:32] " I think there's a preference amongst those who know more about templates than I do that the TD table be on the doc page (instead of the template main page) so that there's less to retrieve when the template is invoked." -- Ah, that makes sense [14:30:09] Also, how much are you punished on page load if you mix code languages? (For example, one of my templates uses wikitext AND Lua. For the /doc pages, that uses TemplateData parameters, that means I might have Lua, wikitext, and now Json (Template Data). [15:01:38] I would guess it depends on the string and what's loading, you could test it yourself and check with the parser profiling data. [15:08:17] biggest :true: of all time [15:09:30] cant even point people to the visual editor by default [15:10:02] because the edit button you can configure to do that is in the dropdown menu instead of the big edit source button on the skin [15:11:50] highly doubt the Single Edit Tab toggle is even going to be supported properly by it [15:12:15] Yeah no, just wondering, but how does one make an image thats not the first image on an article the image that shows up on the popup extension thingy thing when you hover over a link? [15:12:25] That was very convoluted and unspecific [15:12:28] My bad [15:16:34] [1/2] add `class=pageimage` to the image you want it to use [15:16:34] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1541466254416551986/image.png?ex=6a8db1d2&is=6a8c6052&hm=35e60e35c09856bcbed0c765ee6565c1002d67400fde77042b4b075c40ed26d5& [15:16:35] you can override it with wikiseo extension [15:19:29] yeah the automatic choice is also not exactly the first image always [15:20:09] it depends on how suitable for preview the first 4 images are seen by the algorithm [15:21:09] can you override the popup text with wikiseo [15:21:19] no [15:21:39] 😢 [15:49:25] Ah, gracias [15:51:16] Oh nice, it orked [15:51:21] Thank you very much [16:08:04] Indeed. [16:08:15] Yeah that will be fixed for sure soon. [16:08:50] tbh cosmos feels so outdated lmao [16:08:58] It is yes. [16:09:01] it should roughly match the new fandom skin instead [16:09:15] the fact cosmos is really narrow puts me off [16:09:20] It won't match it by default but it will have an option. [16:09:30] That is configurable... [16:09:37] There is a width config. [16:10:04] the fact the default is narrow is a weird choice [16:10:17] The default matches what the old Oasis did by default. [16:10:33] It's the exact same size as it was. [16:19:47] Cosmos LESS variables needs some work to fix the issue where it won't reject an invalid hex [16:21:33] i tried using cosmostweaks to resolve the dark mode issues since it had its own built in stuff [16:21:54] even though i prefer not to need to slap gadgets on like that [16:22:30] it was fine until i noticed the icons on the visual editor turned white but the actual bars didnt become dark [16:23:38] the person behind that gadget did a great job but i can not read white on white [16:31:34] [1/2] I don't think that splitting it up would do much for retrieval, but what it does do is separate the docs from the actual template. This means that A) if you want to edit the doc of a large template, you don't have to scroll down until you find the right line, you can just edit the docs and B) it means that when you edit the doc page, you're not invalida [16:31:35] [2/2] ting the parser cache of any pages that use the template (i.e. it is better for performance, just not in the way you imagined) [16:32:38] That makes sense! Esp the caching part, didn't think about that [16:32:47] I have learned to love a doc subpage [16:41:06] @janebuzjane: I love doc subpages. I wonder if there's a toolforge tool / script that can extract the template parameters and put them into a wikitable on the doc subpage? 🤔 [16:57:54] C) it reduces the expanded length of pages, which is also better in performance [16:59:01] especially for templates used very many times on a same page. imagine the entire doc content also transcluded that many times [16:59:22] you don't transclude docs when you use a template though? [17:48:07] Apologies again for the relay ping but the TemplateData editor will do its best to pull in the parameters from the template automatically so that all you have to do is add the additional info (like alias, label, required, etc) and then once you save it's automatically added as a table to the doc subpage [17:48:24] I don't think an external script would be necessary since it kinda does it for you (or tries) [17:51:59] i usually write json manually or make an llm generate the json based on the template content. clicking here and there repeatedly in templatedata feels awful and boring [17:56:03] @janebuzjane: oh, nice. I don't usually use the VE visual editor or TemplateData editor. I should play around with that more. Thanks for the tip. :) [17:56:43] * dmehus may just to learn to love TemplateData even more :) [17:57:29] @honoka55: true, good points [18:13:28] Random Q: The auto-complete for template or page names on Meta when editing pages, is that a CirrusSearch functionality or something else? [18:15:08] Isn't CirrusSearch an extension on enabled through request [18:15:20] only* [18:16:38] Correct [18:17:40] Huh [18:24:36] I think that's something else [18:24:53] cirrussearch only provides relatedpages and stuff [18:25:44] Hmmm, going to need to figure that out, it's an incredibly handy functionality that more of our org wikis need. [18:25:46] It's the new parser [18:25:52] Ohhhhh [18:25:57] er - "Improved Syntax Highlighting" in preferences [18:26:02] is it? [18:26:08] I thought it was wikieditor or something [18:26:19] [1/2] yeah [18:26:19] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1541514004634009630/image.png?ex=6a8dde4a&is=6a8c8cca&hm=a909d6d3331d1499f826139e110f30c89f863bbcba0de104c951e557cf6d4b5f& [18:26:37] yeah but it comes from something else [18:26:52] codemirror [18:26:53] that's it [18:27:06] Neat [18:27:11] ngl cirrussearch is my opp [18:27:13] in my testing it makes no difference the size of stuff inside `` tags [18:27:17] it's so much effort for barely anything [18:27:34] ah fuck I have to reindex because the script didn't finish [18:27:46] it's a feature of the syntax highlighter, also LinkSuggest does that if syntax highlighting is disabled [18:27:50] this time I'm nohupping it and tailing the output lmao [18:27:52] Partly why it's still restricted - it has a lot of features people ask for, but we need to deploy dedicated rsources for that [18:28:09] We did try LinkSuggest and found it much slower fwiw but it did work [18:28:15] idt opensearch actually needs that much [18:28:31] also you guys are drowning in compute compared to WO [18:29:52] our opensearch servers do sometimes get high load [18:30:22] and there's still the issue with japanese characters that I can't be bothered to find the link for [18:30:27] choose the factorio solution [18:30:31] if you don't have enough just make more [18:30:36] iirc these are the two main reasons why we don't have cirrus globally enabled [18:30:58] I think that's more a thing of the past, the main reason is that disabling it breaks search [18:31:19] Yeah, I could 100% be out of date on this, that recollection is at least a year old [18:32:14] i think that task is private [18:32:45] Phorge task? [18:32:59] ...What's your question? [18:33:46] wait what [18:33:54] I don't think that's any sensitive information [18:33:57] maybe [18:34:05] Ohhhh, it's available on Meta because LinkSuggest is enabled [18:34:08] i was searching for it logged out and dont see it [18:34:16] Thanks all, that was quite the dive [18:34:35] it is restricted yes @thewwrnerdguy [18:36:17] https://issue-tracker.miraheze.org/T14159 [18:36:37] Yeah, that one at least is public