twitter / twitter/communitynotes

A way to make a counterpoint to a "Note not needed" note without that becoming visible

Open
#147 2 comments 4 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 Member A makes an original note A on a post

Community Member B makes a "note not needed" note B on the same post, making his case why the note A should be voted down.

Community Member C or original member A wants to make a counterpoint to B ( let this counterpoint be called C ), stating why the note is needed or why the counterpoint B is false/irrelevant.

Currently there's no proper place to post Note C. If you post it in the Notes section, people might vote to make it visible. But what you're actually arguing for is to keep A visible. So all votes on my note C should be going to note A that I quoted.

Feature:

This could be solved with a reply option for Notes, atleast NNN notes, that shows those replies under the NNN note.

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

Start by reviewing the existing Notes section and the NNN note flow described in this issue, then trace how note visibility and voting are currently handled. Done means a reply to an NNN note can be posted without becoming independently visible, while the original note remains the subject of visibility votes.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.