Handle abuse more transparently
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Currently we have the ability to a) automatically or b) manually block individual abusers whenever we notice abusive behavior. We're keeping track of a) using logs and b) using an internal Slack channel. Once an abuser is blocked, they are redirected to a page saying "you are blocked".
It would help tremendously to be able to communicate a "reason" to a user. For instance: "network scanning", "mining", "vulnerability scanning", etc. This way we have more influence on actual user behavior, and users are enabled to question our decisions.
Additionally, we could add an audit log to the admin pages which is reviewable, and also contains the timestamp and actor (blocking user). This way we can show proof to users more easily on request, without the need to skim multiple Slack channels for info.
Contributor guide
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 by tracing the existing automatic and manual blocking flow, the blocked-user redirect, and the admin pages mentioned in the issue. Define how a blocking reason, timestamp, and actor are recorded and displayed, then verify that blocked users receive the reason and administrators can review the audit history.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100