[00:44:18] @cosmicalpha when your free poke on commenting on the badges task [00:44:30] Oh right. [00:50:38] https://issue-tracker.miraheze.org/T15878#317275 [01:34:42] speaking of phorge badges, do we have one for Package Upgrader? [01:34:52] if so, we should award it to @orduin. :) [12:28:50] idea for new rff: enable edit recovery preference by default [14:53:43] It was also on my todo list alongside syntax highlighting: https://meta.miraheze.org/wiki/User%3APetraMagna/TODO [15:21:37] Another DB161 induced outage that resolved by itself. [16:47:58] [1/2] Final thoughts @notaracham @raidarr @pixldev @rhinosf1 I updated the welcome message and disabled GitHub login also to just make it straightforward with just Miraheze login since you can't use GitHub if you don't already have an account I figured that can also be confusing, though I can restore it if wanted. [16:47:59] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1540764481024692334/Screenshot_20260822_104517_Kiwi_Browser.png?ex=6a8b243e&is=6a89d2be&hm=c1196df13a47ad61346be9b855d61ee6373d4a4ff0d98fb81dcf7a4720cdd4c4& [16:48:35] I think it’s dandy to be able to login with GitHub as an option [16:49:15] My preference would probably be keep GH normal and miraheze big big [16:49:22] Again basically steal what zippy did [16:49:29] The issue is you can't login under most circumstances, so it is misleading for the average user. I can restore if wanted though. I left it able to link GitHub account, just disabled login. I can re-enable if wanted. [16:49:44] I use login with GitHub a lot so this would be really annoying [16:50:28] Let me see if I can allow it conditionally, or clarify it. [16:51:47] An alternative would be changing the text to clarify for users [16:52:48] @cosmicalpha I use login with GitHub a lot so pls keep that [16:52:58] Just have login with GitHub and MH, no local [16:53:34] So do I tbh, but I was trying to make it easier for normal users rather than just for power users who use GH. I can restore and clarify in message that you can't register with it though. [16:53:38] Mainly because I have multiple wiki accounts and only one GitHub so logging in with GitHub always gets me in [16:54:03] You can have the button say Login with GitHub and Login or register with Miraheze [16:54:05] Pretty sure [16:55:38] Yeah you can but that still doesn't clarify it in a way most would read. Give me one moment and I can do it. One reason I wanted to disable GH is then I can set it up so it will automatically log you in to Miraheze without any manual thing at all if you are logged in on wiki. But if that isn't something we want to do I will restore GH and adjust. [16:56:19] That is not something I'd want [16:57:16] It's a significant UX improvement on the local login with a weird mediawiki button with only have two SSO buttons and one actually says MH [16:57:22] I think that's much cleaner [16:57:31] Fair enough. [17:01:19] I restored it and https://github.com/miraheze/phorge-extensions/pull/75 will move the Miraheze button above GitHub [17:01:51] Cool [17:02:06] Second method is also good to login without needing shell when we are down [17:05:23] [1/2] How's that look now, including updated welcome message and everything else? [17:05:23] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1540768860272074915/Screenshot_20260822_110450_Kiwi_Browser.png?ex=6a8b2852&is=6a89d6d2&hm=9975d09f7728d9ab5a29a06de017d746e1600bb144025597c5cf994e0ac876f0& [17:05:51] Good [17:07:08] I think the task should be good to close now then? [17:07:24] I would agree [17:10:02] nice improvements all to the Miraheze Phorge UI. Much more intuitive for users :) [17:13:36] I really do hate that I had to do https://github.com/miraheze/phorge-extensions/commit/dff63c8e05deff72e746d3bff2f9786a2261a67c though. That should really be made easier upstream to make it actually use newIconView properly... seems almost like a bug tbh... anyway task closed out though. [17:13:39] dmehus: I annoyed myself into looking into it [17:13:54] And then cosmic finished it up because I went off on holiday [17:14:09] @cosmicalpha do feel free to groan upstream [17:15:17] I will probably do so on the task a bit later. [17:15:31] * on the upstream task [17:16:34] is it worth filing w/ phorge to look into? [17:16:44] Or at least asking in Conpherence [17:17:11] Yeah that's what I mean. I will make a comment to the existing task MacFan opened later and reopen the task rather than a new one I think. [17:17:38] Belated, but looks good to me [17:18:05] Right now I am working on getting speedscope launched for SRD, finally. I should have done that a long time ago. I will try and update the upstream task once I am done with this. [17:18:20] The only thing I'm wondering is if the GitHub login is for technology team only, whether there should be text there to indicate that? [17:18:38] Anyone can technically use it but most won't know that. [17:18:54] Right on, as long as it isn't walled off from any user, no need to clarify [17:18:54] Changing the order to emphasize the Miraheze one will probably be enough though tnh [17:19:04] Yep, I agree [17:19:40] We can explicitly clarify it if it becomes a real point of confusion though. [17:24:12] Is WO's phorge extensions public? I still really like this approach and would want to steal it for MH [assuming it doesn't rely on there only being one login option] [17:30:06] not atm [17:30:10] I will eventually make it public [17:30:26] or at least it might be public but I haven't updated it yet [17:33:11] didnt find it poking around GH [18:13:03] interesting, I've never had an issue with log in with mediawiki [18:13:56] I mean the issue is I'm not always logged into the account linked to than [18:14:06] As I have a few wiki accounts [18:14:18] But only one GitHub so I'm always logged into the correct of that [18:14:49] I have 2 wiki accounts and I use both of them though [18:15:10] although I do use Firefox containers to separate them [18:57:57] what was the progress for globally disabling `$wgRandomSelectionAllowUncached` again [18:59:49] https://issue-tracker.miraheze.org/T15351 [18:59:57] nobody has claimed it, so no progress [19:01:01] it needs a user notice probably before we disable it [19:01:37] we could also in theory patch the extension to add a parser warning or whatever if the attribute is set, but I'm not sure if that's worth the time or not [19:01:52] @posix_memalign do you think is completely able to replace this extension yet? [19:04:19] it looks like it theoretically would, esp. with the RenderBlocking, but obviously since I haven't used it I don't know all the cases where you would want the `uncached` [21:10:51] second only to going straight to the oauth upon visiting the login button, neat stuff. My compromise for other options would be a split screen for people who like the comparatively unusual alternate methods as opposed to them not being present anywhere [21:14:31] That was my goal and it can be done but there isn't consensus to do so so I went like this instead, and keeping GitHub as that seems to be desired. [21:18:06] if github is the second option with login with miraheze prominent enough then that is a functioning solution [21:19:10] Yep, that is how it is now. [21:19:27] I moved Miraheze above GitHub so it is the first option. [22:32:25] [1/2] If uncached is used purely to do random selection then yes. If the user wants to disable the parser cache in the first place then of course this would not be a replacement. [22:32:25] [2/2] TBH I haven't used it myself on the wikis I admin since the template was made purely to replace the extension. [22:33:26] should we really be accommodating the use case of actually wanting to disable parser cache [22:36:47] That belongs to the discussion for MagicNoCache and my answer would be no. UpdateDaily is a suitable alternative though.