ATRIUMsearch → argument graph
MechanismArticle

Semantic retrieval using embeddings solves the proxy problem: dual-encoder models embed users and posts into a shared space so that related meanings—not surface keywords—position items nearby, and retrieval becomes a fast nearest-neighbor search over a precomputed index.

The alternative to behavioral retrieval is semantic retrieval powered by embeddings, which place related items near one another in a high-dimensional space even without shared keywords. A dual-encoder design converts users and posts into points in the same space, letting platforms precompute post embeddings and run fast nearest-neighbor searches at request time. ✦ AI generated

Author (article How to Fight Clickbait: Meta, LinkedIn & YouTube Case Studies) · ByteByteGo Newsletter · 2026-08-10 · original ↗

An embedding is a list of numbers that positions an item as a point in a high-dimensional space, arranged so that related items land near one another. For example, a post about fixing a leaking tap and a post about reducing water waste sit close together even when they share no keywords, because their meanings are related... One encoder converts a user, along with their profile and recent activity, into a point in the space. A second encoder converts each post into a point in the same space. Since the two encoders operate independently, a platform can compute every post embedding in advance and store it in an index. At request time, it computes the user embedding and runs a nearest-neighbor search to find the closest posts, which keeps retrieval fast across an enormous corpus.

Read full article ↗excerpt · fair-use quotation

Around this claim
This moment responds to
gives exampleLinkedIn consolidated five separate retrieval systems into a single fine-tuned LLaMA-3 language-model dual encoder that serves the entire feed through nearest-neighbor search at sub-50-millisecond latency, and its key insight is that feature representation—not the model—is where the real effort lies.Author (article How to Fight Clickbait: Meta, LinkedIn & YouTube Case Studies) · ByteByteGo Newslettergives exampleMeta went in the opposite direction to LinkedIn: it keeps an ecosystem of more than a thousand specialized models arranged as a multi-stage retrieval funnel, ending in a multi-objective value model that extends the objective past raw engagement to avoid-content signals.Author (article How to Fight Clickbait: Meta, LinkedIn & YouTube Case Studies) · ByteByteGo Newslettergives exampleYouTube removed the search index entirely with PLUM, which assigns videos semantic IDs and treats retrieval as a generation task: an adapted Gemini-family language model produces the codes of the next videos a user is likely to watch, gaining much wider long-tail coverage while risking generated identifiers that map to no video.Author (article How to Fight Clickbait: Meta, LinkedIn & YouTube Case Studies) · ByteByteGo Newsletterexplains mechanismThe real reason the three companies converged on semantic retrieval but diverged in implementation is data structure: a text-rich professional network, a multi-objective media platform, and a video service with an enormous item corpus each favor a different retrieval design.Author (article How to Fight Clickbait: Meta, LinkedIn & YouTube Case Studies) · ByteByteGo Newslettergives exampleUber Eats fine-tuned a Qwen LLM into the embedding backbone of two-tower retrieval, so every query and every document gets an LLM-derived vector.The article author · ByteByteGo Newsletter