2025/03/23

Newest at the top

2025-03-23 03:20:16 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-03-23 03:20:00 +0100dtman34(~dtman34@c-75-72-179-251.hsd1.mn.comcast.net) (Ping timeout: 252 seconds)
2025-03-23 03:19:28 +0100hiecaq(~hiecaq@user/hiecaq) hiecaq
2025-03-23 03:18:30 +0100hiecaq(~hiecaq@user/hiecaq) (Quit: ERC 5.6.0.30.1 (IRC client for GNU Emacs 30.0.92))
2025-03-23 03:18:18 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-03-23 03:15:30 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-03-23 03:15:16 +0100_________(~nobody@user/noodly) _________
2025-03-23 03:13:00 +0100 <talismanick> although I guess they can fall back on plausible deniability
2025-03-23 03:11:44 +0100 <talismanick> but then we have a whole catalog of bad actors with real professional reputations to blacklist lol
2025-03-23 03:10:59 +0100dtman34(~dtman34@c-75-72-179-251.hsd1.mn.comcast.net) dtman34
2025-03-23 03:10:54 +0100 <talismanick> junior devs looking to pad their resumes by "contributing" bug reports?
2025-03-23 03:10:31 +0100 <regalk> That is really concerning...
2025-03-23 03:10:12 +0100 <talismanick> not sure what the financial payoff is in sending fake bug report, though
2025-03-23 03:08:23 +0100 <talismanick> they'll do what all Chinese companies do when you sue them for fraud and malpractice: dissolve and leave you holding the bag, the same scammers creating a new company under a different filing because they know they'll never face consequences
2025-03-23 03:07:11 +0100 <EvanR> surely when you sue them, their AI-in-place-of-real-lawyers will be the weak point
2025-03-23 03:07:00 +0100 <talismanick> not in China there isn't, apparently
2025-03-23 03:06:33 +0100 <EvanR> isn't there a law against this
2025-03-23 03:06:25 +0100 <EvanR> ok so their DDOSing the entire internet
2025-03-23 03:05:46 +0100 <talismanick> never mind that they go to lengths to coordinate across IP address ranges to circumvent blocks when they could behave themselves and not be blocked to begin with
2025-03-23 03:05:36 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 252 seconds)
2025-03-23 03:04:59 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds)
2025-03-23 03:04:42 +0100 <talismanick> so it's not even tragedy of the commons (in the classic 0-sum formulation of inescapable depletion), it's just laziness offloaded as externality because a free API mean they can't be bothered to spend any of their time
2025-03-23 03:03:21 +0100 <talismanick> even though conventional crawlers (Google, Bing) take up a fraction of a percent of bandwidth, these spam scrapers can comprise 90%+ of total bandwidth usage
2025-03-23 03:02:19 +0100 <talismanick> tl;dr: FOSS devs spend thousands on bandwidth while real users get server timeouts, minute-long delay modals, etc as profit-hungry companies vacuum the same text over and over again for free as they all rush to crawl the web and silo its knowledge in the weights of their own LLMs
2025-03-23 03:00:19 +0100hattckory(~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca)
2025-03-23 02:59:44 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-03-23 02:58:53 +0100 <talismanick> EvanR: https://thelibre.news/foss-infrastructure-is-under-attack-by-ai-companies/
2025-03-23 02:58:47 +0100mhatta(~mhatta@www21123ui.sakura.ne.jp)
2025-03-23 02:58:25 +0100_________(~nobody@user/noodly) (Ping timeout: 244 seconds)
2025-03-23 02:57:22 +0100mhatta(~mhatta@www21123ui.sakura.ne.jp) (Remote host closed the connection)
2025-03-23 02:55:39 +0100dtman34(~dtman34@c-75-72-179-251.hsd1.mn.comcast.net) (Ping timeout: 260 seconds)
2025-03-23 02:55:35 +0100Owner_(~Owner@2600:1700:69cf:9000:c07e:d68e:b135:82a6) (Read error: Connection reset by peer)
2025-03-23 02:49:14 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds)
2025-03-23 02:47:48 +0100hattckory(~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) (Ping timeout: 276 seconds)
2025-03-23 02:47:36 +0100 <enikar> finally we found a use to LLM :/
2025-03-23 02:47:35 +0100regalk(~regalk@gateway/tor-sasl/regalk) regalk
2025-03-23 02:44:12 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-03-23 02:37:44 +0100 <EvanR> in the old days you had to send your own spam
2025-03-23 02:37:39 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 252 seconds)
2025-03-23 02:37:25 +0100 <EvanR> what...
2025-03-23 02:35:14 +0100sim590(~simon@209-15-185-101.resi.cgocable.ca) (Ping timeout: 260 seconds)
2025-03-23 02:34:43 +0100hattckory(~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca)
2025-03-23 02:33:56 +0100 <geekosaur> it's being rate-limited because of those, yes
2025-03-23 02:33:16 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-03-23 02:33:15 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-03-23 02:31:29 +0100roqueando(~roqueando@179-125-159-89.dynamic.desktop.com.br) (Client Quit)
2025-03-23 02:28:46 +0100roqueando(~roqueando@179-125-159-89.dynamic.desktop.com.br)
2025-03-23 02:28:26 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-03-23 02:28:07 +0100dtman34(~dtman34@c-75-72-179-251.hsd1.mn.comcast.net) dtman34
2025-03-23 02:21:14 +0100sprotte24(~sprotte24@p200300d16f4e7b00ad35a318f64ef662.dip0.t-ipconnect.de) (Quit: Leaving)