[00:23:08] [1/4] Hey, can this task perhaps be moved to a higher priority? [00:23:08] [2/4] https://issue-tracker.miraheze.org/T13386 [00:23:08] [3/4] It has been two months since this problem has been occurring, and it is coming to a point where it is really frustrating. I know you guys are volunteers and are plenty busy; I completely understand and this is not meant as a complaint. It is just a very constant nuisance to numerous wikis, and probably damages how viewers perceive the wikis, so I just want to see if I can get more [00:23:09] [4/4] attention towards it. [03:22:41] keep forgetting thisbis open, if by chance someone wanna snipe feel free to lmk https://github.com/miraheze/CreateWiki/pull/605 [03:24:09] raising priority really won’t make it go any faster, especially if no one knows whats going on or has the ability to investigate [03:24:29] @blankeclair posted some logs i see, don’t suppose she’d have any idea? :/ [03:25:42] So then what is there to do if nobody knows what's going on? [03:28:53] Someone has to look into it [03:29:12] simple as that [03:29:35] And typically tech doesn’t have the time to look for these things much [03:30:55] Well, is that not the point of priority? [03:31:06] One task takes priority over another. [03:31:07] nope ^^; [03:32:01] So whenever tech does have the time, the things in high priority would be the intended first to do? [03:37:23] Not required [03:37:44] its an outline of what needs to be done and to get a glance of how important is this [03:37:56] If there’s something at Unbreak now [03:38:23] Yeaj you should work on that if you can, but even some tech folks wouldnt be able to help. Laxk of knowledge or needed access [03:46:14] Yeah, so a sort of encouragement. [03:46:34] Eeeeeeeeh [03:46:45] There is no good answer tnh [03:48:35] Hm. [03:49:01] If Claire does not know how to solve the issue, who else is there? [03:49:29] Assuming Claire is a more advanced member of the tech team. [03:52:18] she does more of these debug hunts but there’s othere [03:52:37] But everyone is busy with life or tech stuff [03:52:47] maybe @originalauthority eill have an idea but idk [03:53:01] It doesn’t have to be a tech person who looks into this likely [03:55:45] intermittent bugs are a bane of my existence [03:55:51] and i have that burnout recovery debuff [03:56:18] i now tentatively go on phorge to do low-hanging fruit [03:56:21] sometimes [05:28:14] I think the workaround suggested by @abaddriverlol would work really well. In fact, it should make styels work better because gadget styles are bundled in the initial page payload. `Common.css` is loaded separately after the initial page, which would introduce layout shifts. I'll try this on Strinova Wiki and see how it goes. [08:51:10] on an off topic note I'm looking at your main page fixes in a bit, thank you for the initiative [08:54:44] [1/2] I think I misunderstood the documentation. Gadget styles are loaded the same way as `Common.css` (in fact, they're right next to each other in the html page), so the only advantage is that the backend bug preventing `Common.css` from being loaded might not interfere with the gadget. [08:54:45] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1375758908383297576/image.png?ex=6832dad4&is=68318954&hm=6aada58a5854bb76be59a8266a5a51ad2f43db0f71e0de1eb9e63f79dbe31293& [08:59:04] Thanks! Now that dark mode is done the proper way, a lot of hard-coded colors would need to be changed to take it into consideration. It'll be a long and difficult transition, and hopefully MediaWiki doesn't push another update to throw us under the bus... [08:59:34] that's exactly what I'm concerned about while riding the vector 22 train for suer [09:00:46] one thing I just noticed about your draft is it is instead incompatible with the dark mode extension [09:00:53] a smaller use case but it would probably come up before long [09:01:11] but I'm a bit of a special unicorn and using dark mode extension + timeless at the moment [09:13:52] we could make an exclusion for that come to think, although I won't be able to dive into it until much later [09:15:12] I applied some fixes and it should work with the DarkMode extension now. [09:16:01] aha, so it does [09:16:24] the last bit I've noticed but not worried about (and is an issue on the original too with the extension) is the inversion used on the welcome to miraheze area [09:16:25] Links still look a bit odd, so maybe there's a better solution, but this is the best fix I can think of right now. [09:16:49] https://cdn.discordapp.com/attachments/1006789349498699827/1375764467161370635/image.png?ex=6832e001&is=68318e81&hm=61cd099b8e913a00e43e878e0847c874475eee49e5d57f7fef1f4ffcb4a73ee4& [09:16:56] I see what you mean on links too, not ideal but it can ride [09:17:21] [1/2] live page to compare [09:17:21] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1375764598803660853/image.png?ex=6832e020&is=68318ea0&hm=faace4786dd3f1efe6e229a22237f7e54f5fe0c33d7a98a1ccdabc388921dc35& [09:18:36] getting a darker background hue would likely straighten out the links but not sure how feasible that is without jeopardizing vector's dark display/normal viewing [09:19:55] I disabled inversion on the top banner. Now the button looks weird. Fortunately most people who click it won't customize the appearance too much. [09:24:14] I darkened the background for the first image, but links still don't look right. In both cases, their color is `#36c`, so I think they are victims of https://discord.com/channels/407504499280707585/1331711754845159554/1333174737538646046 [09:27:38] I think we're well into good enough territory on the button tbh although the image does pop a bit more than one might expect it to [09:27:49] [1/2] The colors used here is the same as the picture in the support thread: blue is getting turned into purple/a darker blue. I lost faith in the DarkMode extension after learning about this: it's an ugly hack that works, so I tried living with it, but then I learned that applying `hue-rotate(180deg)` twice doesn't yield the original color, yet this oper [09:27:49] [2/2] ation is fundamental to how the extension works... [09:28:36] darkmode is a terrible extension tbh, a bandaid for unfortunate lack of more convenient alternatives when a skin doesn't have that built in [09:29:02] but, is what it is still I suppose [09:29:27] it's a miracle I'm even testing other skins out much as I have a feeling they usually don't get factored in [09:29:54] but I do like a stable alternative to v22 [09:38:32] For some reason meta have a very large selection of skins, and the layout is broken in subtle ways for a lot of them, presumably because they aren't used or tested. This is not a new problem, though, since most editors use desktop computers, resulting in a bad mobile experience. [09:57:07] the only skins I would concentrate on are usable, not ancient built in defaults (monobook though it leans old, timeless, that might be it) and highly popular 'add on' extensions like cosmos [09:57:23] and ultimately despite its problems vector and even 2010 take precedence as flagship skins [09:57:53] but barring any further changes I can look at the main page again this evening, if there's any tweaks in the meantime those can join in too [14:58:30] I am breaking everything and no one is stopping me..... [14:58:34] :mozelle_stare_look_eyes: [17:04:23] I thought that was your job [17:06:22] Yeah.... but its just not the same this way. [20:17:26] did anybody have the idea yet to send discord notifications via a job instead of synchronously while saving a page edit? [20:17:55] on my local installation, discord notifications delay edits by about 0.4 seconds per webhook and I imagine it's similar on miraheze [20:20:16] or would the overhead of jobs be too high? [20:24:18] I mean 0.4 sec seems fine tbh [20:24:28] i'm not in tech tho 🤷🏽 [20:27:04] i don't know how many webhooks are registered by default but #global-wiki-feed is probably default for all wikis and if you add one or two custom ones each action is delayed by about 1s [20:27:35] which ofc is not terrible but in total it consumes more time when you are making lots of edits [20:34:20] I had this done at one point no idea why I didn't push it lol I really should... but maybe there was a reason I didn't that I can't remember... [20:36:58] Maybe using DeferredUpdates would be better then the job queue? [20:37:00] Probably a deferred updatr [20:37:02] Would be better [20:37:33] oh yeah same thing lol but yeah now thinking about it I think so too. [20:37:38] oh that's cool, I had no idea that existed [20:38:25] Deferred updates are nice