2024/11/04

Newest at the top

2024-11-04 19:10:02 +0100gvg(~dcd@user/gvg) (Ping timeout: 255 seconds)
2024-11-04 19:08:17 +0100 <tomsmeding> that sample is indeed odd
2024-11-04 19:08:12 +0100 <briandaed> yeah, moved from hoogle to fw/ids/ips whatever
2024-11-04 19:07:44 +0100 <int-e> (which /may/ be easy to filter before they burden the CPU unduly but it's still work)
2024-11-04 19:07:20 +0100 <briandaed> https://discourse.haskell.org/t/hoogle-appears-to-be-down/10408/21
2024-11-04 19:07:07 +0100 <int-e> and everything that looks like it accepts parameters gets hammered with attempts to do SQL injection
2024-11-04 19:07:01 +0100 <tomsmeding> (link?)
2024-11-04 19:06:54 +0100 <briandaed> I also don't suspect spam or malicious activities, rather some misconfigured tool, but I saw only limited sample on discourse
2024-11-04 19:06:47 +0100ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 265 seconds)
2024-11-04 19:06:18 +0100 <tomsmeding> (and it's been up and linked to for more than a year now)
2024-11-04 19:06:10 +0100 <tomsmeding> the playground doesn't get spam like that
2024-11-04 19:06:05 +0100 <tomsmeding> and that happens enough times per second to bring the site to a crawl?
2024-11-04 19:05:50 +0100 <dolio> From what I heard, it doesn't sound like dos. It sounds like the internet is full of bots who will search for things like "password" on any web form hoping to get lucky.
2024-11-04 19:05:42 +0100 <tomsmeding> (though if it's really a DOS then it would be worth checking if it comes from a small number of IPs)
2024-11-04 19:05:40 +0100 <briandaed> in my narrow mind spam is sending some useless messages (sometimes malicious), while ddos wants service to be down
2024-11-04 19:04:35 +0100 <tomsmeding> is there a difference?
2024-11-04 19:04:26 +0100 <briandaed> not sure if we should classify it as a spam or rather (d)dos
2024-11-04 19:01:57 +0100 <tomsmeding> (if you know better: please let me know!)
2024-11-04 19:01:57 +0100morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 248 seconds)
2024-11-04 19:01:19 +0100 <tomsmeding> (and, what's more, it's also counterproductive with things like CGNAT, or big schools having a small number of external IPs)
2024-11-04 19:00:26 +0100 <tomsmeding> IP rate limiting is pointless with IPv6
2024-11-04 19:00:03 +0100 <tomsmeding> ultimately spam protection is just really quite hard without relying on internet backbone providers like cloudflare
2024-11-04 18:57:29 +0100tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net) tzh
2024-11-04 18:57:23 +0100morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-11-04 18:55:13 +0100Digitteknohippie(~user@user/digit) (Ping timeout: 252 seconds)
2024-11-04 18:54:53 +0100 <briandaed> more core/threads would help?
2024-11-04 18:54:19 +0100 <sclv> i think its compute bound and suspect its just the hoogle code isn't super load efficient on some things
2024-11-04 18:53:45 +0100 <briandaed> sclv are these spam queries network(io) bound?
2024-11-04 18:44:28 +0100alp(~alp@2001:861:e3d6:8f80:8ee1:f46d:3f90:227c)
2024-11-04 18:31:39 +0100Digitteknohippie(~user@user/digit) Digit
2024-11-04 18:31:38 +0100Digit(~user@user/digit) (Ping timeout: 245 seconds)
2024-11-04 18:30:45 +0100LainExperiments(~LainExper@user/LainExperiments) LainExperiments
2024-11-04 18:18:25 +0100Leonard26(~Leonard26@49.236.10.26) (Quit: Client closed)
2024-11-04 18:17:29 +0100target_i(~target_i@user/target-i/x-6023099) (Quit: leaving)
2024-11-04 18:14:31 +0100Tuplanolla(~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) Tuplanolla
2024-11-04 18:08:12 +0100machinedgod(~machinedg@d108-173-18-100.abhsia.telus.net) (Ping timeout: 244 seconds)
2024-11-04 18:01:12 +0100hiredman(~hiredman@frontier1.downey.family) hiredman
2024-11-04 18:00:55 +0100LainExperiments(~LainExper@user/LainExperiments) (Quit: Client closed)
2024-11-04 18:00:54 +0100morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 246 seconds)
2024-11-04 17:56:34 +0100morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-11-04 17:55:51 +0100 <sclv> what we need is a skilled admin to join us and help configure it to knock out the spam -- or maybe someone to work on making the code more efficient to handle load, or both :-)
2024-11-04 17:52:39 +0100comerijn(~merijn@77.242.116.146) (Ping timeout: 260 seconds)
2024-11-04 17:48:54 +0100spew(~spew@201.141.99.170) spew
2024-11-04 17:46:47 +0100 <haskellbridge> <hellwolf> or, we live with chances, which kinda worked too
2024-11-04 17:46:32 +0100 <haskellbridge> I think we can donate some money and setup a AWS WAF for it... shouldn't cost < $30 dollar
2024-11-04 17:46:32 +0100 <haskellbridge> <hellwolf> > It's apparently getting hit by a bunch of bot activity.
2024-11-04 17:44:44 +0100euphores(~SASL_euph@user/euphores) euphores
2024-11-04 17:43:54 +0100 <geekosaur> I haven't heard any complaints in the past week, so I guess it's back now?
2024-11-04 17:43:54 +0100 <dolio> It's apparently getting hit by a bunch of bot activity.
2024-11-04 17:43:26 +0100rvalue-rvalue