[00:00:40] [02mw-config] 07Amanda-Catherine synchronize pull request 03#2450: Trying something different per MacFan4000 on IRC - 13https://git.io/fAaCl [00:01:43] [02mw-config] 07MacFan4000 closed pull request 03#2450: Trying something different per MacFan4000 on IRC - 13https://git.io/fAaCl [00:01:45] [02miraheze/mw-config] 07MacFan4000 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAaC2 [00:01:47] [02miraheze/mw-config] 07Amanda-Catherine 035af0e3e - Trying something different per MacFan4000 on IRC (#2450) * Trying something different per MacFan4000 on IRC * Update LocalSettings.php [00:03:13] MacFan4000: do we also need to remove https://github.com/miraheze/mw-config/blob/master/LocalSettings.php#L2274 and https://github.com/miraheze/mw-config/blob/master/LocalSettings.php#L2606 [00:03:14] Title: [ mw-config/LocalSettings.php at master · miraheze/mw-config · GitHub ] - github.com [00:03:16] Title: [ mw-config/LocalSettings.php at master · miraheze/mw-config · GitHub ] - github.com [00:03:36] I don't know, but might just as well [00:03:49] Ok [00:05:47] Anyway, Ive deployed that change manually now, so you can go ahead and try to do stuff with MWP [00:06:04] I’m just going to remove the other lines first [00:06:12] ok [00:07:06] [02mw-config] 07Amanda-Catherine opened pull request 03#2451: Supplement to #2450 - 13https://git.io/fAaCr [00:08:23] [02mw-config] 07MacFan4000 closed pull request 03#2451: Supplement to #2450 - 13https://git.io/fAaCr [00:08:24] [02miraheze/mw-config] 07MacFan4000 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAaCK [00:08:26] [02miraheze/mw-config] 07Amanda-Catherine 036c65ea3 - Supplement to #2450 (#2451) [00:08:39] I’ll be back in 15-20 minutes and then I’ll test MWP [00:12:03] also, my runJobs.php scripts in screen are only on to wikis starting with f so it will probs be running all night [00:32:24] MacFan4000: MWP now works [00:32:38] Ok [00:32:44] !m MacFan4000 [00:32:44] <[d__d]> You're doing good work, MacFan4000! [00:32:57] And MWP global? [00:33:09] Wiki-1776: not yet I don’t think [00:50:15] JohnLewis PuppyKun SPF|Cloud Voidwalker FYI minor change to local weatherwiki steward policy https://weather.miraheze.org/w/index.php?title=Weather_Wiki:Stewards&diff=prev&oldid=2573 [00:50:16] Title: [ Login required - Weather Wiki ] - weather.miraheze.org [00:50:37] (Basically just requiring the use of the flood flag instead of bot for mass flooding, nothing major) [01:16:47] !night [01:16:47] Good night, sweet dreams and dream of the miraheze servers without errors! [02:15:52] Sexy girls rock! Especially young sexy girls! Don’t you love seeing teen girls wearing sexy spaghetti straps where you can see their bras and sometimes their boobs? What about sexy bikinis where you can totally see their boobs? [02:15:55] Sexy girls rock! Especially young sexy girls! Don’t you love seeing teen girls wearing sexy spaghetti straps where you can see their bras and sometimes their boobs? What about sexy bikinis where you can totally see their boobs? [02:15:57] Sexy girls rock! Especially young sexy girls! Don’t you love seeing teen girls wearing sexy spaghetti straps where you can see their bras and sometimes their boobs? What about sexy bikinis where you can totally see their boobs? [02:15:59] Sexy girls rock! Especially young sexy girls! Don’t you love seeing teen girls wearing sexy spaghetti straps where you can see their bras and sometimes their boobs? What about sexy bikinis where you can totally see their boobs? [02:16:59] Wtf [02:17:10] that’s very inappropriate spam [02:17:29] And that was logged as well [02:19:59] Took care of the on wiki stuff [02:20:07] But I would advise CU [02:22:06] JohnLewis: Voidwalker: ^^ [02:30:57] Was already on it [02:31:15] Ok [02:48:22] !log did a bunch of stuff on crappygames.mh.o / db trying to find corrupted flow pages [02:48:26] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [02:48:39] !log populated content model for all namespaces archive/page/revision tables on crappygameswiki [02:48:44] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [02:48:52] !log (read only) searched for a bunch of pages by title and page id, didnt find anything useful [02:48:58] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [02:49:12] !log MariaDB [crappygameswiki]> delete from page where page_id=3878 or page_id=42585; [02:49:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [03:04:59] Apparently deleting page info from the page table in the database didn't actually delete the pages but it allowed the page to be edited then deleted and it looks like the issue is mostly resolved. [03:05:08] At least no exceptions currently being thrown accessing pages. [03:05:17] AFAICS the entire history of that one page is still gone. [03:05:19] fuckin rip [03:05:21] anyways !night [05:05:00] RECOVERY - mw3 JobQueue on mw3 is OK: JOBQUEUE OK - job queue below 300 jobs [06:28:47] [02miraheze/CreateWiki] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAagn [06:28:48] [02miraheze/CreateWiki] 07translatewiki 036a1ef9d - Localisation updates from https://translatewiki.net. [06:28:50] [02miraheze/ManageWiki] 07translatewiki pushed 031 commit to 03master [+0/-0/±12] 13https://git.io/fAagc [06:28:51] [02miraheze/ManageWiki] 07translatewiki 036118b88 - Localisation updates from https://translatewiki.net. [06:56:00] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 2 datacenters are down: 172.104.111.8/cpweb, 2400:8902::f03c:91ff:fe07:444e/cpweb [07:00:09] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [07:05:12] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAaae [07:05:14] [02miraheze/services] 07MirahezeSSLBot 030594500 - BOT: Updating services config for wikis [08:01:00] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 3012 [08:50:15] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAaiO [08:50:16] [02miraheze/services] 07MirahezeSSLBot 03e506dfe - BOT: Updating services config for wikis [10:34:58] RECOVERY - mw3 JobQueue on mw3 is OK: JOBQUEUE OK - job queue below 300 jobs [10:39:58] !log removed spam from cw_requests [10:40:04] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [10:49:18] Yay @ jobqueue revovery [12:55:00] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 3021 [13:15:54] And it didn’t last long at all :( [13:25:03] !log > DELETE FROM cw_wikis WHERE wiki_dbname = 'nonciclopediawiki'; [13:25:10] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [13:25:12] !log DROP DATABASE nonciclopediawiki [13:25:17] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [13:56:11] Hi [14:02:09] https://meta.miraheze.org/wiki/Community_noticeboard#About_Copyrighted_Images_.28and_that_they_use_wgAllowExternalImages.29 comments? [14:02:10] Title: [ Community noticeboard - Miraheze Meta ] - meta.miraheze.org [14:35:13] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAV3H [14:35:14] [02miraheze/services] 07MirahezeSSLBot 0358495ab - BOT: Updating services config for wikis [14:44:33] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_phabricator-extensions] [15:26:18] [02miraheze/ManageWiki] 07Southparkfan pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/fAVBi [15:26:19] [02miraheze/ManageWiki] 07Southparkfan 036a1ef6c - Introduce option to require additional right for changing wiki private status [15:32:34] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [15:55:17] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAVzS [15:55:18] [02miraheze/services] 07MirahezeSSLBot 03c5de139 - BOT: Updating services config for wikis [16:12:53] hello? [16:15:13] Hi [16:24:59] hello Reception123 :) [16:32:50] [02ManageWiki] 07Amanda-Catherine commented on commit 036a1ef6ca7092c48a6ccef1fd79823842f378794d - 13https://git.io/fAVwb [16:56:36] [02ManageWiki] 07Southparkfan commented on commit 036a1ef6ca7092c48a6ccef1fd79823842f378794d - 13https://git.io/fAVKW [17:08:00] Hi! Is it possible to have my username globally renamed? I would like to unify it with my username in other places of the internet [17:09:25] Yes [17:09:59] shall I open a phabricator task? [17:10:54] nope, go to Special:GlobalRenameRequest [17:12:20] alright [17:12:47] [02ManageWiki] 07Amanda-Catherine commented on commit 036a1ef6ca7092c48a6ccef1fd79823842f378794d - 13https://git.io/fAVim [17:12:50] you are probably aware of that already, but this page says that the Wikimedia stewards will rename me. I don't know if it's a localization error though [17:13:08] y'know, I could have sworn we fixed that [17:13:50] I hace my language set to Catalan, so maybe the translation isn't updated [17:14:02] that might do it [17:14:11] I think we only updated the en translation [17:14:45] yeah, that's probably it [17:15:18] Reception123, what does the jobqueue look like today? :P [17:15:28] heh I think it was like 3k [17:15:37] not great, but a large improvement anyway [17:16:06] hmm, that means that a global rename could take upwards of half an hour [17:16:15] wasn't there a guest login to icinga? [17:17:14] Voidwalker yep [17:17:17] guest/guest [17:17:21] username=guest [17:17:24] password=guest [17:17:36] doesn't seem to be working [17:18:15] hmm someone changed the password [17:18:17] let me change it [17:18:41] Voidwalker try now? [17:19:04] works ty [17:19:23] Reception123, JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 14535 [17:19:36] so, uhh, not quite :P [17:20:12] I had the script running all night which cleared the queue but not for long [17:20:40] @NeoMahler fyi, I'd prefer to wait until the jobqueue is down before doing any renames [17:20:59] no worries, it's not urgent 😃 [17:21:04] otherwise you would be stuck in the middle of a rename for who knows how long, and I don't think you'd have access to your account [17:24:26] Voidwalker: oh, looks like it got larger [17:24:35] yeh [17:41:23] Reception123: Y como fue con Special:Analitycs? [17:43:00] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 2 minutes ago with 12 failures. Failed resources (up to 3 shown): Package[php-igbinary],Package[php-redis],Package[php7.2],Package[php7.2-curl] [17:43:19] Wiki-1776: Que quieres decir? [17:43:42] !log upgrading php7.2 on mw* and test1* [17:43:47] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [17:44:46] Reception123: la traducción de Especial:Analytics al español? [17:47:12] !log upgrade grafana and php7.2 on misc1 [17:47:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [17:47:20] !log upgrade php7.2 on misc2 [17:47:24] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [17:50:13] !log upgrade php7.2 on misc4 [17:50:17] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [17:50:58] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [17:52:29] !log running jobs on mw1 [17:52:33] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:02:09] Hello [19:02:48] hi [19:02:55] Hi [19:03:06] Hi Reception123 and Wiki-1776 [19:04:36] Reception123: did you see my email to everyone this morning? [19:04:48] yes [19:04:58] Ok [19:22:09] !log UPDATE cw_requests SET cw_status='declined' WHERE cw_custom='sexy'; (spam) [19:22:13] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:23:25] MacFan4000: I’m assuming that you saw my email regarding that spam too [19:25:05] yes, I did most of the cleanup work I think, other cleanup was done by Reception123 and on IRC it was Sigyn [19:25:45] It had already been RevDel’d and deleted by the time I woke up this morning... I saw it in the IRC logs [19:26:39] yeah, I did the revel and global lock and Reception123 did most of the wiki request cleanup [19:26:46] revdel* [19:27:06] I do seriously wonder how someone can make 50+ wiki requests in such a short amount of time [19:27:17] They’ve got to be using some automated script or something [19:27:33] I also wonder why requestwiki doesn't have rate limiting [19:27:53] or if it does why we rant using it [19:28:01] Probably because we don’t want to block legitimate users who want to create more than one wiki for different purposes at once [19:28:17] it used to, but I seem to recall that the manner that it was done is not compatible with recent updates to the extension [19:28:25] no max 5 wikis? [19:28:39] either that, or it was removed because it kept misfiring [19:28:42] Wiki-1776: that’s a ShoutWiki rule, and one that I strongly disagree with [19:29:00] sorry, could not be limited to 5 per hour/day* [19:29:01] I don’t think we should have a limit on the number of wikis people can request/create/manage [19:29:23] ^ yup, but we do want to put a limit on flooding [19:30:07] Yeah, but the LTA last night was definitely using an automated script [19:30:20] There’s no way that someone can flood 50+ requests in that short amount of time [19:30:25] I have corrected my question, what is your answer ahora¨? Amanda [19:30:29] there are ways [19:30:49] AmandaCatherine: [19:32:32] Wiki-1776: 5 per hour might work [19:32:38] Not sure how that would be done though [19:35:23] MacFan4000: We did have rate limiting! [19:35:24] I just noticed [19:35:32] why did that go away? [19:35:41] I found a function to limit requests to an hour before, what happened to that? [19:35:48] Voidwalker> it used to, but I seem to recall that the manner that it was done is not compatible with recent updates to the extension [19:35:49] oh ok [19:35:57] well we must imperatively find another way then [19:36:05] Reception123: also, we don’t want to put a 1-request limit of any kind on [19:36:24] Because that would block users requesting multiple wikis for different purposes [19:37:06] AmandaCatherine: 2 requests maximum [19:37:20] or 5 [19:37:25] That’s still a bit restrictive IMHO [19:37:36] I like Wiki-1776’s idea of 5 requests limit per hour [19:37:46] Minimizes flooding but still allows users to request multiple wikis at once [19:37:57] 5 is a bit much [19:38:08] but I mean anything is better than that many requests [19:38:10] or 3 or 4? [19:38:50] I really don’t know how someone can make 50+ requests without a malicious script, unless they opened 50 tabs on their browser all at once, which would likely result in a crash [19:39:21] But I think that any limit on wiki requests, regardless of timeframe, should be 3 or higher [19:40:14] I would doubt that a teenage girl, who I believe this LTA to be, would be able to write the kind of script needed to pull that off [19:40:56] AmandaCatherine: I don't know how someone has the patience to do so [19:41:17] and what do they gain? [19:41:24] Getting rid of that is literally one command in MySQL [19:41:45] They gain a temporary sensation of seeing their stuff being the only thing in RC [19:41:56] Since 50+ changes will bump off all other changes by default [19:42:08] looks like jobs has gone back up again [19:42:40] And they also gain the feeling that they have spread their stuff which I honestly think is just trying to arouse random people [19:42:50] But none of that seems worth the effort to me [19:42:51] no one reads that though [19:43:04] JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 16655 [19:43:12] John ran the jobs manually a few hours ago [19:43:20] I don't know what keeps going on [19:43:20] Reception123: if they come back, wait till you see what else they do [19:43:38] As I said in the email, they also spread potentially arousing media, some requiring oversight [19:44:12] AmandaCatherine: Yeah, I just don't get the point [19:44:13] Reception123: I'll give you a clue [19:44:16] it's still running :P [19:44:22] JohnLewis: GUP isn't it [19:44:29] AmandaCatherine: I don't know anyone who even reads that stuff [19:44:35] people see it's spam and don't bother [19:44:42] GUP was probably involved [19:44:43] Reception123: I don’t think anyone would on purpose [19:44:44] uh, seems like a lot of htmlcache when I checked on the largest queue wikis [19:45:05] But if they open a random page and there’s a giant 1000px image of a teenage girl showing too much... [19:45:10] (Which they have done) [19:45:13] JohnLewis: yeah, SPF killed some jobs last time [19:45:23] AmandaCatherine: there were images? [19:45:37] Not this time, but they’ve been known for it [19:45:43] If yes, that's illegal and we must report it [19:46:05] It’s only illegal if the people in the pictures are under 18 [19:46:11] Then it’s child pornography [19:46:24] o.o [19:46:25] But if the picture is of the LTA herself and she’s over 18, at least in Canada is not illegal [19:46:49] though miraheze follows netherlands + California laws. [19:46:54] AmandaCatherine: yeah, you mention the word 'teenage' so one can assume [19:47:03] and also in addition the staff memeber has to follow there local laws too [19:47:12] paladox: yeah, California (US laws) say that too probably [19:47:20] California is part of the US, which I believe has similar laws regarding child porn [19:47:55] yeah [19:48:00] Then perhaps to prevent this. It would be better if all uploads were in CommonsWiki except logos. ? [19:48:02] Although I think in the US most images and videos of pornstars can be legally redistributed, as long as they’re not reaching an underage audience [19:48:12] In Canada that cannot be done [19:48:31] Wiki-1776: Perhaps [19:48:35] Wiki-1776: then they would spam commonswiki [19:48:44] And I wouldn’t want to loose the ability to upload files on my wiki [19:48:55] AmandaCatherine: I don't think any revealing images of minors are allowed to be redistributed, but I'm not sure [19:49:03] anyway, it's always better to report [19:49:10] as it's said "see something, say something" [19:49:14] I think that would apply here too [19:49:15] not of minors, but all pornstars have to be 18+ [19:49:21] but I agree though [19:49:22] Yeah [19:49:38] although at the website where I’ve seen them, I just RBI most of the time [19:49:40] But I mean no one can confirm the age of someone, so if it looks suspicious, it should be reported to the authorities [19:49:47] True [19:50:38] Another option is that in some way, all the uploads were recorded in some [19:51:05] I’ve tended to OS stuff that’s actual nudity on general principles, stuff that’s just a risqué bikini or tank top I leave alone [19:51:40] OS? where? [19:51:55] and tbh no pictures of such sort should be on Meta, so either way they're being deleted [19:52:12] Reception123: as I noted in email, I’m familiar with this LTA from another website [19:52:42] What I was saying is that IMHO images that contain actual nudity should be suppressed, not just deleted [19:52:43] A Special: New global images where the last 50 or 500 uploaded images of wikis appear in all of them. And that could be seen by all or just a few users [19:52:54] But things that are just risqué can be standard deleted and RBID [19:53:02] AmandaCatherine: would you be able to perhaps share that website? (just for more insight) [19:53:07] if you would like you can do so via PM [19:53:39] JohnLewis: is posible?: A Special: New global images where the last 50 or 500 uploaded images of wikis appear in all of them. And that could be seen by all or just a few users [19:54:39] Reception123: the website was taken down and moved elsewhere last month after it got so badly overrun by multiple LTAs it wasn’t salvageable [19:54:57] I didn’t follow up on its new location, since I wasn’t as active there as I used to be [19:55:02] So any user could upload images to his wiki and appear in Special:NewImagesGlobal [19:55:33] I think the host of which the site was hosted also went dead altogether because of spam [19:55:56] Wiki-1776, it might be possible, but I doubt any work would get done on it by us anytime soon [19:56:09] there's other priorities [19:57:59] hmm [19:59:32] ok [19:59:37] AmandaCatherine: what was it called? just curious [20:03:07] Would anyone have any objections to me removing the long essay from my user page on Meta? [20:03:41] why would we? Your userpage, you can do whatever you want [within common sense of course] [20:04:06] Just because the essay is about the history of LP and me etc and wasn’t sure if removing that would cause problems [20:04:29] AmandaCatherine: No IMO. though if you'd like you can always make a subpage [20:09:08] Uhh... what? https://meta.miraheze.org/w/index.php?title=Meta:Administrators%27_noticeboard&curid=661&diff=59412&oldid=59126 [20:09:11] Title: [ Difference between revisions of "Meta:Administrators' noticeboard" - Miraheze Meta ] - meta.miraheze.org [20:10:13] Also ?invalid wiki request https://meta.miraheze.org/wiki/Special:RequestWikiQueue/5865 [20:10:15] Title: [ Wiki requests queue - Miraheze Meta ] - meta.miraheze.org [20:14:34] I am aware of this individual, and I think it may be time to bring a harder edge down towards them [20:14:59] This is the same user who wanted to duplicate and move Wikipedia, isn’t it? [20:15:49] that's not all, there's about ten accounts involved in some shenanigans on another wiki [20:16:06] Huh [20:16:41] I have rights on their “Knowledge Box Wiki” - haven’t really been following that closely, but the only shenanigans I’ve seen are mass creations of mysterious blank pages [20:17:01] Although Voidwalker check your PM please [21:04:11] Has anyone else ever come across a wiki that was filled with ~105 blank or useless pages? [21:04:37] which? [21:04:45] Knowledge Box [21:04:53] Created by that user who you just locked socks of [21:08:33] Voidwalker: should we close their wikis, especially the ones that are borderline copyright infringement with trying to fork Wikipedia? [21:08:54] I'm going to wait for their response before doing anything else [21:09:02] Ok [21:09:17] I cleared out the 100 or so blank pages on Knowledge Box, but feel free to revert [21:09:27] I also blocked and desysopped both main accounts [21:10:41] "Void * changed group membership for User:Perrie3@knowledgeboxwiki from bureaucrat to (none)" [21:11:06] That’s good too [21:11:14] Not sure if you want to de-crat Louise3 or not [21:11:38] I'm leaving them semi-intact depending on how they respond [21:12:09] Ok, like I said I desysopped and blocked both accounts, and nuked the 100 blank pages [21:12:15] But anyone can feel free to revert if I was mistaken [21:14:17] Ah, but do you think I could open a thread on Phab about Special:NewImagesGlobal? in order to monitor the images uploaded on all wikis. Voidwalker [21:15:10] (and in Phabricator it could be analyzed if it would be possible or would go to Upstream) [21:17:51] MacFan4000: given Voidwalker’s findings, isn’t this just feeding a possible troll https://meta.miraheze.org/w/index.php?title=Meta:Administrators%27_noticeboard&diff=59424&oldid=59416 ? [21:17:52] Title: [ Difference between revisions of "Meta:Administrators' noticeboard" - Miraheze Meta ] - meta.miraheze.org [21:19:09] Yeah, I thought about closing the request but, I don’t think I should since I’m not a bureaucrat on meta [21:19:53] I just think your comment seems to be acting like it’s just a normal misplaced request [21:20:01] When that is about as far from the truth [21:20:25] Well it is misplaced. [21:20:35] Wiki-1776, go right ahead [21:20:42] Yes, but it’s also been made by someone who is not being honest [21:20:47] And therefore should be declined out of hand [21:21:00] Voidwalker: ^^ [21:23:36] I'm going to leave it because 1 it's not a proper request and 2 it's out of scope of the board [21:39:27] [02puppet] 07MacFan4000 opened pull request 03#829: Change wiki-Abuse to go to staff@ - 13https://git.io/fAwTq [21:39:37] JohnLewis: ^^ [21:39:56] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAwTY [21:39:58] [02miraheze/puppet] 07MacFan4000 039ba64a2 - Change wiki-Abuse to go to staff@ (#829) [21:39:59] [02puppet] 07paladox closed pull request 03#829: Change wiki-Abuse to go to staff@ - 13https://git.io/fAwTq [21:40:37] [02miraheze/puppet] 07JohnFLewis pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAwTc [21:40:38] [02miraheze/puppet] 07JohnFLewis 0397f0091 - fwd wiki-abuse [21:40:57] huh https://meta.miraheze.org/wiki/Special:RequestWikiQueue/5866 [21:40:58] Title: [ Wiki requests queue - Miraheze Meta ] - meta.miraheze.org [21:41:05] Not sure if that’s valid or not [21:41:18] I know the URL isn’t [21:42:09] they seem to have used custom domain [21:42:14] but still wrong seeing as it's wikia [21:42:23] Yeah, you can’t create a wikia site on Miraheze [21:42:29] (Well, you can, but not at the wikia URL) [21:42:34] JohnLewis the custom domain field has no point any more seeing as you have to set wgServer for it to work. [21:43:00] The comment which is “got shut down” is what stands out to me [21:43:24] MacFan4000: unfortunately Wikia seems to shut down a lot of wikis for unusual or questionable reasons [21:43:32] So that shouldn’t be an automatic no-goer [21:44:42] Note that if they obide by our content policy then we can host them (we are not as strict as wikia) seeing as we allow freedom of speach to a extent [21:44:47] JohnLewis am i right ^^? [21:44:56] john the legal expert in that stuff [21:47:06] Paradox: the custom domain field never meant anything besides “hi I want these domain in the future okay!” [21:47:35] JohnLewis paradox? [21:47:39] and oh [21:47:44] Tbh you are [21:48:01] JohnLewis im what? :P [21:48:21] Anyway GTG [21:51:56] https://phabricator.miraheze.org/T3582 Done [21:51:57] Title: [ ⚓ T3582 Creation of Special:NewFilesGlobal ] - phabricator.miraheze.org [21:54:13] 😮 [21:54:17] Another Wikimedia chapter? [21:54:26] CnocBride? [21:54:31] *@CnocBride [21:55:10] I was just saying it's great to see another Wikimedia chapter migrating on to Miraheze. [21:55:23] Is Wikimedia Indonesia on our servers or am I mistaken? [21:55:51] oh i see, and i think they have a wiki but not sure. [21:56:05] Thanks CnocBride [21:56:22] yeh wikimedia Australia [22:03:44] thanks Voidwalker [22:04:03] np [22:36:03] please do not accept https://meta.miraheze.org/wiki/Special:RequestWikiQueue/5867 without approval from myself or a member of staff [22:36:05] Title: [ Wiki requests queue - Miraheze Meta ] - meta.miraheze.org [22:36:35] Ok Voidwalker [22:44:59] RECOVERY - mw3 JobQueue on mw3 is OK: JOBQUEUE OK - job queue below 300 jobs [22:49:00] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 3259 [22:58:30] Hmm jobqueue can’t stay normal [22:59:46] Nope not if someone edits there user page [22:59:58] As it creates a job for every wiki [23:00:07] yeah, but that didn't happen this time [23:00:17] paladox: it not GUP I don’t think, as it doesn’t create 60k jobs [23:00:27] Ok [23:00:32] it’s been htmlcache lately [23:00:38] So what is creating 60k jobs [23:00:48] Is it someone editing a wiki page ! [23:00:53] 19:00 it’s been htmlcache lately [23:00:56] ! = ? [23:00:56] That [23:01:03] Ok [23:01:22] Nothing we can do about that I doint think? [23:01:25] paladox, the icinga guest login doesn't work again [23:01:35] I’ll fix it [23:01:52] there should be something we can do about it, because it was never a problem, at least, not like this [23:02:03] This makes me wonder if SPFs recent caching change could be the cause since this started after he did that [23:02:27] Voidwalker: fixed [23:02:49] any idea why that keeps getting changed? [23:03:04] Yep [23:03:11] Someone can change the password [23:03:19] Anyone who can login into that user [23:05:13] Voidwalker: ^^ [23:05:53] mmh, that's annoying [23:06:02] be neat if you could lock that [23:06:51] I was looking at that earlier [23:07:01] But apparently there’s a open request for that [23:10:49] https://phabricator.miraheze.org/T3583 [23:10:50] Title: [ ⚓ T3583 Jobqueue ] - phabricator.miraheze.org [23:11:21] There is a task for the jobqueue mess [23:11:28] And it’s UBN :) [23:18:23] [02mw-config] 07Amanda-Catherine opened pull request 03#2452: Fix - 13https://git.io/fAwO3 [23:23:27] [02mw-config] 07MacFan4000 closed pull request 03#2452: Fix - 13https://git.io/fAwO3 [23:23:28] [02miraheze/mw-config] 07MacFan4000 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAwOz [23:23:29] [02miraheze/mw-config] 07Amanda-Catherine 03538759f - Fix (#2452) [23:39:10] Phab admins https://phabricator.miraheze.org/T3584 [23:39:11] Title: [ ⚓ T3584 Update my Herald rule ] - phabricator.miraheze.org [23:46:03] paladox: ^^ [23:50:32] Hmm.. not sure if this is a vulnerability or not, but I seem to be able to add myself as a watcher to both the security project and the CoC ACL project, even though both have their membership restricted [23:52:01] nope, iirc, that just means that you will be able to see tasks in those projects when/if they go public [23:52:49] But it also says that I will receive all mail sent to project members [23:53:10] mail is done externally, or it should be [23:53:13] hmm [23:53:51] It appears that if I add myself as a watcher, I will receive all of the automatic emails that Phabricator sends for tasks in those two projects, even though I’m not a member [23:54:06] And therefore I would get an email about new tasks being created in those projects even if I can’t see them [23:55:33] https://i.imgur.com/J8f8mxd.jpg [23:55:43] ^ Voidwalker [23:58:38] hmm, I don't think you should be able to get mail for tasks you can't see