twitter / twitter/communitynotes

Feature Suggestion: Optional Author-Context Layer for High-Visibility Posts in Community Notes

Open
#443 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

Suggestion

For highly viral posts and high-profile public figures on contentious topics, add an optional structured author-context layer:

• Relevant domain expertise vs. track record on this specific issue
• Consistent framing patterns, including ideological lean where the public post history shows a clear signal (with sourced examples)
• Multi-axis probabilistic signals + confidence bands
• Automatic weak-signal, low-data, sarcasm, or outdated-view flags

Scope
Limited strictly to high-visibility cases only. Fully transparent, bridging-rated, and with easy user feedback.

Why it helps
It would let readers better evaluate “who is saying this and what priors are they bringing?” — especially for voices who appear neutral. This could reduce deception and support de-escalation across all sides.

Examples (see attached thread for visuals):

  • Domain expertise mismatch
  • Ideological lean signals
  • Multi-axis scores
  • Weak-signal flags

Link to X post with full details:
https://x.com/TomGlassAI/status/2054051858369728831

Happy to provide more details or iterate.

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

No implementation files, tests, or entry points are named. Start by reviewing the repository structure and the linked proposal, then clarify the data sources, scoring design, visibility rules, transparency requirements, and feedback flow. Done should be a concrete, agreed scope with an implementation and validation plan.

Written by the indexing model from the issue text.

Assessment

Domain
ai
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.