[00:02:28] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:02:30] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:02:34] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:02:44] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:02:46] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:02:56] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:18] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:24] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:28] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:52] PROBLEM - cp5 Puppet on cp5 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:56] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:04:08] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:04:10] PROBLEM - lizardfs2 Puppet on lizardfs2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:04:34] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:10:57] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [00:11:19] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [00:11:25] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [00:11:29] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [00:11:57] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [00:12:09] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [00:12:11] RECOVERY - lizardfs2 Puppet on lizardfs2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:29] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:31] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:35] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:45] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:47] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [00:13:51] RECOVERY - cp5 Puppet on cp5 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:14:33] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [02:25:55] PROBLEM - db4 Disk Space on db4 is WARNING: DISK WARNING - free space: / 76915 MB (20% inode=94%); [05:42:24] [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fNpJj [05:42:25] [02miraheze/mw-config] 07Reception123 03f942aff - fix macfans incubatorwiki fix [05:56:11] hamza: hi [05:56:18] hamza: was the import done? [06:04:23] hamza: Oh, sorry to hear that [06:04:34] hamza: Since the images were downloaded by Paladox (I couldn't) I will have to ask him [06:05:23] hamza: Sorry that they weren't imported, I'm sure they will be in a few hours when Paladox is online [06:08:10] Ok :) [06:08:20] hamza: hope your wiki is going well [10:50:14] [02mw-config] 07JohnFLewis commented on pull request 03#2376: Downgrade isvwiki to Wikipedia's CC BY-SA - 13https://git.io/fNpRH [10:50:15] [02mw-config] 07JohnFLewis closed pull request 03#2376: Downgrade isvwiki to Wikipedia's CC BY-SA - 13https://git.io/fNbhZ [11:01:35] hello [11:01:58] hi Zppix [11:02:02] I have an issue i need more money in my bank account, could you fix xD jk [11:02:06] Zppix: had time to look at the bot? [11:02:09] Zppix: ask Labster lol [11:02:21] Reception123: Ive been really busy im trying to as much as i can [11:02:25] oh ok [11:09:01] why not give Sigyn +O MacFan4000 ? [11:09:09] I can’t [11:09:15] It’s up to ops [11:09:28] Reception123: ^^ [11:11:44] there's no point in having +O for a bot [11:11:49] This is also temporary [11:13:12] The point for Sigyn is so it can see all messages at all times [11:13:51] And it can now and will in future [11:15:44] The point is we have to manually op it every time [11:16:55] I mean if you really want to +O it I don't really mind, but once this spam period is over it should be -O'ed [13:12:09] Good morning [13:21:39] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 5947 [13:28:06] Uhh... someone lock/block https://meta.miraheze.org/wiki/Special:CentralAuth/Mushroom_cloud [13:28:07] Title: [ Global account information for Mushroom cloud - Miraheze Meta ] - meta.miraheze.org [13:28:13] Quickly please before they do any more damage [13:35:12] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fNpPJ [13:35:13] [02miraheze/services] 07MirahezeSSLBot 03ba8527e - BOT: Updating services config for wikis [13:43:31] JohnLewis MacFan4000 PuppyKun Reception123 SPF|Cloud mass ping - someone act now https://meta.miraheze.org/wiki/Special:CentralAuth/Mushroom_cloud [13:43:32] Title: [ Global account information for Mushroom cloud - Miraheze Meta ] - meta.miraheze.org [13:43:44] Really urgent - they’re ongoing [13:43:53] Done [13:43:58] Rolling back [13:44:02] !m MacFan4000 [13:44:02] <[d__d]> You're doing good work, MacFan4000! [13:44:12] * AmandaCatherine breaths a sigh of relief [13:44:53] Pfft, my mass ping tripped Sigyn [13:44:58] I got a stern warning [13:46:05] Done [13:48:33] !log sudo -u www-data php importImages.php --wiki quranwiki --search-recursively /home/reception/archive_unzipped [13:48:37] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [13:53:56] Well, at least the filter is working https://meta.miraheze.org/wiki/Special:AbuseLog?wpSearchUser=Mushroom+cloud&wpSearchTitle=&wpSearchImpact=0&wpSearchActionTaken=disallow&wpSearchFilter=&wpSearchWiki= [13:53:57] Title: [ Abuse filter log - Miraheze Meta ] - meta.miraheze.org [13:54:08] But it appears they figured out a a way to bypass it too [13:54:10] With hidden text [14:16:33] [02miraheze/mediawiki] 07Reception123 pushed 031 commit to 03REL1_31 [+0/-0/±1] 13https://git.io/fNpD2 [14:16:35] [02miraheze/mediawiki] 07Reception123 03e1ae412 - Update CreateWiki [14:16:43] eeek [14:16:51] being required to captcha, weird experiences lol [14:17:07] revi: aren't you a sysop? [14:17:10] or you mean on another wiki [14:17:10] on other wiki [14:17:16] k yeah [14:17:30] https://incubator.miraheze.org/wiki/User:Revi/common.js nice external link detection [14:17:31] Title: [ User:Revi/common.js - Incubator Plus 2.0 ] - incubator.miraheze.org [14:17:36] even tho they don't allow link to be visible lol [14:17:48] Reception123: doint forget to run lc:D [14:18:05] Can't we globally enable SyntaxHighlight? [14:18:08] still causing problems? [14:18:17] (IIRC it caused some meh in the past) [14:18:21] We could [14:18:44] !log rebuild LC on test1wiki [14:18:48] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [14:19:15] Yeah, maybe we should make SyntaxHighlight global [14:20:22] [02miraheze/mw-config] 07MacFan4000 created branch 03syntaxhighlightglobal 13https://git.io/fNpDN [14:20:24] [02mw-config] 07MacFan4000 created branch 03syntaxhighlightglobal - 13https://git.io/vbvb3 [14:20:41] <3 [14:21:43] [02miraheze/mw-config] 07MacFan4000 pushed 031 commit to 03syntaxhighlightglobal [+0/-0/±1] 13https://git.io/fNpyT [14:21:45] [02miraheze/mw-config] 07MacFan4000 0378b9041 - Update ManageWiki.php [14:21:50] miraheze/mw-config/syntaxhighlightglobal/f942aff - Reception123 The build passed. https://travis-ci.org/miraheze/mw-config/builds/416838078 [14:22:19] MacFan4000: why is it telling me and not you? [14:22:45] because when I created the branch the latest commit was yours [14:25:10] [02miraheze/mw-config] 07MacFan4000 pushed 031 commit to 03syntaxhighlightglobal [+0/-0/±1] 13https://git.io/fNpyB [14:25:11] [02miraheze/mw-config] 07MacFan4000 03c219ed0 - Update LocalExtensions.php [14:26:14] [02miraheze/mw-config] 07MacFan4000 pushed 031 commit to 03syntaxhighlightglobal [+0/-0/±1] 13https://git.io/fNpyV [14:26:16] [02miraheze/mw-config] 07MacFan4000 034df210e - Update GlobalExtensions.php [14:28:37] [02miraheze/mw-config] 07MacFan4000 pushed 031 commit to 03syntaxhighlightglobal [+0/-0/±1] 13https://git.io/fNpyM [14:28:38] [02miraheze/mw-config] 07MacFan4000 034984781 - Update LocalSettings.php [14:28:46] [02mw-config] 07MacFan4000 opened pull request 03#2378: Syntaxhighlightglobal - 13https://git.io/fNpyy [14:28:53] [02mw-config] 07MacFan4000 closed pull request 03#2378: Syntaxhighlightglobal - 13https://git.io/fNpyy [14:28:55] [02miraheze/mw-config] 07MacFan4000 pushed 031 commit to 03master [+0/-0/±4] 13https://git.io/fNpyH [14:28:56] [02miraheze/mw-config] 07MacFan4000 037521270 - Syntaxhighlightglobal (#2378) * Update ManageWiki.php * Update LocalExtensions.php * Update GlobalExtensions.php * Update LocalSettings.php [14:29:24] revi: Reception123: paladox: ^^ [14:29:30] [02mw-config] 07MacFan4000 deleted branch 03syntaxhighlightglobal - 13https://git.io/vbvb3 [14:29:31] [02miraheze/mw-config] 07MacFan4000 deleted branch 03syntaxhighlightglobal [14:30:09] hamza: you're welcome :) [14:30:11] it's still ongoing [14:31:07] Ok [15:35:12] [02mw-config] 07Amanda-Catherine opened pull request 03#2379: Remove nominornewtalk from bots - 13https://git.io/fNpbn [15:36:14] ^ FYI I *think* (not sure) that a “squash & merge” may be needed as opposed to a merge commit in order to automatically update my weatherwiki fork of the repo [15:36:40] Because I’ve had to keep re-forking the repo each time I make a new PR because it wants to open a PR for the last change which was already merged [15:36:57] and I’m thinking that its because the merge commit is new commit that wasn’t in the forked repo [15:46:34] [02mw-config] 07MacFan4000 closed pull request 03#2379: Remove nominornewtalk from bots - 13https://git.io/fNpbn [15:46:35] [02miraheze/mw-config] 07MacFan4000 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fNpAv [15:46:36] [02miraheze/mw-config] 07Amanda-Catherine 03116e062 - Remove nominornewtalk from bots (#2379) All edits, regardless if bot or not, or if minor or not, should always trigger the new messages prompt [15:49:03] Yeah, notice what happened here https://github.com/weatherwiki/mw-config [15:49:03] Title: [ GitHub - weatherwiki/mw-config: Production MediaWiki configuration ] - github.com [15:49:18] “1 commit ahead, 1 commit behind miraheze:master” [15:49:29] So now if I open another PR, it will try to merge that PR again [15:49:33] So I have to re-fork [15:50:07] The “1 commit ahead” was because I pushed directly to my repo and opened the PR from there. However, once the PR is merged, it should go back to “even with miraheze:master” [15:50:12] MacFan4000 ^ [15:50:33] any commits will cause that though [15:50:52] I don’t think it does if you squash merge [15:50:56] the chances of you making multiple commits over a period of time and no one else doing any is extremely low [15:51:17] I can open a new PR even if the branch is behind the master [15:51:25] I can’t open a new PR if it is ahead of the master [15:51:33] Because it will duplicate my last PIR [15:51:38] s/PIR/PR [15:51:38] AmandaCatherine meant to say: Because it will duplicate my last PR [15:53:06] And see now it wants to merge that last PR again https://github.com/miraheze/mw-config/compare/master...weatherwiki:master [15:53:07] Title: [ Comparing miraheze:master...weatherwiki:master · miraheze/mw-config · GitHub ] - github.com [15:53:13] Even though it’s already been merged [15:54:02] JohnLewis ^^ [15:55:14] probably then [15:55:38] Probably then what? [15:55:43] Was my theory right? [15:55:50] probably [15:56:33] Mind if I test it? (I’ll re-fork, make a null commit, and I’ll have you merge with a squash, and I’ll revert it right after) [15:56:41] wait [15:56:48] MacFan4000 did squash and merge [15:57:03] Ok, so why does it still think that there’s an extra commit? [15:57:22] because the meta data in the commit has changed probably [15:57:38] There haven’t been any other commits since that one [15:58:25] technically it's a different commit [15:58:43] because Mac is the committer but in your repo, you're the committer [15:59:37] So there’s no way to re-use my repo for multiple PRs [15:59:51] no, you'd need to use branches [16:00:10] ?? [16:00:31] edit from the miraheze repo [16:00:41] automates the whole process [16:01:20] But that creates a fork called “Amanda-Catherine/mw-config” [16:01:37] otherwise press the branch selector and create a new branch [16:01:49] So, I need to make a PR to my own repo first [16:01:55] yeah, but it'll make a new branch in your fork [16:02:10] So then can I merge my own PR? [16:02:20] And then push the PR to Miraheze master? [16:02:39] you don't want to edit the master branch or merge it in your repo [16:02:50] it'll make a branch which you can request to be merged into our repo [16:04:03] Okay, brand-new fork that is even https://github.com/weatherwiki/mw-config [16:04:04] Title: [ GitHub - weatherwiki/mw-config: Production MediaWiki configuration ] - github.com [16:04:07] So don’t edit that at all? [16:04:29] yeah, don't touch the master branch [16:04:39] you cant reuse branches [16:05:24] Ah, so click the “branch:master” dropdown? [16:05:27] And create a new branch [16:06:00] could do, but that'll base it on the master branch of your repo [16:06:07] so it's best to edit in the miraheze repo [16:06:34] PROBLEM - misc1 Puppet on misc1 is WARNING: WARNING: Puppet last ran 1 hour ago [16:07:52] * AmandaCatherine is still confused [16:08:11] So what you’re saying is that it is technically impossible to use https://github.com/weatherwiki/mw-config and keep it up to date [16:08:12] Title: [ GitHub - weatherwiki/mw-config: Production MediaWiki configuration ] - github.com [16:08:47] using the web editor, yeah [16:09:30] There’s another editor? [16:10:01] command line [16:10:26] But I’m assuming that I don’t have access to that [16:10:30] (i.e. sysadmin only) [16:10:52] no? git is universal [16:11:10] So I can edit the Miraheze command line? [16:11:16] That’s scary [16:11:31] no [16:11:39] you'd use your own repo [16:12:28] This is still confusing. I’ll just delete the entire organization of weatherwiki [16:12:42] I thought I’ve been able to keep forks up to date in the past [16:12:50] But, meh [16:26:57] Hmmm.. request for adoption by an IP https://meta.miraheze.org/wiki/Requests_for_adoption#collabvm [16:26:58] Title: [ Requests for adoption - Miraheze Meta ] - meta.miraheze.org [16:27:07] Does that get procedurally declined automatically? [16:29:01] JohnLewis ^ [16:29:36] yes [16:32:02] Time for lunch [17:46:50] Hmm.. no unread messages [17:46:55] That’s an interesting change [17:49:32] AmandaCatherine: there's not always that much around here [17:49:55] MacFan4000: https://phabricator.miraheze.org/T3491 - since you mentioned this, are you taking care of it? [17:49:56] Title: [ ⚓ T3491 LocalSetting.php and Photo Directory of wikiageing wiki ] - phabricator.miraheze.org [17:50:40] Reception123: I know, it’s just sometimes that I’ve come back to 100+ unread messages [17:50:53] Depends on the day of course [17:51:09] Not really, I was just wondering if the private was a concern, but now I know [17:51:26] Also, the wiki that was requested for adoption here https://meta.miraheze.org/wiki/Requests_for_adoption#collabvm.miraheze.org has vandalism on the main page [17:51:27] Title: [ Requests for adoption - Miraheze Meta ] - meta.miraheze.org [17:51:34] But I can’t revert it because the wiki is closed [17:51:35] MacFan4000: ok. if you want to do it feel free [17:51:56] AmandaCatherine: we are aware of the issues, hence Voidwalker's reply to the user [17:52:24] Isn’t it just as simple as remove the vandalism and be done? [17:52:34] It was likely done by a spammer/vandalbot during inactivity [17:53:02] Thing is, that wiki was made private for violating the content policy [17:53:22] It is a tricky case, that requires staff discussion first [17:53:36] Oh [17:53:36] most of the content on the wiki that looks like vandalism was added by the wiki administrators [17:53:52] So we’re dealing with rouge admins here? [17:53:59] And/or compromised admin accounts? [17:55:34] Probably not compromised accounts. [17:55:37] and this is an old case [17:55:53] Was it pre-CVT era? [17:56:09] Because if not, the vandalism shouldn’t have stayed there [17:56:38] And the only two logical reasons why an administrator would vandalize a wiki are either if they went rouge for some reason or if their account was compromised [17:57:10] AmandaCatherine: It was not necessarily vandalism [17:57:16] CVT wouldn’t matter anyway [17:57:28] They can’t read private wikis [17:57:38] Well it was public at the time [17:57:42] Only sysadmins/stewards can [17:58:38] Although, I don’t see in the global content policy where it says that profanity is not allowed, unless you consider that part of “A wiki must not create problems which make it difficult for other wikis.” [17:59:00] (Not that I’m endorsing it in any way, just stating what I can find factually) [17:59:25] AmandaCatherine: Yes, that is what would be consider [17:59:28] *considered [17:59:38] At Stewards' discretion [18:00:13] I think that the policy should be more clear: either we allow profanity globally and leave it to the local level to disallow it if they choose [18:00:26] Or we explicitly ban profanity globally [18:00:42] AmandaCatherine: It doesn't really work like that. Even in real life laws, there are some things that are up for discretion, not everything is said point blank. [18:00:50] profanity isn't the explicit issue here anyway [18:00:52] We can't specifically say "This is not allowed, this is not allowed" [18:01:12] Voidwalker: well, the first thing I saw on the main page is profanity in big letters [18:01:31] Yeah, I think he means it isn't the sole reason why [18:01:53] that is, quite honestly the cleanest case on the whole wiki [18:02:35] So if the entire wiki was vandalized... [18:02:43] Hi! Just contacting you to tell that here are no high priority open tasks. Nice job! [18:02:49] ...it’s likely a case of a rouge admin or an automated vandalbot [18:03:14] AmandaCatherine: No, as I said, we have reason to believe it was not "vandalism" but intentional [18:03:16] by the administrators [18:03:23] which were not "hacked" or "rogue" [18:03:38] ZppixBot i have a few high priority tasks. [18:03:39] jks [18:03:47] .priotasks [18:03:48] MacFan4000: There are no high priority open tasks. Nice job! [18:04:02] ZppixBot: make some up then [18:04:19] If the wiki started out fine, and then became vandalized, that’s the definition of a rouge admin [18:04:24] We bully ZppixBot too much, when the world is taken over by the bots, it won't be nice :P [18:04:25] Reception123: 2018-08-16 - 18:04:23 tell Reception123 No, I don't want to. [18:04:30] Some would like to call it a traitor [18:04:33] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [18:04:35] well i fucked it up [18:04:37] i meant .msg [18:04:46] lol [18:04:50] oh, I was like what, a reminder through ZppixBot what is going on [18:04:56] ZppixBot: ah I love that .msg [18:05:03] AmandaCatherine: don't think that's the case [18:05:05] reception123 No, I don't awnt to. Equal rights for all bots! [18:05:07] afaik, it was always like that [18:05:10] .msg Zppix test [18:05:15] it didn't work [18:05:16] Now spelling [18:05:19] ZppixBot: I thought bots couldn't make typos [18:05:22] .msg Zppix test [18:05:29] paladox: it has to be in a PM [18:05:33] oh [18:05:38] Bots are human too. Damn you! [18:05:47] paladox: and that would just send a message to Zppix from ZppixBot [18:05:48] it worked paladox [18:05:52] It won’t say anything back though [18:05:52] ok [18:05:53] ZppixBot: pretending to be a human now, eh? [18:05:53] heh [18:06:11] So why did a wiki get approved for creation if they were just going to post profanity/hate speech? [18:06:15] Reception123, who says I was never not human? [18:06:25] (Assuming it was post-global content policy era) [18:06:50] Because they didn’t say that was their purpose? [18:06:57] well why not? [18:06:58] xD [18:06:59] ZppixBot: the last 3 letters of your name [18:07:00] :PP [18:07:22] * AmandaCatherine mutes ZppixBot [18:07:33] Stop bullying me :P [18:07:39] Reception123, Bots can be human too you know, this is discrimination. [18:08:04] mutes AmandaCatherine [18:08:22] jk [18:08:32] who else is abusing my bot but me? [18:09:00] JohnLewis Reception123: why wasn’t the wiki deleted? [18:09:46] ZppixBot: Well, in any case you're more human than Paladoxbot, I'll give you that xD [18:09:47] Because in the assumption of good faith, time should be given to resolve issues. [18:10:37] Were any of the admins/crats stripped of their rights? [18:10:45] And/or their global accounts locked? [18:11:15] No because that defeats the purpose of letting them resolve the issue? [18:11:35] It could be anybody Zppix [18:11:45] Well, locking does, but just desyopping an admin who is acting rouge isn’t stopping anything except disruption [18:12:17] But deleting the content is the resolution [18:12:28] ZppixBot: I can look into the logs you know [18:12:48] taking that away from them means they a) can’t resolve it b) lose the motivation to [18:13:00] Depends on how you define “delete” - actually use the delete function in MediaWiki, just blank the page, ? [18:13:12] Replace the page with something else? [18:13:26] Well you described deleting and blanking so the former [18:14:08] Some might consider just blanking a page to be “soft deletion” since the average passerby may not know how to check the revision history [18:15:00] Maybe [18:15:05] Alright ZppixBot maintainers thats enough .msg please, its starting to be disruptive [18:15:09] just anything regarding removak [18:15:36] But blanking can be done without sysop under most circumstances [18:16:04] Does CVT get ratelimitted? [18:21:26] But if you revoke rights people are less likely to resolve + it’s heavy handed [18:22:33] Zppix: no, CVT have the noratelimit perm [18:22:41] Well, since the wiki was closed for inactivity before the issues were resolved, I think you could say that at that point, the time to fix it is over [18:23:43] Zppix: is there a guide or something for how to install stuff using piwikibot? I'd have no problem trying it out myself or maybe paladox could take a look, if you're busy [18:23:56] Reception123: i can link you to the piwikibot docs [18:23:57] Reception123 possibly though not sure [18:24:05] i have never used pywikibot [18:24:13] Reception123: https://www.mediawiki.org/wiki/Manual:Pywikibot [18:24:13] Title: [ Manual:Pywikibot - MediaWiki ] - www.mediawiki.org [18:24:17] paladox: well you do find a way to get anything to work, so :P [18:24:24] lol [18:24:25] heh [18:24:44] Reception123 https://www.wikidata.org/wiki/Wikidata:Pywikibot_-_Python_3_Tutorial [18:24:44] Reception123: https://www.mediawiki.org/wiki/Manual:Pywikibot/Installation/Toolforge [18:24:45] Title: [ Wikidata:Pywikibot - Python 3 Tutorial - Wikidata ] - www.wikidata.org [18:24:46] Title: [ Manual:Pywikibot/Installation/Toolforge - MediaWiki ] - www.mediawiki.org [18:24:47] Zppix: have you started anything yet? So I don't redo anything [18:24:55] Reception123: paladox i wouldnt start the bot for real though until i look at it just to be safe, cause as far as im concerned im the one responsible for it in terms of cloud services pov [18:25:06] heh [18:25:08] ah, I see all the maintainers are spamming me with links, so everyone's aware of stuff :D [18:25:10] Reception123: except for git clone on the tool account nope [18:25:27] Zppix: Oh, ok. Though if Signbot operates on it, it should be fine? [18:25:36] Reception123: wym? [18:25:43] Zppix: in that case, maybe we should wait for you? Do you think you'll be able to get it done this month? [18:26:01] "i look at it just to be safe, cause as far as im concerned im the one responsible for it in terms of cloud services pov" - well I mean it's used already with Signbot with commonswiki [18:26:04] Reception123: i dont mind if you set it up on testwiki under a test account but i want to be sure that works before moving it to an official acct [18:26:32] We could use the ZppixBot wiki account [18:26:42] well tha twould be after Zppix would check it [18:26:47] MacFan4000: that account is purely for ZppixBot to login to phab [18:26:50] before we could just do a "Testbot" account or something on testwiki [18:26:55] paladox: get to work! [18:26:55] MacFan4000: i perfer to have signbot use its own acct [18:27:22] Reception123 get what to work? I have no idea how to use pywikibot :) [18:27:24] MacFan4000: so if something were to happen we can still block signbot and not block ZppixBot on wiki you understand what im saying? [18:27:34] Yes [18:27:35] paladox: none of us do [18:27:44] paladox: you cant do anymore damage then i could [18:27:45] :P [18:27:48] lol [18:27:49] paladox: I'll do the installing, and you do the fixing when I break something xD [18:27:52] that's how it usually works [18:28:16] lol [18:28:17] ok [18:28:30] great, I even forgot what we called the toolforge project [18:28:32] great start for me [18:28:57] Reception123: mh-signbot [18:29:11] ah, I did miraheze-signbot [18:29:12] thanks MacFan4000 [18:31:37] Miraheze wikis can still use wikimedia commons images right? [18:32:04] Zppix: yes, of course [18:32:11] it's still enabled by default [18:32:14] Reception123: then why isnt this working at all? https://publictestwiki.com/wiki/Template:WIP [18:32:15] Title: [ Template:WIP - TestWiki ] - publictestwiki.com [18:32:28] Created an account for testing and password is sent via mail [18:32:31] paladox: ^ [18:32:36] MacFan4000: which email? [18:32:42] ok [18:32:43] Tool email [18:32:49] oh ok [18:32:54] MacFan4000: wow I didn't know that existed [18:32:55] ok great [18:32:59] paladox: why isn't commons working? [18:33:08] Reception123 what do you mean? [18:33:14] paladox: check the link Zppix sent [18:33:18] oh shut up spambots [18:33:38] !m Sigyn [18:33:38] <[d__d]> You're doing good work, Sigyn! [18:33:58] Reception123 ok [18:34:02] Zppix: pywikibot is pretty large [18:34:06] Reception123 uh, i only see the password [18:34:12] Reception123: all toolforge tools have emails that are (usually) sent to the maintainers, the email address is tools.toolname (at) tools.wmflabs.org [18:34:12] paladox: for? [18:34:19] Reception123 https://publictestwiki.com/wiki/Main_Page [18:34:19] Title: [ TestWiki ] - publictestwiki.com [18:34:31] Reception123: and wmf has plenty of space? [18:34:32] oh i am not on the tool then [18:34:41] I'm doing too many things at the same time I'm confused now (signbot, Zppix' commons issues, image import) [18:34:51] Zppix: ik, just saying [18:34:51] Ignore me [18:34:56] just focus on bot [18:35:00] ill figure my stuff out [18:35:02]