[00:16:09] BlankEclair or MacFan4000 either of you on? [03:07:06] @pixldev I'm here [04:21:30] 3 days notice is required if there won't be full downtime. If there will be full downtime it requires a week. [12:23:51] interesting, today no outage at 12 UTC, the increased load is still there but not to the point where the servers die [13:05:54] @Infrastructure Specialists People have reported not being sent password reset emails - please investigate [13:06:17] opening a task is the best way to go about this imo [13:06:52] Any errors given in the reports or just don't have any email at all without any errors given on-wiki? But yes task is best. [13:07:45] No errors reported; all that's known is that password reset emails aren't being sent out [13:08:02] I'll investigate a bit later. [13:08:26] Not going to spam is it? [13:08:38] @cosmicalpha see mattermost pls [13:08:49] One user has reported that no email is present in the spam folder [13:08:57] I saw I'll be over there in a second again. [13:09:03] https://www.mediawiki.org/wiki/Extension:ContentTranslation [13:09:15] this ext needs an external server to be set up, but the example shown gives out one hosted by WMF [13:09:21] how are we with using WMF resources? [13:09:33] (and also, idk what the server does, it's not really documented that well) [13:11:58] If we need an external server ourselves it can wait till March but depending on how much traffic we send to it can we use theirs. [13:14:39] i hate how like [13:14:44] it doesn't document what the hell the server does [13:14:59] oh [13:15:00] https://www.mediawiki.org/wiki/Content_translation/cxserver [13:16:33] oh, declined: https://issue-tracker.miraheze.org/T13121#263199 [13:16:49] https://issue-tracker.miraheze.org/T13122 [13:19:21] Don't take that reason into account. It can be reconsidered if we can get the service or use Wikimedia's. [13:19:34] oh wow [13:19:40] but ye, i already commented your response on there [13:20:17] Things can change in 7 years lol. [13:20:50] more like 5.5 [13:21:26] I just checked the years lol. It's 2025 and was first declined in 2018... [13:22:16] Or its my 6:00AM brain doing weird things too and has woken up yet... [13:23:11] Also have a huge headache this morning... [13:23:17] oh wait [13:23:39] ah, i was going the the linked comment [15:45:52] Huh? [15:46:10] The temp passwords on account creation are single use ain't they [15:47:37] Can tech do a complete purge of a wiki’s cache [15:50:05] @tali64 what account? [15:50:10] Which cache [15:50:48] sexypediawiki, lots of pages with broken PI boxes that would need to be purged [15:51:24] Err ye [15:51:26] That's parser cache [15:51:38] Yeah thought it wasn’t CF [15:51:50] Is there a button to put it back in the microwave [15:53:55] Where do we keep that again [15:54:18] @tali64 https://issue-tracker.miraheze.org/T13122#263215 [15:54:22] Men [15:55:15] Right [15:55:51] wait, what about men? [15:56:10] Mem [15:56:33] BlankEclair: also ffs, there's a thing called a bedtime [15:56:42] Although saying that I woke up at 3am this morning [15:56:48] awfebawifebaiuwfbiawflawbiawbefuiawebf [15:56:52] So you could have just woke up like me [15:57:10] is it a good idea that i had coffee ice cream at midnight? ^^; [15:57:17] No [15:57:19] No [15:57:21] And no [15:57:28] why the three nos? [15:57:45] Because it needs that many [15:58:02] i was offered ice cream with a flavour that i liked :(( [15:58:19] Who is offering you coffee ice cream at midnight [15:58:23] I'd like a word with them [15:58:27] well okay [15:58:30] it was more like 10 pm [15:58:40] I'd still like a word with them [15:58:53] oh dear [15:59:00] we were having uh [15:59:02] a very late dinner [15:59:39] 15:59:26 ⇐︎ + BlankEclair quit (~BlankEcla@WikiTide/BlankEclair): Quit: Konversation terminated! [15:59:44] For the discord folk [16:01:18] Hazzah! [16:01:47] So no easy way to wipe? [16:02:09] It's very easy for tech [16:21:27] I thought the parser cache was stored in the database [16:44:56] Maybe we moved it [16:44:58] It might be [16:45:05] It was Memcache at a time [16:45:14] It's still easy to clear though [18:10:18] you can purge it with ?action=purge [18:12:29] the parser cache is stored in memcached, btw, not the database. [18:12:57] (backed by database backup) [18:15:27] I know that, this is a case where an entire wiki needs to be purged [18:15:42] Hence asking about wiping for the wiki [18:16:30] Well if its a PI, you can edit that PI and a job will be spawned to purge those pages from the cache I guess [18:16:38] Not ideal but can be done without tech intervention [18:17:09] Hm? [18:17:20] You mean editing the template should purge all pages that use it? [18:18:33] Pretty sure when a template is edited all of the pages its used on are queued for reparsing [18:18:45] (So that they reflect the updated parameters of the new template) [18:19:21] > The main ParserCache instance serves as a semi-permanent store of a wiki's content as seen by readers. The default ("canonical") rendering of the page is generated immediately when the page is edited, or when any template or other dependency of the output changes (see LinksUpdate). Output using different options is generated and cached on demand. [18:19:24] Yeah [18:49:47] Hm [19:18:27] Perhaps we could make an announcement like this, asking for more volunteers... [19:20:01] Hm? [19:23:37] For the rollout of temporary accounts? [19:24:06] if that's rolled out, it'll likely be sometime during the deploy of 1.44 [19:25:44] I meant to link to this one 😛 [19:28:54] [1/2] I thought it a good Idea to give some ideas where users can give specific help. [19:28:54] [2/2] For example volunteering in technical team, testing new features or mediawiki testing, etc. [19:29:50] When new users ask for roles, because they want to help, they often are ineligible. [19:30:05] we always shift the burden of local testing to local sysops \:P [19:30:06] but an announcement to alert sysops of any potential changes needed would be useful [19:30:13] But having a list of things we could direct them to would be nice [19:32:15] yep [19:32:16] for sure [19:32:22] like abuse filters [19:32:49] Miraheze maintained extensions might need an update but we'll see [19:33:03] it would be funny if an essentially IP user could request a wiki \:P [19:41:26] [1/2] Hmmm [19:41:26] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1332435110821363722/image0.jpg?ex=67953e65&is=6793ece5&hm=ec044e3a9205e9a3381b4157c26a65743272197e009d3ff4c7fde2cdd2642562& [20:22:32] theres really no need for that banner to be that big jesus [20:23:08] I can't even see it [20:23:16] I thought I did something wrong lol [20:23:34] I'll adjust it if it's wonky once I see it [20:24:36] Isn’t analytics already updayed [20:24:37] [1/2] man ... [20:24:37] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1332445979663663218/IMG_20250124_232424.jpg?ex=67954885&is=6793f705&hm=c57c879e13713f215ee44b847ad8eca49b393c31f2a93ddfd7e220bd76d68d22& [20:24:55] Hm [20:25:06] please make it more compact for phones [20:25:22] maybe hide the icon too [20:25:42] getting to fandom's level here lol [20:26:02] hmm, can I fit css rules in in-line CSS? [20:26:51] from my experience site notice works only w/ CSS applied from Common.css [20:30:30] nah it works from inline css [20:49:31] media query tho? [20:56:52] you can't inline media queries [22:54:38] a:waaa: [22:55:46] awaaa [22:55:49] awawa