[00:06:17] [1/8] What exactly do these permissions do? They appear on the following wikis: [00:06:17] [2/8] `(ceo)` = [00:06:17] [3/8] `(co)` = [00:06:17] [4/8] `(edit-admin-pages)` = nenawikiwiki [00:06:18] [5/8] `(edit-create)` = [00:06:18] [6/8] `(0)` = [00:06:18] [7/8] `(1)` = [00:06:19] [8/8] I don't even know the URL for the nenawikiwiki. [00:07:53] Try reaching out to the local admins to ask [00:08:02] We have no idea what they intend to use those permissions for [00:08:07] they're custom ones set by them [00:10:06] any Miraheze wiki can be usually accessed by https://nenawiki.miraheze.org/ even if it has custom domain [00:17:47] Er... I don't recall local administrators being able to create custom permissions. Or have they been granted the ability to create custom permissions yet? [00:22:02] can barely access my wiki, might as well call off editing for today 😦 [00:22:17] RIP images [00:22:20] I was able to a year or two ago iirc [00:22:47] They've always had the permission to create custom rights [00:23:00] It's just that it has to be requested on Phabricator, like in the good old days [00:23:25] Ugh. [00:24:09] So you have to request that the permissions are created for you? Or you have to request for the ability to create custom permissions at will? [00:24:27] You have to request the permission be created for you [00:24:35] Creating permissions from within ManageWiki isn't possible [00:24:45] They're created manually via LocalSettings.php [00:26:21] why can't peoiple edit that? [00:26:38] You can if you want to [00:26:38] people cant do it directly because malicious code could be added [00:26:40] Even my site logo has vanished, bit stuck on what to do here. Wait? [00:26:45] or code that simply doesn't work [00:26:48] #announcements [00:26:49] [00:26:52] all our code is here [00:27:08] Alrighty [00:27:27] @!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! you could make a pr though [00:27:35] It's a good habit to always check announcements if something is malfunctioning. [00:27:43] Just so folks know, we don't have an ETA on files being back up. The disks are back in the server, but the server isn't booting. [00:27:57] I heard that creating custom permissions freely was being considered, on the condition that there are restrictions on what types of permissions can be created. [00:28:16] I believe it was declined as it'd be too hard to implement [00:28:52] For example, custom permissions are only created to work with namespace restrictions and page protection settings. [00:30:16] Another good place to keep an eye on for technical problems is [00:32:07] I have a handful of permission concepts. Most of which would be too hard to implement. One of those permissions allows for selective revisions to be deleted with `?action=delete` as opposed to deleting entire pages and selectively undeleting revisions with Special:Undelete. [00:34:18] I understand that such a permission wouldn't be CC-BY-SA friendly. But it has always irked me how selective revisions can be undeleted with Special:Undelete, but selective revisions can't be deleted with `?action=delete`. Even with Special:RevisionDelete existing, as that is built on an entirely different system from ?action=delete and Special:Undelete. [00:38:37] Yeah, that far exceeds the complexity of a configuration change and would have to be a change to the core of the software. I doubt it would be done though, as maintaining a list of all revisions (even if deleted by RevisionDelete) is the preferred behavior of the software [00:42:17] True. Even if revisions could be deleted with ?action=delete, they could still be undeleted again with Special:Undelete. But such a permission would have a lot of room for abuse, as it would only be intended for use in situations where the CC-BY-SA licence wouldn't be at risk. [00:46:22] The fictitious `(selectivedelete)` permission would come in handy for someone like me. As I have been in situations where I would need such a permission. And because I would know how to use it without violating the CC-BY-SA licence. [01:37:09] and now there are intermittent 503s and 502s [01:38:35] Was about to ask if that was just me [01:46:12] I've been having them since a few days ago tbh [01:47:41] Well this time it's always the regular ol' miraheze logo 503 not smw 503 [02:06:04] im having them too [02:40:45] My wiki looks like a lowkey luminal space now. It's kinda funky. [02:43:48] <光纪#9056> me too [02:43:54] Mind the gaps, that's where the monsters hide. (jokes) [02:44:11] (not a joke) [02:45:39] <光纪#9056> What's worse is that I have a board with regional links on the map and it's completely messed up🤣 [02:49:32] oof [03:07:23] Are we down? I am getting continuous 503s on Meta... [03:09:17] Oh db101 backups probably. [03:10:38] Nevermind I have no idea, but icinga looks bad. [03:17:06] Everything I've tried is down atm. [03:17:46] I am able to access [03:23:08] Looks like mw backends going down depools everything??? Really doesn't seem like a good idea [03:37:13] Been down for 30 minutes now. [03:37:47] @Site Reliability Engineers something need rebooted? [03:38:07] Nothing I can see, it's up for me, seems to have been a blip on cp32 [03:38:24] or maybe not? [03:39:04] It has been constantly down all wikis I have visted for 30 minutes, and I am on cp33 [03:40:01] It's not obvious what's going on, there's no services other than cp* that appear to be down right now [03:40:06] Once created, can custom permissions be freely be granted and revoked from usergroups with Special:ManageWiki/permissions on the wiki the permission has been added to, or does it still need to be added to usergroups on request? [03:40:13] Massive amount of warning in icinga on IRC [03:40:17] nothing on grafana either [03:40:36] I'm looking at the icinga web interface and the only warnings that stuck are for cp* [03:40:57] Can you manually pool mw servers back into varnish and see if they work? [03:42:02] Or reboot cp server? [03:42:44] Yes, once created it can be controlled via ManageWiki [03:43:09] I'm seeing edits on Meta so it seems some people are able to edit [03:44:06] [1/5] ``` [03:44:06] [2/5] backend.set_health mediawiki healthy [03:44:06] [3/5] backend.set_health mw121 healthy [03:44:07] [4/5] ``` [03:44:07] [5/5] in varnishadm might be worth trying? [03:46:26] Now it switched to 502s. [03:46:41] Nope back to 503s. [03:47:18] cp32 is taking a long time to restart [03:47:30] (Varnish XID 21955262) via cp33 at Wed, 12 Apr 2023 03:46:29 GMT. [03:47:41] It is cp33 though? [03:47:44] or cp32 also? [03:48:01] I restarted cp32 [03:48:27] Depool us in DNS maybe? [03:49:29] cp33 shows healthy on all backends right now [03:49:40] cp2 only has 40% or so failure, cp 3 has 80% or higher according to IRC icinga [03:50:08] Never mind, cp22 jumped to 60% [03:50:35] Still 503s on cp33 [03:55:09] Things were down for me as well, but back up now. [03:55:39] Ahh, that timing. Of course issues come up while I was in the middle of working on something time-sensitive. =V [03:55:45] Still getting 503s on cp33 here [03:56:32] Bro is the wiki back up? [04:03:14] Back up for me also. [04:05:31] isn't it lovely when 300 different things go wrong at once? [04:07:05] Honestly, I'm not sure if there was actually anything that could have been done there to fix anything [04:07:40]

PROBLEM - cp22 HTTP 4xx/5xx ERROR Rate on cp22 is CRITICAL: CRITICAL - NGINX Error Rate is 62% [04:07:53] Still issues it seems. [04:08:13] Maybe it will recover. [04:10:46] Disgutedorite: Always how sysadmining goes it feels; there can never just be *one* thing that goes wrong. D; [04:11:29] Only one thing going wrong makes solving the problem too easy! /s [04:11:54] If anything can go wrong, it will it seems. [04:12:58] Murphy's law 🤷‍♂️ [04:13:19] Yeah, that is basically what I was quoting lol [04:14:22] "Anything that can go wrong will go wrong." [04:59:52] [1/2] on an unrelated note I've been monitoring the stewards' noticeboard waiting for a reply on my thing and [04:59:53] [2/2] damn Naleksuh is literally just digging their own grave huh, and I say this while having literally zero context of what happened [05:00:29] I got [d0c99925ee8d783a80e560dc] 2023-04-12 04:59:48: Végzetes kivétel: „FileBackendError” on my Wiki lol [05:00:32] your input and commentary on the thread would be appreciated [05:01:09] I was just saying based on this alone https://meta.miraheze.org/w/index.php?title=Stewards%27_noticeboard&diff=prev&oldid=329073&diffmode=source [05:02:24] still, an outside view of this would be appreciated [05:06:15] [1/2] this is a long thread with branches I am not used to commenting on things like this [05:06:16] [2/2] should I reply to what I linked directly noting what it looks like from my perspective (kinda immature and seriously looks like they're trying to make a false equivalence to make themself look less bad but executing it very, very poorly, even without any information to go off of regarding what they actually did), or? like, where do I put the reply [05:07:23] I mean, at this point it's pretty much a choose-your-own-adventure [05:08:07] You can click the "Reply" button to that message if you wish and share your analysis there [05:23:09] Yes, an outside perspective on stuff like this can be very helpful. [05:25:47] Am just getting caught up on that one myself, had thought things were quiet on this front, but I guess not. [05:26:09] [1/4] I'm a little tired and don't want to sound too inflammatory, is this response okay? [05:26:09] [2/4] > Sorry to interrupt since I have very little information about this situation and am not involved directly, but I noticed this argument going on while I was waiting for a reply to a request I made elsewhere on the noticeboard and I feel the need to note that from an outside perspective, Naleksuh, with zero context for what you did (or are accused of doing), the sample s [05:26:09] [3/4] cript of calling for BrandonWM's removal looks like the kind of thing a kid who got banned for posting porn in general chat would write up to say that ''actually'', the mod who banned them should be banned instead because they ''also'' posted a picture of a girl at some point. The roleplay of users who probably don't exist also makes me think either you genuinely believe [05:26:10] [4/4] you have an army of supporters, or you are attempting to intimidate other people into thinking you do to keep your status as a wiki creator. Your own words gave me all the context I needed to be instantly convinced to support your removal. [05:28:36] I'd humbly suggest removing the reference to posting porn. While a valid comparison, it's not relevant and invites further nonsense. [05:29:24] Yeah, I try to remain neutral while also stating the facts. [05:29:36] It's a good way to go, when things are inflammatory. [05:29:46] "spamming in general chat" and "posting an emoji response once" instead for the comparative example? [05:30:31] I'm an outsider too, this is getting silly now and it needs to have a lid put on it. [05:30:42] Is that section for voting on someone's removal? [05:31:15] The introduction (or my reading of it as I'm not familiar with removal request formatting) is a bit unclear. [05:31:39] There isn't a good forum for it, but it's generally a steward action so the section is being kinda-repurposed. [05:32:12] If it's request for removal for Naleksuh, and voting on that, I definitely support based on continued pattern of inflammatory behaviour. [05:32:42] notaracham is this comparison better [05:32:56] Yep, my perspective is that anything worth saying has largely been said, and stewards will deal with the issue once platform stability is back in a good place. [05:33:15] Closer/clearer, yes. [05:33:25] If its not really a vote, then there's not much point in me engaging... [05:33:35] It's not really, no. [05:34:07] More of a festivus-style airing of grievance. [05:34:53] Ah, okay. Is there any value to MH in adding a mostly neutral perspective on the issue? [05:35:25] Community input in itself is still helpful for establishing a record and pattern, which in turn helps guide steward action. [05:35:45] But as said before, this is pretty rare so there isn't well-established procedure/precedent [05:36:38] I'd also add, pretty much everything that needs to be said has, but if you feel an outside perspective is helpful/would provide new insight, you're free to add it. [05:37:23] Personally, it's about time for me to call it a night. [05:37:49] morning, what's happening again [05:38:38] Continued file server stuff re: swift, most relevantly. [05:38:53] Yep. Frankly the false (reversed) vendetta has worn out its welcome, the user just needs to be removed at this point, so everyone can move on. [05:39:04] Some downtime for some stuff, then back up. [05:42:44] Adding your view on the SN thread would be appreciated so that the closing Steward can consider all viewpoints and opinions [05:45:43] Here's a comparison between what users with both the `(delete)` permission and the fictitious `(selectivedelete)` would see on the `?action=delete` page if the fictitious `(selectivedelete)` permission were to exist exactly how I've envisioned it. And what users with just the `(delete)` permission see. [05:50:52] You can probably figure this out already, but both images display options that won't appear without the `(deleterevision)` permission for the 'change visibility of selected revisions' button and checkboxes. And the `(deleterevision)` and `(deletelogentry)` permissions for the 'change visibility' links. [05:53:20] Shoot, forgot I was logged in as wrong user LOL [05:54:04] If I swap the comment to my primary, the username I use for voting, is anyone going to jump on me for it? [05:54:29] Nah [05:54:31] Was an honest multitasking mistake 😆 [05:54:51] If you already have an established multi-user relationship, that's fine. [05:55:17] Yeah, i do. I usually separate for my own wiki. [05:55:27] I always comment and vote only under my primary though, the one I use here. [05:55:40] All good, then. [05:56:28] If meta will let me log in that is heheheehh. [06:02:06] Alright, comment done and on to productive stuff now [06:16:20] Has anyone figured out a decent "expand all" "collapse all" function for pages with lots of tables (like if tables were used on a FAQ page for example)? [06:16:55] I'm lousy at js and only half way there from someone else's code. [06:19:24] super hacky way is to click every expand / collapse button [06:20:38] depending on how expand or collapse works you could jsut call the function repeatedly for every collapsible element [06:23:22] It's also possible to create a custom button that uses the same target ID for all objects. I'll dig up where I did that tomorrow [06:26:09] Yeah, that's kinda what I've got now, but not fully functional. If you do have something, would much appreciate it. [06:26:15] I'll keep fiddling in the meantime heheh. [06:26:46] https://planet-crafter.fandom.com/wiki/Version_history has an example of this using mw-customcollapsible [06:27:50] I scooped this from Fandom, but the collapse is problematic. [06:28:13] The expand works not so much the collapse. [06:28:27] duplicate ids is kinda bad practice tho [06:30:04] For sure, it's also awful for screen readers [06:31:40] Yeah, I'm so no-good at js. Basically I've been trying bits of code from here and there to try to cobble something together (very poorly) lol. / [06:31:48] The planet crafter example was unfortunately the cleanest way I could figure and these caveats are also mentioned in the mw-customcollapsible documentation [06:32:12] Thank you! I'll give that a go! [06:36:53] [1/14] ```js [06:36:54] [2/14] $('.test2').on('click', function() { [06:36:54] [3/14] if ($(this).data('state') === 'expanded') { [06:36:54] [4/14] $('.mw-collapsible-toggle-expanded').click(); [06:36:55] [5/14] $(this).data('state', 'collapsed'); [06:36:55] [6/14] $(this).text('Expand all'); [06:36:55] [7/14] } else { [06:36:55] [8/14] $('.mw-collapsible-toggle-collapsed').click(); [06:36:56] [9/14] $(this).data('state', 'expanded'); [06:36:56] [10/14] $(this).text('Collapse all'); [06:36:56] [11/14] } [06:36:57] [12/14] }); [06:36:57] [13/14] ``` [06:36:58] [14/14] i threw together the cheap hack method i mentioned earlier [06:37:05] instead of class test2 it's whatever your button is [06:38:12] instead of hitting every single mw-collapsble you could give your collapse all / expand all element a data field that specifies an additional class instead of just mw-collapsible yada yada [06:38:57] That'ssimilar to the hacky version I cobbled together. [06:46:00] Alternatively you could reimplement the collapsing logic and have total control over all the states [07:30:07] just heads-up, I'll be going to places for a week and a half so I'll be out of active wiki doings and support attempts here [07:35:12] [1/2] Unauthorized [07:35:12] [2/2] This server could not verify that you are authorized to access the document you requested. [07:35:32] Please fix those wikis right now!!!! [07:35:37]