@[email protected] to Open [email protected] • 4 months agoFOSS infrastructure is under attack by AI companiesthelibre.newsexternal-linkmessage-square30fedilinkarrow-up1383cross-posted to: [email protected][email protected][email protected][email protected][email protected][email protected]
arrow-up1383external-linkFOSS infrastructure is under attack by AI companiesthelibre.news@[email protected] to Open [email protected] • 4 months agomessage-square30fedilinkcross-posted to: [email protected][email protected][email protected][email protected][email protected][email protected]
minus-square@[email protected]linkfedilink13•4 months agoYou’d think these centralised LLM search providers would be caching a lot of this stuff, eg perplexity or claude.
minus-square@[email protected]linkfedilinkEnglish38•4 months agoThere’s two prongs to this Caching is an optimization strategy used by legitimate software engineers. AI dorks are anything but. Crippling information sources outside of service means information is more easily “found” inside the service. So if it was ever a bug, it’s now a feature.
minus-square@[email protected]linkfedilink15•4 months agoThird prong, looking constantly for new information. Yeah, most of these sites may be basically static, but it’s probably cheaper and easier to just constantly recrawl things.
minus-square@[email protected]linkfedilinkEnglish8•4 months agoThey’re absolutely not crawling it every time they nee to access the data. That’s an incredible waste of processing power on their end as well. In the case of code though that does change somewhat often. They’d still need to check if the code has been updated at the bare minimum.
minus-square@[email protected]linkfedilink1•4 months agoHashes for cached content. Anyone know what sort of DB makes sense here?
You’d think these centralised LLM search providers would be caching a lot of this stuff, eg perplexity or claude.
There’s two prongs to this
Caching is an optimization strategy used by legitimate software engineers. AI dorks are anything but.
Crippling information sources outside of service means information is more easily “found” inside the service.
So if it was ever a bug, it’s now a feature.
Third prong, looking constantly for new information. Yeah, most of these sites may be basically static, but it’s probably cheaper and easier to just constantly recrawl things.
They’re absolutely not crawling it every time they nee to access the data. That’s an incredible waste of processing power on their end as well.
In the case of code though that does change somewhat often. They’d still need to check if the code has been updated at the bare minimum.
Hashes for cached content. Anyone know what sort of DB makes sense here?