aceModerate evidence
Published recordMedia & ArtsProblem Space
More
Artificial Intelligence in Broadcasting: Public Trust and Misinformation Detection in Robotic News Presentation
- Truvace record
- TRV-2026-2699raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- f172c1b0b2e1…check it
Social robots are increasingly proposed for high-stakes societal roles such as journalism. This raises questions about public trust, especially for non-humanoid designs, and how source credibility relates to an audience’s evaluation of information. In a field experiment, 40 participants in Brazil interacted with an emotionally expressive, non-humanoid social robot that presented three news stories, one of which was fabricated. Pre- and post-interaction questionnaires assessed perceived trust, role acceptance, an…
The problem
In a field experiment with 40 people in Brazil, only 7 (17.5%) correctly picked out the fabricated story among three told by a social robot, below the 33.3% chance rate, even though they rated the robot as credible.
What this doesn’t fix
The study used a convenience sample of 40 mostly young attendees of a technology event, a single 10-15 minute session and no human-presenter comparison group. The authors also note that formal ethics committee approval was not obtained.
Sources
1 on file- Journal of Intelligent & Robotic Systemsdoi:10.1007/s10846-026-02409-6
Cite this record
v1Truvace Impact Record TRV-2026-2699, v1: “Artificial Intelligence in Broadcasting: Public Trust and Misinformation Detection in Robotic News Presentation.” Truvace, 2026-11-12. /record/TRV-2026-2699 (accessed on the day you copy it). sha256 f172c1b0b2e13126…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2699 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.