this post was submitted on 20 Mar 2025
383 points (99.7% liked)
Open Source
35627 readers
271 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You'd think these centralised LLM search providers would be caching a lot of this stuff, eg perplexity or claude.
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?
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.