twitter / twitter/communitynotes
X Support is doxxing CN contributor X handles in follow-up emails when a note is reported
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 350
- Avg merge
- 6m
- Merged PRs (30d)
- 2
Description
I've reported 2 notes today, both follow-up emails from X Support came back with @usernames.
- https://x.com/i/birdwatch/t/20371860944883XXXXX
⋯ menu ⟶ Report ⟶ http://help.x.com/en/forms/community-note?note_id=20387088139229XXXXX ⟶ How can we help? (required) ⟶ Report a Community Note ⟶ https://help.x.com/en/forms/community-note/report-note?note_id=20387088139229XXXXX ⟶ Submit - Confirmation email sent/received "We have an update for you [CAAAAAAAAAo0XyAEAAABUf____w] Hello, We've received your report, and appreciate you letting us know what happened..."
- Follow-up email received "Update on your X report Hello, Thanks for reporting @[username]. Our support team has determined that a violation of our Rules did not take place..."
Expected behavior
- Same
- Same
- Follow-up email received "We have an update for you [CAAAAAAAAAo0XyAEAAABUf____w] Hello, We're writing to let you know that after reviewing the available information, we didn't find a violation of X Rules in the content you reported..."
Environment
Win11Pro/Chrome
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the community-note report flow at help.x.com/en/forms/community-note/report-note and trace how the follow-up email is generated after submission. Compare the email content described in the reproduction with the expected wording, including whether the reported contributor handle is inserted. Done means follow-up emails omit the @username while retaining the report update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100