twitter / twitter/communitynotes
Lost writing ability from note with Needs More Ratings status
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 350
- Avg merge
- 6m
- Merged PRs (30d)
- 2
Description
Describe the bug
I had my writing ability locked for the first time in July. I increased my rating impact by 5 points to get writing unlocked in December. I wrote two new notes, and both of those notes are still in the Needs More Ratings status. A community member rated one of the notes as Not Helpful, and my writing ability was locked again. I am now being asked to increase my rating by 15. This means a single vote, from a single member, on a note that still need more ratings, has caused me to get locked out again.
The documentation says notes currently in Needs More Ratings Status are not counted, but that doesn't seem to be true.
The documentation also says if a contributor’s writing ability is repeatedly locked, the additional Rating Impact needed to unlock it again increases by 5 each time. That also doesn't seem to be true since I am being asked to increase my rating by 15 on my second lockout.
I only have a lifetime total of 5 notes that have reached Helpful or Not Helpful status, so how is it possible I got locked out twice? That would mean you evaluated the same 5 notes twice, or you evaluated notes that still need more ratings.
To Reproduce
Steps to reproduce the behavior:
- Write 5 notes, have 3 reach Not Helpful status, and 2 reach Helpful status.
- Get locked out from writing for the first time.
- Increase impact rating by 5 and get writing unlocked.
- Write a new note, have one member rate it Not Helpful, but the note remains in Needs More Ratings status.
- You should get locked out again, and take note of how much you need to increase your impact rating to unlock again.
Expected behavior
I expect this to behave as the documentation says - notes currently in the Needs More Ratings status should not be counted. Also, rating impact should only increase by 5 each lockout as the documentation says.
Screenshots
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 documentation/contributing/writing-ability.md, especially the sections linked in the report, then reproduce the five-note sequence described in the issue. Trace the writing-lock calculation to determine whether notes in Needs More Ratings are counted and how the second-lockout increase is computed; done means the behavior matches the documented rules.
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
- 42/100