TRV-2026-1773Certified recordPeer-reviewed

The impact of artificial intelligence on journalism: How media trust and attitudes toward journalists shape acceptance, trust, willingness to pay for AI news, and support for replacing journalists

Although AI is advancing rapidly in many fields, its use in journalism is especially significant, as journalism shapes public opinion and fosters democratic discourse. Artificial intelligence (AI), in particular, has attracted attention for its potential to greatly enhance journalists’ work, but also raises concerns about ethics and job displacement. However, previous research has largely overlooked the public’s perspective on AI, even though understanding these views is crucial for predicting future consumption…

Media & Arts · Problem Space — documented harm · certified 2026-10-18 · v1 · article view · machine-readable

Current reading — problem

Public acceptance of AI in journalism, trust in its output, willingness to pay, and support for replacing human journalists are all moderate to low in two large national surveys, limiting audience demand for AI news.

What this doesn’t fix

The data come from cross-sectional surveys in only two countries, so the findings describe attitudes at a single point in time rather than changes or causal effects.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1773, v1: “The impact of artificial intelligence on journalism: How media trust and attitudes toward journalists shape acceptance, trust, willingness to pay for AI news, and support for replacing journalists.” Truvace, 2026-10-18. /record/TRV-2026-1773 (accessed at citation time). sha256 cc2128816005c596…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1cc2128816005…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1773 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.