mitchellh / mitchellh/vouch

Updating username could lead to getting around being `denounced`

Open
#20 12 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

design needed enhancement
Dominant language
Nushell
Stars
5.1k
Forks
91
PR merge metrics
No merged PRs in 30d

Description

A good point was brought up when we were thinking through implementing the vouch system for the OpenCode repo (we see a lot of AI slop, especially in issues) and someone in https://github.com/anomalyco/opencode/pull/12640#issuecomment-3865765666 brought up the thought of if someone changes their username they would be able to get around being denounced.

A bad user (that wants to spam) might change their username to get around being "banned/denounced" from a repo.

I think a way to solve this would be to have in the .td file would be to include the userid of the user as well so that:

-github:slopmaster3000 Submitted endless amounts of AI slop

would become

-github:slopmaster3000:128301923810298 Submitted endless amounts of AI slop

The only caveat to this is since this isn't Github specific (and I don't have experience with other providers like Gitlab) I can't confirm if this is a reliable way to attain user-ids.

Contributor guide

Open the contributing guide

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 tracing how .td entries are parsed and how provider user identities are resolved for denouncements. Check the supported provider integrations before choosing an identity field; done means a username change cannot bypass an existing denouncement without breaking providers that lack stable user IDs.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
authorization
Issue type
Feature
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.