2024/11/06

Newest at the top

2024-11-06 19:29:15 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 276 seconds)
2024-11-06 19:28:19 +0100 <geekosaur> that was only activated yesterday, it remains to be seen how much it's contributing because the bot spam had been going on for weeks (it's largely why hoogle was down a lot, apparently)
2024-11-06 19:27:07 +0100 <briandaed> like geekosaur said, it's probably an effect of 'bot fighting' functionality from cloudflare, sclv and chreekat can shed some light..
2024-11-06 19:26:27 +0100 <jco> I see, thanks...
2024-11-06 19:24:51 +0100 <institor> maybe the app server is overloaded
2024-11-06 19:24:42 +0100 <institor> that would explain the intermittent behavior
2024-11-06 19:23:53 +0100 <geekosaur> and ignoring things like robots.txt
2024-11-06 19:23:44 +0100 <geekosaur> from what I've seen, it seems like a lot of AI crawlers have been hammering hackage and hoogle
2024-11-06 19:23:13 +0100ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 248 seconds)
2024-11-06 19:22:36 +0100 <jco> Hey, what's up with https://hackage.haskell.org? Get 503s and it feels like that site has been having problems for a while. https://status.haskell.org seems to indicate there's an ongoing incident. Does anyone here know more about this?
2024-11-06 19:19:59 +0100wootehfoot(~wootehfoo@user/wootehfoot) wootehfoot
2024-11-06 19:17:54 +0100jco(~jco@78-70-217-44-no600.tbcn.telia.com) jco
2024-11-06 19:07:32 +0100 <statusbot6> Status update: there is a network outage affecting hackage, we are investigating -- http://status.haskell.org/pages/incident/537c07b0cf1fad5830000093/672bb063281978053cb3d85e
2024-11-06 19:01:58 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich
2024-11-06 18:57:28 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 245 seconds)
2024-11-06 18:35:16 +0100briandaed(~root@185.234.210.211.r.toneticgroup.pl)
2024-11-06 18:31:36 +0100kuribas(~user@ip-188-118-57-242.reverse.destiny.be) (Remote host closed the connection)
2024-11-06 18:29:48 +0100ljdarj1ljdarj
2024-11-06 18:29:48 +0100ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 244 seconds)
2024-11-06 18:27:32 +0100ljdarj1(~Thunderbi@user/ljdarj) ljdarj
2024-11-06 18:19:18 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich
2024-11-06 18:13:52 +0100pabs3(~pabs3@user/pabs3) pabs3
2024-11-06 18:10:46 +0100jrm(~jrm@user/jrm) jrm
2024-11-06 18:09:57 +0100Guest7(~Guest7@syn-172-249-181-078.res.spectrum.com) (Ping timeout: 256 seconds)
2024-11-06 18:09:17 +0100jrm(~jrm@user/jrm) (Quit: ciao)
2024-11-06 18:00:51 +0100pabs3(~pabs3@user/pabs3) (Ping timeout: 276 seconds)
2024-11-06 17:51:57 +0100sprotte24(~sprotte24@p200300d16f45f600c5ad94218b2aa1c2.dip0.t-ipconnect.de) (Quit: Leaving)
2024-11-06 17:48:16 +0100euleritian(~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de)
2024-11-06 17:48:01 +0100euleritian(~euleritia@dynamic-176-007-150-185.176.7.pool.telefonica.de) (Read error: Connection reset by peer)
2024-11-06 17:47:08 +0100son0p(~ff@186.119.84.155) son0p
2024-11-06 17:44:48 +0100merijn(~merijn@77.242.116.146) (Ping timeout: 265 seconds)
2024-11-06 17:44:48 +0100chele(~chele@user/chele) (Remote host closed the connection)
2024-11-06 17:38:46 +0100Smiles(uid551636@id-551636.lymington.irccloud.com) (Quit: Connection closed for inactivity)
2024-11-06 17:33:27 +0100TonyStone(~TonyStone@user/TonyStone) TonyStone
2024-11-06 17:30:58 +0100tomboy64(~tomboy64@user/tomboy64) tomboy64
2024-11-06 17:30:35 +0100 <Inst> given certain events
2024-11-06 17:30:27 +0100 <Inst> probably, and now is not a good time
2024-11-06 17:30:19 +0100 <EvanR> or confused
2024-11-06 17:30:14 +0100 <EvanR> you're misleading
2024-11-06 17:29:08 +0100 <Inst> i mean that purely functional programming, as an advertising phrase, at least, is misleading
2024-11-06 17:28:42 +0100 <Inst> erm, GHCup upkeep
2024-11-06 17:28:20 +0100 <Inst> you didn't agree to the bet, so i can't try to cajole you into passing maerwald some money for GHC upkeep
2024-11-06 17:28:06 +0100 <Inst> onlineapp.d(20): Error: `pure` function `onlineapp.bigPow` cannot call impure function `std.stdio.writefln!(char, BigInt).writefln`
2024-11-06 17:27:23 +0100merijn(~merijn@77.242.116.146) merijn
2024-11-06 17:27:15 +0100 <EvanR> which is true
2024-11-06 17:27:13 +0100 <EvanR> just that it's unpopular
2024-11-06 17:27:01 +0100 <EvanR> I don't know what that refers to, but anyway, you're not supporting "pure functional programming is meaningless"
2024-11-06 17:26:28 +0100 <Inst> if i win, will you donate to maerwald?
2024-11-06 17:26:26 +0100merijn(~merijn@77.242.116.146) (Ping timeout: 265 seconds)
2024-11-06 17:26:13 +0100 <EvanR> I wager $10 that it's for documentation purposes and doesn't actually stop side effects