twitter / twitter/communitynotes

[Research] Understand Community Note Contributors' Fact-Check Process

Open
#412 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.9k
Forks
350
Avg merge
6m
Merged PRs (30d)
2

Description

Community Notes is widely used, but we still know little about the people who write the notes. Most research looks at public data, not contributors’ real experiences.

We don’t yet fully understand:

  • Why people choose to write notes

  • What makes the process hard or frustrating

  • How writers feel about the rating system

  • How they think about possible AI support

Understanding contributors’ perspectives is important for improving the system.
As part of our research project at Tsinghua University and Cornell University, we are conducting a interview study with Community Note writers.

We are inviting contributors to join a 40 minute interview about:

  • How you write notes

  • How you fact-check information

  • Your experience with the rating system

  • Your thoughts on using AI tools in the process

Participation is voluntary and confidential. Interviews are recorded only with permission, and all names are removed. Participants receive a $20 Amazon gift card.

If you’re interested, please contact:
Shuning Zhang – zsn23@mails.tsinghua.edu.cn
Jingruo Chen - jc3564@cornell.edu

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue contains a research recruitment announcement rather than a code task. No files, tests, or entry points are named, and no repository change or completion condition is specified.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.