65/100

Moderate evidence

Published recordScienceGeneral

Exploring Conversational Dynamics in Scientific and Pseudoscientific Health Communities on YouTube: Process Mining and Network Analysis Study

Truvace record
TRV-2026-1277raw data (JSON)
Version
v3Revised
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
577c7c72bef3…check it

Background Social media platforms, particularly YouTube (Google LLC), are important sources of health information, but also significant vectors for misinformation and pseudoscience. While many studies analyze the content and sentiment of this information, the dynamic, sequential nature of user interactions, which can shape belief formation and community dynamics, remains poorly understood. Objective This study aimed to explore the applicability of network analysis and process mining techniques for identifying an…

The gain

Applying network analysis and process mining to 52,412 YouTube comments distinguished scientific from pseudoscientific health discussions, showing mixed-valence evaluation in scientific threads versus affirmation bonding in pseudoscientific threads.

What this doesn’t fix

Exploratory observational design based on sampled corpora with preliminary findings, limiting generalizability beyond the retrieved YouTube comment threads.

Sources

1 on file
  1. Peer-reviewed2026-10-02

Cite this record

v3

Truvace Impact Record TRV-2026-1277, v3: “Exploring Conversational Dynamics in Scientific and Pseudoscientific Health Communities on YouTube: Process Mining and Network Analysis Study.” Truvace, 2026-11-04. /record/TRV-2026-1277 (accessed on the day you copy it). sha256 577c7c72bef34cda…

Change history

3 versions

Every change made to this record since it was first published, and why.

  1. Revisedv3577c7c72bef3…

    Editorial pass: sharper headline; filed as context: no real AI gain or problem (gain activity_only, problem absent).

  2. Revisedv20f245de2cb89…

    Direction audit: the problem line stated no AI consequence and was removed.

  3. Publishedv19dfa75d2a2cc…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-1277 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.