Skip to content

Allow blacklisting GitHub users, organizations, or DNS namespaces #98

Description

@tadasant

This is a fallback in case we do we have spammers or other bad actors succeed in publishing malicious/spam content.

This should be possible in some code in this repo where we have git logs to audit history of changes.

Adding someone to this list should optionally delete everything they've published historically.

Activity

  1. added
    go-live blockerThis issue is one we need to address prior to initial go-live
    on May 27, 2025
  2. self-assigned this
    on Aug 26, 2025
  3. domdomegg commented on Aug 27, 2025

    @domdomegg
    Member

    Another idea: we could require GitHub users have had their account for a while, e.g. 30 days. This would add more friction to malicious users creating new accounts when they are banned. I won't do this for go-live but we can explore it if it becomes a problem.

    (Although it might add a little more friction to genuine users with fresh GitHub accounts, I know a couple people who created GitHub accounts to build and share MCP servers so it would be sad to block them - so think we can see how we go and then do this if the spam becomes apparent)

  4. added a commit that references this issue on Aug 27, 2025
    ad07a27
  5. added a commit that references this issue on Aug 27, 2025
    9d04671
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

go-live blockerThis issue is one we need to address prior to initial go-liveimplementation workShovel-ready to write code

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions