[10:20:00] <RhinosF1>	 niko: can you add litharge to -sre
[10:29:24] <niko>	 RhinosF1: hi, the litharge needs +o there
[10:30:10] <RhinosF1>	 niko: done
[10:30:55] <RhinosF1>	 Oh no
[10:31:00] <RhinosF1>	 Reception|away: can you ^
[10:32:33] <niko>	 RhinosF1: would you like default expiration for new bans/quiets on -sre ?
[10:32:44] <RhinosF1>	 Please
[10:32:50] <niko>	 1 day ?
[10:33:33] <niko>	 all done, ( expect the +o )
[10:35:56] <RhinosF1>	 Ye
[11:58:26] <Reception|away>	 Done
[12:03:07] <MacFan4000>	 niko: The GitHub notification bot that we use (not run by us) appears to have been klined the other day by Ozone because somebody (not us) had it in their channel without having the bot exempted. Would it be possible to un-kline it?
[12:03:45] <MacFan4000>	 07:06     ⇐︎ Not-4c5b quit (~notifico@ec2-52-3-50-241.compute-1.amazonaws.com): Killed (ozone (No Spam))
[12:04:15] <MacFan4000>	 I know a kill isn’t the same as a Kline, but it hasn’t been able to connect since
[12:04:31] <niko>	 sure, one sec
[12:07:03] <niko>	 MacFan4000: i see no active bans related to that
[12:08:00] <MacFan4000>	 Hmm, ok
[20:41:13] <niko>	 MacFan4000: aws ranges are salsified that explains why the bot can't send notification
[20:52:48] <dmehus>	 niko, what options do we or the Notifico project and/or Libera.Chat have to correct this, particularly since this wasn't a problem on Freenode?
[20:53:32] <niko>	 is the ip static ?
[20:54:18] <dmehus>	 Not sure off hand, I'd have to check with MacFan4000.
[20:54:48] <dmehus>	 Could we whitelist all AWS IPs on that range? I don't suspect spambots can afford to pay for expensive AWS infrastructure
[20:55:28] <RhinosF1>	 dmehus: spambots can afford anything
[20:56:06] <niko>	 dmehus: i 'm not familiar with aws infra and what range implies in this cases
[20:58:56] <dmehus>	 niko, was thinking the 2.52.0.0/16 or 2.52.50.0./24
[20:59:02] <dmehus>	 for starters
[20:59:32] <dmehus>	 oops
[20:59:36] <dmehus>	 I had that wrong
[21:00:25] <niko>	 dmehus: please confirm twice, after i will poke to infr
[21:00:27] <niko>	 infra
[21:00:36] <dmehus>	 s/2.52.0.0\/16 or 2.52.50.0.\/24/52.3.0\/16 or 52.3.50.\/24
[21:00:36] <MirahezeBot>	 dmehus meant to say: niko, was thinking the 52.3.0/16 or 52.3.50./24
[21:01:00] <niko>	 16 is wide
[21:01:12] <dmehus>	 yeah
[21:01:25] <MacFan4000>	 The operator says the issue is that the bot doesn’t support newer ssl protocols currently
[21:01:34] <dmehus>	 oh
[21:01:43] <niko>	 newer ?
[21:01:52] <niko>	 ha
[21:02:04] <dmehus>	 MacFan4000, could Notifico not run on the non-SSL 6667 port instead?
[21:02:49] <MacFan4000>	 16:07 <TkTech> If it's configured for SSL and non-SSL, it merges the networks together and prefers SSL
[21:02:56] <RhinosF1>	 niko: it's python2
[21:03:15] <MacFan4000>	 It tries to minimize the amount of connections coming from the server
[21:03:33] <RhinosF1>	 Looks like it's using an old cipher
[21:03:37] <dmehus>	 oh TkTech is the Notifico developer? I just DMed them a few days ago on Freenode :D
[21:03:48] <RhinosF1>	 Yes they are
[21:03:55] <dmehus>	 ah, cool :)
[21:06:40] <niko>	 MacFan4000: do you/he know which ranges used ?
[21:07:52] <RhinosF1>	 niko: maybe bring this to #notifico