twitter / twitter/communitynotes

Bug in "temporarily locked out from writing new notes" feature.

Open
#142 1 comment 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

Describe the bug
Account stays permanently locked out from writing notes, even if requirements to unlock are met.

To Reproduce
Steps to reproduce the behavior:

  1. Get locked out from writing by getting 3 of the last 5 rated notes deemed "not helpful";
  2. After getting locked out, get all 3 notes previously rated as "not helpful" to "needs more ratings";
  3. After that, the locked out message dissapears for around one hour, returning later (even with 0 notes rated as "not helpful");
  • Even if you increase your Rating Impact by 5 (as required to unlock the account) the step 3 occurs again.

Expected behavior
The account ability to write notes should be unlocked after the requirements are met.

Screenshots
Screenshot_20230824-135657_Chrome
Screenshot_20230824-135710_Chrome

Environment
Mobile (Samsung S20 - Android 11; SM-G980F Build/RP1A.200720.012)
Web (Chrome 115.0.5790.168)

Additional context
I already increased my Rating Impact score by 14 since getting this bug, but after the message appears later it keeps asking for 5 more.

I'm having this problem for around 24 hours.
For contact in X/Twitter: @bananajoga

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 source file or test is named. Start by tracing the logic for writing-note lockouts, the last-five-note ratings, and Rating Impact; reproduce the reported sequence and verify that meeting the unlock requirements keeps the account unlocked instead of restoring the message later.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.