[00:01:50] I think Miraheze is back :) [00:02:15] Yes we are coming out of readonly [00:03:31] interesting!! [00:03:35] [discord] ugh I swear every upgrade screws up the portlet menu formatting in some way or another [00:03:53] everything is usually screwed [00:03:56] [discord] i.e. this [00:03:56] [discord] https://cdn.discordapp.com/attachments/435711390544560128/986783146462806076/Screenshot_2022-06-15_20-03-47.png [00:04:07] I guess this is the point where I say goodbye to Miraheze for awhile. I wish you all the best. [00:04:27] there are a lot of things that are currently broken that I've observed [00:10:12] [discord] it always does that [00:10:15] [discord] its so annoying [00:17:06] [discord] ugochimobi: what all have you observed? [00:17:27] Images are broken in some wikis [00:17:27] Twinkle will be fixed shortly [00:17:35] I just gotta get onto the wiki first, it's loading so slow :( [00:23:19] Wait. Jesus Christ. Why is the default skin Vector 2022 now? [00:23:31] I thought we were just adding Vector 2022 not making it default! [00:23:35] @Zppix help save us!! [00:24:09] [discord] Legacy Vector is still around and will be for years to come [00:24:31] [discord] i hate vector 2022 [00:24:37] it was already available [00:24:41] [discord] it ruined every wikis css [00:24:55] [discord] We've been telling wikis to prepare for months now [00:25:21] [discord] Anyway, as usual, blame upstream \:P [00:25:42] [discord] I mean we could have just kept legacy as default [00:26:28] [discord] It's our commitment to always provide the most close to stock MW experience possible so we moved to V2022 as the default but users can always rollback easily [00:26:36] [discord] just 2/3 button clicks [00:28:08] [discord] arguably it would be better not to break most wikis' CSS [00:29:12] Agent : `It's our commitment to always provide the most close to stock MW experience possible` And that's why it needs to be vector and not vector-2022 [00:29:14] Glad we're in agreement [00:29:31] [discord] Vector 2022 is the default skin in 1.38 which is why we did that [00:29:44] stock mediawiki uses new vector as default [00:30:56] Ah okay, chrs made a random change to Twinkle code without telling me [00:31:05] That explains why it broke. Reverting change. [00:31:36] [discord] Naleksuh: no, I fixed it after the mediawiki upgrade broke portlet styling again [00:32:04] I already said I was going to fix it, why did you decide to change conflict me? [00:32:09] And when did you even get interface-admin permissions? [00:32:14] [discord] because I was also fixing MoreMenu [00:32:31] [discord] and I have Twinkle enabled so I knew it was affected [00:33:06] I will be making more changes to Twinkle in the coming minutes as well for vector 2022. Please don't remove those either [00:33:17] [discord] why would I [00:33:32] I dunno. Why did you already change it once? [00:33:56] [discord] see above [00:34:12] Naleksuh: read https://meta.miraheze.org/w/index.php?diff=238370&diffmode=source [00:34:16] [url] Meta:Administrators' noticeboard: Difference between revisions - Miraheze Meta | meta.miraheze.org [00:34:19] doug specifically stated twinkle [00:34:54] that is the provided link in the rights log [00:35:01] Oh, Arcversin is Chrs [00:35:21] [discord] yep [00:35:26] Yeah, I remember Arcversin requesting interface-admin for Twinkle and being informed that no changes were necessary. I didn't know Chrs was still them [00:45:38] And now Agent is edit conflicting me [00:48:58] [discord] on what? [02:25:15] @Agent can you please edit the meta main page to add a 1.38 upgrade news item? [02:27:11] [discord] MacFan4000: done, apologies for the delay [02:27:22] np, ty [02:33:27] That's not really news [02:56:03] Well we’ve considered it as such for years [04:42:49] Agent : Is vector-info-page a new 1.38 message? [04:42:54] Or rather, a vector-2022 thing? [04:44:07] [discord] Naleksuh: Yes, a new Vector-2022 message [04:44:21] [discord] It appears to logged out users to guide them on where to go for help [07:41:19] Hi, is it the right chat to report a bug? [07:41:49] Depends on what bug that would be. [07:41:58] Just post it and I'll review what specific type and where it's supposed to go [07:43:12] My wiki was set to "All righs reserved" licence before update, but it is now under "Creative Commons Attribution Share Alike" licence. In the settings it is still set as "All righs reserved". [07:43:26] What wiki is this? [07:43:38] tannenwald.miraheze.org [07:44:31] Hmm, yeah I see that. Interesting. [07:44:41] Try setting the license to something else then back to All rights reserved\ [07:45:02] already tried that [07:45:36] Weird [07:45:49] And you're doubly sure that the license is absolutely set to All rights reserved? [07:46:03] yes [07:46:06] even my second wiki historika.miraheze.org was set to CC-BY-NC and now is just plain Creative Commons Attribution Share Alike [07:46:22] seems like update messed something in licence setting [07:46:27] Alright. I will add that to the task tracker [07:46:36] Yes, Miraheze recently did a software update and that might have broken something [07:47:10] thanks for your help [07:47:50] goodbye [07:52:06] Leaving already? [07:59:11] I just triaged your task as UBN Naleksuh, that's a very serious issue. I'm mobile but I'll look first thing in the morning. [07:59:48] Is it that serious? It's just some text [07:59:58] I'm not a lawyer but I don't think it's binding if you didn't mean to license it that way [08:00:38] It's a licensing issue. I'm not sure on the legality either, but it definitely is serious. [08:08:31] I will re-triage it to "Unbreak Tomorrow Morning!" [08:08:32] Going to bed now [08:11:54] I'm working on it now from mobile. [08:12:17] Lol. I was just joking [08:12:21] Good luck, going to bed soon [08:15:33] https://github.com/miraheze/mw-config/pull/4764 might fix the issue. But needs someone else to check it, as I'm also going to sleep soon Naleksuh. Thanks for bringing that issue up though. [08:15:34] [url] Fix licensing by Universal-Omega · Pull Request #4764 · miraheze/mw-config · GitHub | github.com [08:58:58] Can't sleep-- looks like that PR is just moving stuff from $wgConf parameters to globals? [08:59:00] If that fixes it, great [09:38:18] Naleksuh: yeah that's what it does. The fact licensing uses wgConf has broken 2 other times before because it doesn't always read properly from GlobalSettings.php. This might be unrelated to the upgrade honestly, and rather another change I deployed around the same time to help performance. So it might've been my fault. [10:36:11] Hello Guest328! If you have any questions, feel free to ask and someone should answer soon. [12:47:07] [discord] Did something happen to the skipcaptcha right for bots? [12:47:27] [discord] Nothing should have, no [12:47:50] [discord] I'm being told by an editor that pywikibot and awb is having trouble with the captcha [12:48:13] [discord] We've tried turning the bot user right on and off, to no avail. [12:48:45] [discord] would it be possible their access reset at some point, or that some sort of permissions were reset at some point? [12:49:05] [discord] Might be worth checking what groups they're in at this moment and if they hold it, if they do and that's still a thing it might need to be reported on phab [12:52:44] [discord] We've tried removing them, then adding them to bots and it hasn't fixed it. And skipcaptcha is no longer listed as a permission in ManageWiki [12:53:21] [discord] I'll go get a phab ticket set up [12:53:43] [discord] cc on `skipcaptcha` not even showing ^ [12:54:06] [discord] hmm [12:54:16] [discord] [[Special:ManageWikiDefaultPermissions]] [12:54:16] https://meta.miraheze.org/wiki/Special:ManageWikiDefaultPermissions [12:54:19] [discord] [12:54:19] [url] Manage a wikifarm's default permissions - Miraheze Meta | meta.miraheze.org [12:55:02] [discord] and so it does [12:56:04] [discord] Yeah, the right disappeared completely [12:56:07] [discord] No idea why [12:57:44] [discord] Well now, this is an issue [12:58:09] [discord] Meta and global AFs also rely on people having skipcaptcha in their rights so this might cause some issues [12:58:24] To me it looks like no extension-specific rights are showing up [12:58:52] skipcaptcha would be part of ConfirmEdit [12:59:08] Others aren’t there as well such as nuke [12:59:21] [discord] You're right, I can't see any rights for extensions on Betaheze either [13:02:53] [discord] Well, the rights appear on Special:ListGroupRights but not ManageWikiPermissions [13:03:43] [discord] Strange [13:23:41] Opened https://phabricator.miraheze.org/T9398 [13:23:42] [url] ⚓ T9398 Extension specific rights don’t show up in managewiki | phabricator.miraheze.org [13:24:32] [discord] big 'oh dear' [13:26:51] We did a lot last night [13:26:58] Oh dear was the only likely result [14:42:31] How do you customize vector-2022, especially the logo, stickyness, etc.? [16:32:10] Hello. [18:41:36] I reached 900 edits globally. Nice to achieve that milestone before I leave Miraheze for awhile. [18:50:58] 12.88.141.146 is still editing [18:51:08] And appears to have made a "Hi people." edit yet again [18:51:50] won't be for long [18:53:58] Why's the at? [18:54:06] They were supposed to be blocked 16 hours ago but it didn't happen [18:54:30] [discord] because the RfC will be closed soon and their IP will be globally banned to enforce it [18:54:41] [discord] getting final input from void before I enact in full [18:56:47] @raidarr afaik even if bureaucratic the RfC can't be closed until 20 June [18:57:03] since the policy requires them to be open for 5 days [18:57:24] [discord] Is that a hard policy or is discretion allowed for circumstances, such as when the majority is apparent and the subject has consented? [18:57:39] [discord] I had thought it was the latter [18:57:42] [discord] > Requests for Comment must generally stay open for at least five (5) days. They can be closed before either if they are out-of-scope, malformed, or if it is clear that there is no chance of consensus. [18:57:52] according to that not really... [18:58:08] but given that the subject agrees I think an exception could potentially make sense [18:58:17] [discord] while I can make an argument on 'generally' I suppose it would be a flimsy bit to depend on [18:58:21] though in such cases it would probably be fair to require that multiple Stewards agree with such an interpretation [18:58:23] A certain supervoter whose name starts with d and ends with s frequently closes RfCs in less than 5 days.... [18:58:34] in that case those closes are incorrect [18:58:46] unless of course there is no chance of consensus which is a valid exception [18:59:12] [discord] Naleksuh I know who you're referring to, and I do think he should clarify on why he did what he did. [18:59:31] [discord] I suspect he would argue the latter and for the most part I do think they applied [18:59:38] [discord] It is rather obvious [18:59:46] [discord] It's Doug, obviously. [19:01:07] Yeah, though afaik all his closes would've in his view been within the exceptions [19:02:23] JohnLewis was concerned about it, as much as I've been concerned about his lack of activity as of lately (although I can't blame his work schedule or anything, as that would be rather silly). [19:21:33] How do you customize vector-2022, especially the logo, stickyness, etc.? [19:22:43] "stickyness"? [19:24:07] Apparently you can get the header (and search box>?) to stick to the top of a screen. Mine does not. There must be instructions somewhere, right? [19:25:40] Yeah [19:25:59] I want to explore the "benefits" of vector-2022 before reverting back to legacy. [19:26:11] There are none [19:26:17] Just revert now and you'll be fine [19:26:34] well that's your opinion, I'm sure some people like it otherwise it wouldn't have been adopted [19:27:16] as for the instructions I'm not sure where they'd be as I don't see anything useful on the main mediawiki.org page [19:27:52] I noticed that Meta has a logo on thier page. So someone knows how to do it... [19:28:52] as far as I'm aware no extra settings have been changed on Meta [19:28:56] CosmicAlpha: ^ maybe you have an idea? [19:29:48] It might just be the already existing logo and the SITENAME [19:30:07] [discord] Special:ManageWiki/settings -> Styling -> wgIcon and wgWordmark [19:30:29] [discord] There are a lot of extra settings to customize Vector's TOC, sticky header and such but they're not in ManageWiki yet [19:30:41] Our old logos did not migrate. The Meta logo looks like two very small images. [19:31:10] You have to use $wgWordmark instead of $wgLogo in ManageWiki I believe., or maybe $wgIcon, for the icon + sitename? I can't remember for sure. [19:31:13] [discord] ah, thats the icon [19:54:56] [discord] community ban is enacted [20:01:31] [discord] well [20:01:34] [discord] goodbye apex [20:01:35] [discord] :( [20:01:45] Agent get on IRC pls [20:02:29] Hi [20:08:48] Can you ban $a:ApexAgunomu [20:09:07] We do not need them coming back every 3 minutes either for "hi fuckers" or something about the wiki they are locked on [20:11:36] darkmatterman450 [20:11:59] Naleksuh Yes? :/ [20:12:12] I was just saying hi [20:12:17] Why ":/"? [20:12:18] Ah, I see. :P [20:12:28] That's because I was confused when you pinged me. [20:16:10] Naleksuh: IRC team thinks it's best to leave Apex unbanned on IRC for now. If they come back and keep spamming then it's an long or indefinite ban for her [20:16:39] I don't think it's best to leave them unbanned on IRC for now [20:16:52] Okay, it doesn't matter then, because there's no question they will [20:21:50] So far they've not behaved badly on IRC so for the time being they can probably stay on [20:22:03] but if there's any hint of spam/offensive messages they'll be banned [20:23:08] and "hi fuckers" would indeed count as something they'd be banned for [20:31:27] [discord] :/ seems to be something dmm always says [20:31:51] [discord] Obviously yes. :/ [20:31:52] [discord] [20:31:54] [discord] See what I did there? [20:32:02] [discord] It's the Matter Face. [20:32:14] [discord] something to add to my vocabulary thing [20:32:27] [discord] [[User:Bukkit/Vocabulary]] [20:32:27] https://meta.miraheze.org/wiki/User:Bukkit/Vocabulary [20:32:29] [discord] [20:32:30] [url] User:Bukkit/Vocabulary - Miraheze Meta | meta.miraheze.org [20:46:36] [discord] Hi. I'm having trouble logging into meta miraheze. After trying to login I'm presented with "No active login attempt is in progress for your session.". This also persists on different browser/in icognito. Any ideas? [20:49:30] That's weird [20:49:40] Agent: can you poke logs ^ [20:49:59] Looking [20:50:10] Someone else also reported similar issues earlier [20:50:12] Different browser / incog means it can't be cookie issue [20:50:20] Hello szczot3k! If you have any questions, feel free to ask and someone should answer soon. [20:50:24] [discord] On what wiki? [20:50:34] Agent: just search for the username [20:50:44] szczot3k: what's your on wiki username [20:50:57] Because it could be loginwiki at fault [20:51:00] [discord] meta.miraheze, on wiki username's the same (Szczot3k) [20:51:05] [discord] let me see [20:52:06] It _might_ be a problem with sign up, as I've just registered [20:52:58] [discord] `Failed to load session, unpersisting` [20:53:07] [discord] no trace for that [20:53:32] [discord] I broke mediawiki, great [20:53:34] [discord] before that, all I see is `Login for Szczot3k succeeded from IP` [20:53:39] Failed to load [20:53:43] That's helpful [20:53:48] Nothing else around that time [20:53:58] * RhinosF1 hates mediawiki logs for sessions [20:54:11] CosmicAlpha: any idea beyond clearing cache? [20:54:16] [discord] `Key "CentralAuthSource" changed` [20:54:25] Eh [20:54:29] [discord] ```from /srv/mediawiki/w/includes/session/SessionProvider.php(330) [20:54:30] [discord] #0 /srv/mediawiki/w/includes/session/SessionManager.php(676): MediaWiki\Session\SessionProvider->mergeMetadata(array, array) [20:54:31] [discord] #1 /srv/mediawiki/w/includes/session/SessionManager.php(544): MediaWiki\Session\SessionManager->loadSessionInfoFromStore(MediaWiki\Session\SessionInfo, WebRequest) [20:54:32] [discord] #2 /srv/mediawiki/w/includes/session/SessionManager.php(247): MediaWiki\Session\SessionManager->getSessionInfoForRequest(WebRequest) [20:54:33] [discord] #3 /srv/mediawiki/w/includes/WebRequest.php(837): MediaWiki\Session\SessionManager->getSessionForRequest(WebRequest) [20:54:35] [discord] #4 /srv/mediawiki/w/includes/session/SessionManager.php(168): WebRequest->getSession() [20:54:36] [discord] #5 /srv/mediawiki/w/includes/Setup.php(861): MediaWiki\Session\SessionManager::getGlobalSession() [20:54:37] [discord] #6 /srv/mediawiki/w/includes/WebStart.php(93): require_once(string) [20:54:39] [discord] #7 /srv/mediawiki/w/index.php(44): require(string) [20:54:40] [discord] #8 {main}``` [20:54:55] [discord] Do I get a reward, or at least something to put into my User: space? [20:55:03] You get a sticker [20:55:09] No idea how to claim it [20:55:19] [discord] I'll figure it out [20:55:42] Are you logging in from a custom domain or a miraheze sub domain? [20:56:06] [discord] Directly from meta.miraheze [20:56:38] [discord] (via: https://meta.miraheze.org/w/index.php?title=Special:UserLogin&returnto=Miraheze) [20:56:41] [url] Log in - Miraheze Meta | meta.miraheze.org [20:57:34] And did you ever try logging in from a custom domain prior to the issue? I have only one idea what could cause it if clearing cookies didn't, but my idea is only possible if you've logged in from a custom domain. [20:58:05] [discord] I'm 95% sure I've just created the account, directly via meta.miraheze [20:58:34] Hmm... [20:58:37] [discord] If you check the account creation date, and it's from ~1h ago, then it jumps up to 100% [20:59:07] And you did try clearing cookies? [20:59:32] Yeah, the usual stuff when troubleshooting that kind of stuff [21:00:16] I'm 100% sure I've just created the account, as I've received a confirmation email [21:01:16] Confirming the email _did not_ resolve the issue [21:02:01] Although I see a lot of cookies issues in the dev console [21:02:11] Such as: "Cookie “centralauth_Session” has been rejected for invalid domain." [21:02:22] that's bad [21:02:27] But how is it now invalid [21:02:34] That would 100% break a session [21:02:52] the ca_Session cookie is set for the ".miraheze.org" domain [21:02:58] it shouldn't be wrong, right? [21:03:20] ca_Session = “centralauth_Session” [21:03:57] [discord] entire error [21:03:58] [discord] https://cdn.discordapp.com/attachments/435711390544560128/987100242111520829/unknown.png [21:04:28] szczot3k: yes that's how it's been for years [21:04:58] They are all likely to cause what you are seeing [21:05:21] [discord] I can also provide the cookies dump, but I'd rather not dump them to a logged channel [21:06:30] [discord] best messaged privately to someone like rhinos if you do provide it [21:06:41] [discord] ikr [21:08:29] szczot3k: you can email them to security[at]miraheze.org [21:09:04] Or drop them in a key base message or something [21:09:12] We should probably have a GPG key [21:17:07] [discord] Although sending the cookies that I've currently have set (and send with every request) doesn't make sense [21:17:26] [discord] How would I check what are the rejected cookies? [21:17:33] Yeah, that's another problem with these custom domains [21:18:21] meta.miraheze isn't really "custom domain", isn't it? [21:19:26] No, the other domains [21:19:38] [discord] anything in .miraheze.org is not [21:19:44] And anything that's not is [21:19:49] I think we're wrapped up here [21:20:21] Yeah, but I'm not really experiencing a "custom domain" cookies problem here [21:20:31] [discord] my browser configuration can make custom domains a bit of a pain, but nothing I can't resolve quickly enough [21:20:37] [discord] and it does sound like this is a different issue entirely [21:20:52] This has nothing to do with a custom domain [21:21:03] And more than likely something that's changed in mediawiki [21:21:46] But if something changed in mediawiki itself, then I'm really surprised I'm the first to experience it [21:22:01] session logic is a mess [21:22:11] It's not uncommon for it to do weird stuff [21:22:12] [discord] the upgrade wasn't long ago, you might just be one of the first if it's a wider issue [21:22:22] And people don't always report issues [21:24:19] So just lmk if there's anything I can help with. I can do some "technical" troubleshooting if need be [21:27:07] I can also report it on phab if you'd prefer that [21:27:29] Maybe phab will let me in... :/ [21:27:35]