[00:04:19] <icinga-miraheze>	 PROBLEM - gluster1 Puppet on gluster1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[/mnt/mediawiki-static]
[00:53:54] <MH-Discord>	 <Doug> > The current job setup is kinda redneck it legit is just a cron that runs a script for all wikis > We should really move to way WM does it Oh wow, yeah, that's interesting > ^ yeah
[04:23:41] <icinga-miraheze>	 PROBLEM - wiki.azimuth.navy - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'wiki.azimuth.navy' expires in 15 day(s) (Fri 16 Oct 2020 04:16:08 GMT +0000).
[04:23:50] <Not>	 [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUMdZ
[04:23:51] <Not>	 [02miraheze/ssl] 07MirahezeSSLBot 038483f5e - Bot: Update SSL cert for wiki.azimuth.navy
[04:37:16] <icinga-miraheze>	 RECOVERY - wiki.azimuth.navy - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.azimuth.navy' will expire on Tue 15 Dec 2020 05:21:14 GMT +0000.
[05:59:42] <icinga-miraheze>	 PROBLEM - mr.gyaanipedia.co.in - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for mr.gyaanipedia.co.in could not be found
[05:59:42] <icinga-miraheze>	 PROBLEM - wiki.seamly.net - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for wiki.seamly.net could not be found
[06:06:23] <icinga-miraheze>	 RECOVERY - mr.gyaanipedia.co.in - reverse DNS on sslhost is OK: rDNS OK - mr.gyaanipedia.co.in reverse DNS resolves to cp7.miraheze.org
[06:06:24] <icinga-miraheze>	 RECOVERY - wiki.seamly.net - reverse DNS on sslhost is OK: rDNS OK - wiki.seamly.net reverse DNS resolves to cp6.miraheze.org
[06:47:57] <icinga-miraheze>	 RECOVERY - jobrunner2 APT on jobrunner2 is OK: APT OK: 9 packages available for upgrade (0 critical updates).
[10:05:12] <Not>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUDnU
[10:05:13] <Not>	 [02miraheze/services] 07MirahezeSSLBot 03888e94d - BOT: Updating services config for wikis
[10:05:25] <MH-Discord>	 <Avengium (Ángel)> Hi
[10:05:42] <MH-Discord>	 <Avengium (Ángel)> How can i help Miraheze admins with a simple task?
[11:11:45] <icinga-miraheze>	 PROBLEM - wiki.zymonic.com - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'wiki.zymonic.com' expires in 15 day(s) (Fri 16 Oct 2020 11:07:07 GMT +0000).
[11:15:03] <Not>	 [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUD8r
[11:15:05] <Not>	 [02miraheze/ssl] 07MirahezeSSLBot 0395cdafc - Bot: Update SSL cert for wiki.zymonic.com
[11:25:13] <icinga-miraheze>	 RECOVERY - wiki.zymonic.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.zymonic.com' will expire on Tue 29 Dec 2020 10:14:56 GMT +0000.
[12:22:06] <MirahezeBot>	 Hello wm-bot52! If you have any questions, feel free to ask and someone should answer soon.
[12:55:31] <Reception123>	 !log reception@jobrunner1:/srv/mediawiki/w/maintenance$ sudo -u www-data php initSiteStats.php --wiki snapwikiwiki --update
[12:55:35] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log
[12:57:46] <Reception123>	 !log reception@jobrunner1:/srv/mediawiki/w/maintenance$ sudo -u www-data php updateSpecialPages.php --wiki snapwikiwiki
[12:58:16] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log
[13:12:03] <Reception123>	 !log reception@jobrunner1:/srv/mediawiki/w/maintenance$ sudo -u www-data php rebuildall.php --wiki snapwikiwiki
[13:12:08] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log
[14:05:11] <Not>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUDi4
[14:05:13] <Not>	 [02miraheze/services] 07MirahezeSSLBot 030c2a06e - BOT: Updating services config for wikis
[14:06:59] <Not>	 [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUDir
[14:07:00] <Not>	 [02miraheze/mw-config] 07paladox 03ff1fb34 - ldap: Log to ldap.log
[14:08:06] <Not>	 [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUDiP
[14:08:08] <Not>	 [02miraheze/mw-config] 07paladox 0363ade20 - ldap: 'realname' => 'givenName'
[14:24:41] <MH-Discord>	 <Hispano76> hola @Avengium (Ángel) no sé que tipo de tareas estás preguntando. Pero empezar con traducir páginas en MetaWiki al español, hay algunas que están incompletas o desactualizadas.  https://meta.miraheze.org/wiki/Special%3ALanguageStats
[14:24:42] <MirahezeBot>	 [ Language statistics - Miraheze Meta ] - meta.miraheze.org
[14:25:54] <Not>	 [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUDXC
[14:25:56] <Not>	 [02miraheze/mw-config] 07paladox 0351a9622 - Grant managewiki-restricted to sysop on ldapwikiwiki
[14:37:32] <icinga-miraheze>	 PROBLEM - lama.madooa.org - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'lama.madooa.org' expires in 15 day(s) (Fri 16 Oct 2020 14:31:07 GMT +0000).
[14:37:38] <Not>	 [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUD18
[14:37:39] <Not>	 [02miraheze/ssl] 07MirahezeSSLBot 03ff0faea - Bot: Update SSL cert for lama.madooa.org
[14:44:17] <icinga-miraheze>	 RECOVERY - lama.madooa.org - LetsEncrypt on sslhost is OK: OK - Certificate 'lama.madooa.org' will expire on Tue 15 Dec 2020 21:43:01 GMT +0000.
[14:50:43] <Not>	 [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUDMo
[14:50:44] <Not>	 [02miraheze/mw-config] 07paladox 034352c4d - wgGlobalPreferencesDB set to ldapwikiwiki for ldapwikiwiki
[14:53:14] <MH-Discord>	 <Doug> > How can i help Miraheze admins with a simple task? @Avengium (Ángel) What do you want to help with?
[14:54:17] <MH-Discord>	 <Doug> > <Reception123> !log reception@jobrunner1:/srv/mediawiki/w/maintenance$ sudo -u www-data php updateSpecialPages.php --wiki snapwikiwiki @Reception123 Ooh, what was that for? That sounds interesting. 🙂
[14:54:39] <Reception123>	 @Doug Special:ActiveUsers not updating
[14:57:10] <MH-Discord>	 <Doug> > <Reception123> @Doug Special:ActiveUsers not updating @Reception123 Ah, cool. Yeah, I wish that special page could be transcluded and also linked to directly with [[Special:ActiveUsers/sysop]]. Currently, the way the user groups are set, they're not set to use the actual group names, so those wikilinks don't work. I have to use short URLs on TestWiki to link to those pages.
[14:57:32] <MH-Discord>	 <Doug> Is that a recurring problem, though, with that special page not updating?
[14:59:30] <Reception123>	 well the issue was a user who was "active" wasn't showing up on the page
[14:59:55] <MH-Discord>	 <Doug> nudges @RhinosF1 and @Zppix to see if we could have MirahezeBots and wm-bot interface with MH-Discord to allow Discord users to use MirahezeBots and wm-bot commands like s/word/word so he can correct something he said in #irc-relay on Discord
[15:00:58] <MH-Discord>	 <Doug> > <Reception123> well the issue was a user who was "active" wasn't showing up on the page @Reception123 Oh yeah, the same thing is happening with Southparkfan on Metawiki, in that he doesn't show up as an "active administrator" or "active bureaucrat" despite having 1 or more log actions in the last month.
[15:02:33] <MH-Discord>	 <RhinosF1> @Doug we don't do the development of MH-Discord
[15:02:50] <MH-Discord>	 <Doug> > @Doug we don't do the development of MH-Discord @RhinosF1 Who does that?
[15:02:51] <MH-Discord>	 <RhinosF1> I know some relay style stuff allow you to type command: x
[15:03:05] <MH-Discord>	 <RhinosF1> Which then send the command and sender on 2 lines
[15:03:25] <MH-Discord>	 <RhinosF1> https://github.com/reactiflux/discord-irc/issues
[15:03:26] <MirahezeBot>	 [ Issues · reactiflux/discord-irc · GitHub ] - github.com
[15:03:58] <MH-Discord>	 <Doug> oh I thought MH-Discord meant "Miraheze," but I guess that's just the bot's name on this server, not necessarily who develops it.
[15:05:23] <MH-Discord>	 <RhinosF1> It's just the configured irc nick
[15:05:31] <MH-Discord>	 <RhinosF1> MH is Miraheze
[15:05:40] <MH-Discord>	 <RhinosF1> But yeah it's developed separately
[15:11:44] <MH-Discord>	 <Doug> > It's just the configured irc nick @RhinosF1 But doesn't the bot interpret the username that said it as "MH-Discord," so it would thus be unable to amend what one said on Discord, unless they changed their display name temporarily to MH-Discord, I guess?
[15:13:19] <MH-Discord>	 <Zppix> No.
[15:13:31] <MH-Discord>	 <Zppix> Theres no way to run a command from discord on irc
[15:13:48] <MH-Discord>	 <Zppix> thats an upstream issue
[15:14:05] <MH-Discord>	 <Zppix> all the relay bot is, is a configured version of an already made software
[15:15:42] <MH-Discord>	 <Doug> ah, okay, I guess I could file a task upstream. Do they use Phabricator do you know off hand?
[15:17:17] <MH-Discord>	 <Zppix> I think Rhinos already linked to the task
[15:18:00] <MH-Discord>	 <Zppix> if not use https://github.com/reactiflux/discord-irc/issues
[15:18:01] <MirahezeBot>	 [ Issues · reactiflux/discord-irc · GitHub ] - github.com
[15:18:01] <MH-Discord>	 <Doug> > I think Rhinos already linked to the task @Zppix Nope, only the GitHub repository. Not sure what they use for bug tracking and feature requesting.
[15:19:02] <MH-Discord>	 <Doug> Ah, GitHub has a built-in bug tracker/feature request feature. Guess lots of projects don't really use it and prefer to use Phab or BugZilla because it's not that robust?
[15:20:14] <MH-Discord>	 <Zppix> correct
[15:20:34] <MH-Discord>	 <Zppix> that and they are open source
[15:23:22] <MH-Discord>	 <Doug> > that and they are open source Good point. Despite GitHub being used for open source projects, the entire code for GitHub itself is not open source, as far as I'm aware. For some users, that's not ideal, and for others, it may be a dealbreaker.
[15:23:29] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 22.45, 21.77, 18.24
[15:25:29] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 29.19, 23.35, 19.15
[15:27:29] <icinga-miraheze>	 RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 16.55, 20.21, 18.51
[16:20:20] <Not>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUDbi
[16:20:22] <Not>	 [02miraheze/services] 07MirahezeSSLBot 03ef7a601 - BOT: Updating services config for wikis
[16:52:04] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 21.67, 19.35, 17.35
[16:54:03] <icinga-miraheze>	 RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 17.35, 18.95, 17.48
[17:17:34] <icinga-miraheze>	 PROBLEM - db7 Check MariaDB Replication on db7 is CRITICAL: MariaDB replication - both - CRITICAL - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 160s
[17:23:54] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 28.94, 24.96, 20.61
[17:27:52] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 22.48, 23.88, 21.19
[17:29:51] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 25.67, 23.65, 21.37
[17:37:47] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 20.57, 23.48, 22.52
[17:42:05] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 50.51, 29.03, 24.44
[17:49:38] <icinga-miraheze>	 PROBLEM - gluster1 Current Load on gluster1 is CRITICAL: CRITICAL - load average: 10.43, 6.40, 4.62
[17:51:42] <icinga-miraheze>	 PROBLEM - gluster1 Current Load on gluster1 is WARNING: WARNING - load average: 7.14, 6.25, 4.77
[17:53:38] <icinga-miraheze>	 RECOVERY - gluster1 Current Load on gluster1 is OK: OK - load average: 3.72, 5.43, 4.66
[17:55:40] <MH-Discord>	 <Avengium (Ángel)> @Hispano76  Hola Hispano. ¿que tal van las tasks de Miraheze Phabricator?
[17:56:50] <MH-Discord>	 <Avengium (Ángel)> @Doug i don't know the type of task. Depending on the task i see if i know how to handle it or not.
[18:07:28] <MH-Discord>	 <R4356th> I could help with basic configuration and JavaScript, CSS , Python etc if you accepted configurations.
[18:08:02] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 13.42, 18.09, 23.23
[18:10:02] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 30.23, 22.29, 24.09
[18:10:34] <MH-Discord>	 <Avengium (Ángel)> that sounds great! 🎉 🥳 👍
[18:13:07] <MH-Discord>	 <Doug> > @Doug i don't know the type of task. Depending on the task i see if i know how to handle it or not. @Avengium (Ángel) Yeah, if you know some languages and are familiar with the Translate extension, Meta can always use translators and translation administrators (i.e., ability to mark updated pages for translation and prepare untranslated pages). Also, if you know what to look for, don't mind adding {{subst:Unsigned}} signatures, tagging
[18:13:08] <MH-Discord>	 out of scope pages with {{delete}}, and fixing formatting errors on talk pages and noticeboards per WP:LISTGAP, we can still use a few more patrollers on Meta.
[18:14:03] <MH-Discord>	 <Doug> So those would be a couple things. Also, we can always use more wiki creators, if you're familiar with Content Policy, what to approve, what to decline, and when to request more information, specially wiki creators that know multiple languages.
[18:14:11] <MH-Discord>	 <Avengium (Ángel)> I'm currently helping translate some specific words and terms to spanish, as Hispano76 suggested
[18:14:23] <MH-Discord>	 <Doug> > I'm currently helping translate some specific words and terms to spanish, as Hispano76 suggested @Avengium (Ángel) Oh, great. 🙂
[18:14:51] <MH-Discord>	 <Avengium (Ángel)> I'm not familiar with wiki admin at all. Content Policy included 😂 ,  😅
[18:15:08] <MH-Discord>	 <Doug> > I'm not familiar with wiki admin at all. Content Policy included 😂 ,  😅 @Avengium (Ángel) ah, okay, no worries then 🙂
[18:16:21] <MH-Discord>	 <Avengium (Ángel)> Patrollers is a thing i could do i think. but maybe in the future
[18:20:21] <Not>	 [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUyki
[18:20:22] <Not>	 [02miraheze/puppet] 07paladox 034cc3fd8 - ldap: Set ppolicy
[18:22:41] <hispano76>	 :)
[18:24:11] <icinga-miraheze>	 PROBLEM - ldap1 Puppet on ldap1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Openldap_overlay[ppolicy on cn=config]
[18:25:57] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 14.43, 19.98, 23.87
[18:31:59] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 28.39, 22.31, 23.17
[18:37:57] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 18.31, 21.99, 23.13
[18:40:01] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 26.30, 22.73, 23.20
[18:40:37] <Not>	 [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUytk
[18:40:38] <Not>	 [02miraheze/puppet] 07paladox 035e51a8f - Fix
[18:42:10] <icinga-miraheze>	 RECOVERY - ldap1 Puppet on ldap1 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures
[18:47:38] <icinga-miraheze>	 RECOVERY - db7 Check MariaDB Replication on db7 is OK: MariaDB replication - both - OK - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 1s
[18:53:58] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 11.15, 18.73, 23.06
[18:59:58] <icinga-miraheze>	 RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 15.20, 15.69, 20.24
[19:12:03] <Not>	 [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUyYb
[19:12:05] <Not>	 [02miraheze/mw-config] 07paladox 0388f6844 - Make wgLDAPPasswordHash default to []
[19:12:40] <Not>	 [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUyOk
[19:12:42] <Not>	 [02miraheze/puppet] 07paladox 037b50c8b - Update openldap.pp
[19:13:54] <Not>	 [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUyOG
[19:13:55] <Not>	 [02miraheze/mw-config] 07paladox 03d88e6e8 - Update LocalExtensions.php
[20:45:03] <Not>	 [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JUyCA
[20:45:05] <Not>	 [02miraheze/mediawiki] 07paladox 038044ec4 - Update WikiForum
[21:01:47] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 24.05, 18.23, 15.44
[21:03:47] <icinga-miraheze>	 RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 18.19, 17.60, 15.53
[21:55:10] <MirahezeBot>	 Hello syno! If you have any questions, feel free to ask and someone should answer soon.
[21:59:06] <syno>	 Hello guys, why are most open proxies not globally locked, I’ve been blocking a lot on the test Wiki but they are not globaly locked.Thanks
[22:09:53] <dmehus>	 @syno We used to have Proxybot, which handled this, but it stopped functioning some time ago, as I understand it. I'm not sure what the easiest way to report open proxies is currently. In theory, stewards' noticeboard, but that could potentially fill up awfully fast. @Zppix, what do you recommend? E-mail to cvt{{@}}miraheze[dot]org?
[22:24:29] <icinga-miraheze>	 PROBLEM - wiki.vinesh.eu.org - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for wiki.vinesh.eu.org could not be found
[22:24:29] <icinga-miraheze>	 PROBLEM - www.openonderwijs.org - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for www.openonderwijs.org could not be found
[22:24:30] <icinga-miraheze>	 PROBLEM - sims.miraheze.org - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for sims.miraheze.org could not be found
[22:26:00] <icinga-miraheze>	 PROBLEM - wiki.villagecollaborative.net - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for wiki.villagecollaborative.net could not be found
[22:26:01] <icinga-miraheze>	 PROBLEM - fc.songcontests.eu - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for fc.songcontests.eu could not be found
[22:26:04] <icinga-miraheze>	 PROBLEM - www.dariawiki.org - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for www.dariawiki.org could not be found
[22:26:05] <icinga-miraheze>	 PROBLEM - wiki.patriam.cc - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for wiki.patriam.cc could not be found
[22:26:05] <icinga-miraheze>	 PROBLEM - www.schulwiki.de - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for www.schulwiki.de could not be found
[22:30:20] <Not>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUyuI
[22:30:22] <Not>	 [02miraheze/services] 07MirahezeSSLBot 033a3bb66 - BOT: Updating services config for wikis
[22:31:16] <icinga-miraheze>	 RECOVERY - www.openonderwijs.org - reverse DNS on sslhost is OK: rDNS OK - www.openonderwijs.org reverse DNS resolves to cp6.miraheze.org
[22:31:17] <icinga-miraheze>	 RECOVERY - wiki.vinesh.eu.org - reverse DNS on sslhost is OK: rDNS OK - wiki.vinesh.eu.org reverse DNS resolves to cp7.miraheze.org
[22:31:17] <icinga-miraheze>	 RECOVERY - sims.miraheze.org - reverse DNS on sslhost is OK: rDNS OK - sims.miraheze.org reverse DNS resolves to cp6.miraheze.org
[22:32:53] <icinga-miraheze>	 RECOVERY - wiki.villagecollaborative.net - reverse DNS on sslhost is OK: rDNS OK - wiki.villagecollaborative.net reverse DNS resolves to cp6.miraheze.org
[22:32:59] <icinga-miraheze>	 RECOVERY - fc.songcontests.eu - reverse DNS on sslhost is OK: rDNS OK - fc.songcontests.eu reverse DNS resolves to cp7.miraheze.org
[22:33:02] <icinga-miraheze>	 RECOVERY - www.dariawiki.org - reverse DNS on sslhost is OK: rDNS OK - www.dariawiki.org reverse DNS resolves to cp7.miraheze.org
[22:33:02] <icinga-miraheze>	 RECOVERY - wiki.patriam.cc - reverse DNS on sslhost is OK: rDNS OK - wiki.patriam.cc reverse DNS resolves to cp7.miraheze.org
[22:33:03] <icinga-miraheze>	 RECOVERY - www.schulwiki.de - reverse DNS on sslhost is OK: rDNS OK - www.schulwiki.de reverse DNS resolves to cp7.miraheze.org
[23:22:21] <MH-Discord>	 <Zppix> @Doug proxybot was a bot I discontinued mostly because I lost interest and because I lost majority of the source code. I would recommend either
[23:26:39] <dmehus>	 @Zppix Ah, yeah, I knew it was discontinued, but didn't know the reasons. That's too bad you lost the source code, though. I think @RhinosF1 is planning on working on a new addition to one of the Miraheze bots to alert @CVT of open proxies, but yeah, as to reporting them, I will let @syno know next time I see her
[23:28:04] <dmehus>	 .tell syno @Zppix said that can report open proxies through either method, `cvt{{@}}miraheze[dot]org` or alternatively via [[stewards' noticeboard]]. In either case, it's probably best to report them in a batch list of some sort
[23:28:04] <MirahezeBot>	 dmehus: I'll pass that on when syno is around.
[23:29:04] <dmehus>	 ~~--~~
[23:30:27] <MH-Discord>	 <Doug> > Patrollers is a thing i could do i think. but maybe in the future @Avengium (Ángel) Okay, just let me know whenever you are ready and have time to commit to it.