Content that changes over time makes previously seen items hard to find again

What it is

Yesterday a documentary sat third in For You; today that seat is something else, and scrolling down does not bring it back. It was not taken down. Ranking removed it from this person’s visible set. Unstable personalized content means the item set one user faces is rewritten over time, so finding yesterday’s sighting loses a reliable path — not a wrong memory of location, but the object having left the scrollable world.

Location memory is coordinates collapsing. Here it is addressability of the object in time.

Why it happens

Personalization optimises expected clicks now, not “keep yesterday’s appearances findable.” Once an object drops out of the current best set, it is gone from home, from continue-watching, and not necessarily in search’s default ranking. Re-finding tactics people use — scroll again, scan by cover — assume the object is still in the same pool. After the pool is sliced by time, those tactics go to zero.

An infinite stream adds a layer: there is no “page N” to report, so backtracking has no address. If history only stores completions, a half-watched row that was flicked past leaves nothing. “Just saw” is then not a first-class state in the product; only “finished” is.

Studying it

Have people mark several items in a personalised stream as “might want this back” (completion not required). Search again after hours, a day, a week. Measure: success, path (home / search / history / give up), attribution. Independent variables: whether watch history includes unfinished, whether search is personalised, whether the item is still in the catalogue. Dependent variables: re-find success, time, rate of judging failure as “taken down.”

Still in the catalogue and unfindable is this question. True takedowns should be reported separately.

Where it stops holding

Live events and timed inventory were never re-findable; mark that at the time. Items the user explicitly saved are out of scope — save is another addressing channel. A pure chronological timeline at least leaves “about which day.” This entry is personalization erasing the object from a person’s time. It does not treat people being unable to direct each other, and it does not require a non-personalised search — that is the fallback layer.

Applying it

• Make “appeared on your home” a searchable state, at least in history, finished or not.
• Do not send re-finding back through For You. Give history or “recently seen.”
• Check: have someone name an item they saw on home yesterday and did not finish, and look for it through the product’s own entries. If it cannot be found and is still in the catalogue, temporal addressability is broken. Open “recently seen” and test again.

Related

• Same group: L6.12.1 Personalization makes the same entry show different content, so location memory fails · L6.12.3 Users cannot give each other directions; shared screenshots no longer match anyone else’s interface · L6.12.4 Stable structure with variable content is easier to master than a structure that also moves · L6.12.5 Search and history that are not personalized must exist as a fallback
• Nearby: L6.09 Feedback Loops and Preference Entrenchment · L6.05 Turning Personalization Off · L2.07 Prompt History and Reuse
• Search terms: unstable personalized content · feed ephemerality · re-finding