Comment by mewse-hn
16 hours ago
Funny to see this after I spent the morning troubleshooting and fixing my crowdsec install on my debian 13 vps. Apparently they stopped supplying a community blocklist to my machine because I'm running the old debian packaged version instead of directly from them (http 500). I had a LLM build a blocklist from publicly available sources rather than tie myself more tightly to their SaaS platform.
Wait … that’s lame. If it’s in Debian repos I expect it to work with full functionality (up to the version number)
I can understand the myriad reasons for why a company would be inconvenienced by that.
But on the other hand, it seems like a reason for me to never use the vendor
I feel like a massive blocklist is simultaneously exactly the kind of thing an LLM is likely to hallucinate and exactly the kind of thing you don't want to rely on an LLM for.
If they had it build it from public sources then I assume it was combined via tool usage rather than direct generation. Beyond the hallucination risk, the latter would just be a waste of tokens & time.
Modern agent harnesses rely heavily on tools, as well as writing code, to avoid hallucinations affecting deterministic values.
Which means it'd be a lot cheaper, to use tools, and public sources, and just automate it the traditional way...
3 replies →
Ah, I have to check that, thanks!
Ah, I just learned this, thanks for the heads up.