[04:10:02] <MirahezeRelay>	 <posix_memalign> [1/2] Agent tracked MW updates on pages such as  https://meta.miraheze.org/wiki/MediaWiki/1.43. Something similar could be done on meta? It could also use MH Monthly's talk page delivery infrastructure. 
[04:10:02] <MirahezeRelay>	 <posix_memalign> [2/2] Speaking of extension updates, should we notify affected wikis about `Extension:YouTube` going away soon? I imagine some users will be very unhappy when that happens eventually without notice. I could try the talk page bot on [T14037](https://issue-tracker.miraheze.org/T14037) on a small scale (e.g. only deliver messages to bureaucrats of highly-active wikis).
[06:40:38] <MirahezeRelay>	 <rhinosf1, replying to posix_memalign> Yes
[06:41:03] <MirahezeRelay>	 <rhinosf1> Extension:YouTube is replaced Drop in with EmbedVideo
[06:41:25] <MirahezeRelay>	 <rhinosf1> We'll switch EmbedVideo on when YouTube is switched off I imagine
[06:41:35] <MirahezeRelay>	 <rhinosf1> Probably immediately before the update
[07:28:00] <MirahezeRelay>	 <cosmicalpha, replying to rhinosf1> It could really be done whenever. I just chose to do it with the upgrade to give us time for the transition even though its drop in.
[07:29:06] <MirahezeRelay>	 <cosmicalpha> I plan to do it a day before the upgrade at the latest as to not have to deal with it during the upgrade also.
[07:29:38] <MirahezeRelay>	 <cosmicalpha> And at current I am planning for the upgrade first week in September.
[07:31:17] <MirahezeRelay>	 <cosmicalpha> But thats if Cargo works. As that one is indeed a blocker.
[07:31:24] <MirahezeRelay>	 <cosmicalpha> I think it might the only blocker left.
[07:33:05] <MirahezeRelay>	 <posix_memalign> [1/2] SMW is still untested btw. It would be nice if someone can upgrade it on mirabeta and then enable it on https://smwtest.mirabeta.org/wiki/Main_Page. 
[07:33:05] <MirahezeRelay>	 <posix_memalign> [2/2] Wikibase repository is also untested due to error 45 in [P554](https://issue-tracker.miraheze.org/P554), but I don't think many wikis are using it.
[08:19:34] <MirahezeRelay>	 <abaddriverlol, replying to posix_memalign> Done
[09:26:10] <MirahezeRelay>	 <rhinosf1, replying to posix_memalign> Is there an upstream ticket for wikibase?
[09:42:32] <MirahezeRelay>	 <posix_memalign, replying to rhinosf1> I'm not sure if this is an upstream issue or not. @abaddriverlol looked into it before and might know what caused it.
[09:43:07] <MirahezeRelay>	 <abaddriverlol> https://discord.com/channels/407504499280707585/808001911868489748/1403474699236675655
[09:43:48] <MirahezeRelay>	 <abaddriverlol> I doubt this is an upstream issue as Wikibase should work fine with 1.44 as it's WMF-deployed
[10:01:40] <MirahezeRelay>	 <songngu.xyz> Uh guys, I can't upload new avatar to my user: <https://100bangai.songngu.xyz/Th%C3%A0nh_vi%C3%AAn:Pisces>
[10:02:18] <MirahezeRelay>	 <posix_memalign> [1/3] Looks like Semantic Drilldown is still incompatible with 1.44.
[10:02:18] <MirahezeRelay>	 <posix_memalign> [2/3] https://issue-tracker.miraheze.org/P554#L107
[10:02:18] <MirahezeRelay>	 <posix_memalign> [3/3] Basic SMW functionalities work, though.
[10:18:17] <MirahezeRelay>	 <posix_memalign> Same goes for Semantic Scribunto (error 47 of the same paste).
[10:48:42] <BlankEclair>	 is proceededing w/ https://issue-tracker.miraheze.org/T14148 okay? footer of that wiki says "This project is not affiliated with Digital Extremes, All rights over their art and imagery is reserved by them"
[10:52:44] <MirahezeRelay>	 <pskyechology, replying to BlankEclair> i see no issue as the wiki is about their video game and usage of video game materials (incl. art and imagery) in wikis usually falls under fair use
[10:53:13] <BlankEclair>	 okay, i'm putting you at fault if we get into legal trouble /j
[10:53:40] <MirahezeRelay>	 <pskyechology> D:
[10:54:19] <MirahezeRelay>	 <pskyechology> or if it doesn't fall under fair use, it falls under "why the hell should we bother when you aren't making money off of this"
[18:37:30] <MirahezeRelay>	 <functiondj> are there resources for improving page load performance?
[20:26:18] <MirahezeRelay>	 <rhinosf1, replying to functiondj> It depends what you think the issue is
[20:26:28] <MirahezeRelay>	 <rhinosf1> There's stuff you won't be able to control
[20:30:19] <MirahezeRelay>	 <pskyechology> [1/3] for the frontend it's basically just
[20:30:20] <MirahezeRelay>	 <pskyechology> [2/3] 1. avoid loading huge images
[20:30:20] <MirahezeRelay>	 <pskyechology> [3/3] 2. avoid loading costly scripts
[21:20:41] <MirahezeRelay>	 <functiondj, replying to rhinosf1> https://cdn.discordapp.com/attachments/1006789349498699827/1407111988877725917/DE3E259F-379B-4A09-9C2C-72869A27359D.png?ex=68a4eaa9&is=68a39929&hm=0dee78d4d952f7ebb703a2e2a077c4a46ee4e80ffe2039c96d14bdb90b1bc303&
[21:21:37] <MirahezeRelay>	 <functiondj> looking at the network tab, it seems to be like optimizing backend processing somehow could yield the most benefits across the board.
[21:25:05] <MirahezeRelay>	 <rhinosf1, replying to functiondj> Likely 0 you can do about that
[21:25:48] <MirahezeRelay>	 <functiondj> oh :( unfortunate
[21:25:53] <MirahezeRelay>	 <functiondj> but thanks for replying
[21:28:38] <MirahezeRelay>	 <rhinosf1> We do monitor performance so it may get better over time
[21:29:06] <MirahezeRelay>	 <rhinosf1> Backend is more likely an us problem than a you one though
[21:30:05] <MirahezeRelay>	 <kockaadmiralac> Are you looking at it from incognito with no cookies to see how it loads for a regular viewer
[21:31:45] <MirahezeRelay>	 <functiondj> no, will try.
[21:32:22] <MirahezeRelay>	 <functiondj> [1/2] from incognito mode
[21:32:22] <MirahezeRelay>	 <functiondj> [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1407114927939784745/26A0C763-1A39-48C8-A195-C75F453DBA75.png?ex=68a4ed65&is=68a39be5&hm=02e6a2b02d2e877877bb336103de4ff1b56d2cf51be400afd2e35b81e73f216e&
[21:33:31] <MirahezeRelay>	 <functiondj> maybe slightly worse, but might just be random variance
[21:49:20] <MirahezeRelay>	 <rhinosf1> Worse is surprising
[21:49:23] <MirahezeRelay>	 <rhinosf1> I would expect better
[21:49:36] <MirahezeRelay>	 <rhinosf1> As logged out should benefit from more caching
[22:08:57] <MirahezeRelay>	 <originalauthority> (If you’re specifically interested in how fast the response is returned from the backend you probably want mw.config.get(‘wgBackendResponseTime’) which is probably pretty good and the rest is the browser rendering whatever is returned
[22:12:51] <MirahezeRelay>	 <originalauthority, replying to functiondj> ResourceLoader differing is weird
[23:16:29] <MirahezeRelay>	 <rodejong> [1/14] https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/HUMVKPDTDUSNAEP5YSRUYUGFLQJ7EPRI/
[23:16:30] <MirahezeRelay>	 <rodejong> [2/14] Breaking change: Removal of rc_type and rc_new fields from recentchanges table
[23:16:30] <MirahezeRelay>	 <rodejong> [3/14] Amir Sarabadani @ 18 Aug 2025 12:19 p.m.
[23:16:30] <MirahezeRelay>	 <rodejong> [4/14] Hello,
[23:16:31] <MirahezeRelay>	 <rodejong> [5/14] As part of improving performance and stability of the recentchanges table, we are addressing some tech debt. rc_new field was deprecated 13 years ago and rc_type similarly was deprecated 11 years ago. We are moving forward with dropping these columns in favour of rc_source field.
[23:16:31] <MirahezeRelay>	 <rodejong> [6/14] If you're querying rc_new or rc_type, please switch to using rc_source instead. They will be removed from wikireplicas in a week.
[23:16:31] <MirahezeRelay>	 <rodejong> [7/14] This would allow us to consolidate several different indexes on this table and improve performance of Special:Recentchanges and Watchlist plus simplifying MediaWiki code.
[23:16:32] <MirahezeRelay>	 <rodejong> [8/14] To follow the work, you can check https://phabricator.wikimedia.org/T400696 and related subtickets.
[23:16:32] <MirahezeRelay>	 <rodejong> [9/14] Thank you and apologies for the inconvenience
[23:16:32] <MirahezeRelay>	 <rodejong> [10/14] Best
[23:16:32] <MirahezeRelay>	 <rodejong> [11/14] --
[23:16:33] <MirahezeRelay>	 <rodejong> [12/14] Amir Sarabadani (he/him)
[23:16:33] <MirahezeRelay>	 <rodejong> [13/14] Staff Database Architect
[23:16:34] <MirahezeRelay>	 <rodejong> [14/14] Wikimedia Foundation https://wikimediafoundation.org/