WeSearch

Ask HN: Why aren't LLM token CDN cache's a thing?

·1 min read · 0 reactions · 0 comments · 7 views
More from Ycombinator ai Compare coverage Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

Sorry if this is a stupid question but...Problem:I boot opencode into a codebase.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 5,048 of its stories.

Original article
Ycombinator
Read full at Ycombinator →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherYcombinator
Canonical URLhttps://news.ycombinator.com/item?id=49714867
Publication timeTue, 15 Sep 2026 16:20:29 +0000
Retrieval time2026-09-15T16:46:52.559Z
Last seen2026-09-15T16:46:52.559Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterBPcKWrHhoBgy · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Sorry if this is a stupid question but...Problem:I boot opencode into a codebase. I ask it to do one thing, it has to call 40 tools to "remember" what the codebase looks like relevant to that.It has no memory so every fresh boot is re-explore.My understanding, as an ML n00b, is the GPU have KV states of massive matrices that are multi GB in RAM (e.g., 10-30GB) so dumping to disk and pushing over network (his shoulders shuddered at the thought of egress fees), is not great.So instead we have cache during "work time", but off "work time", we have to reboot and build the cache again.But couldn't CF or someone setup CDNs to cache token state between days or something like that?Ages ago I was trying to solve part of this problem client side w/ vectoring a codebase and creating a tool to do…

Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Ycombinator