element-hq / element-hq/synapse

Replace every mention of "blacklist"

Open
#15,277 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

T-Task
Dominant language
Python
Stars
4.6k
Forks
607
Avg merge
5d 22h
Merged PRs (30d)
51

Description

This issue has been migrated from [#15277](https://github.com/matrix-org/synapse/issues/15277).

---

### Description

The terms "black list" and "white list" are racist.

This Internet Standard draft explains it quite well:

https://www.ietf.org/archive/id/draft-knodel-terminology-13.txt

```
2.2. Blacklist-Whitelist

The metaphorical use of white-black to connote good-evil is
exclusive. While master-slave might seem like a more egregious
example of racism, white-black is arguably worse because it is more
pervasive and therefore more insidious. While recent headlines have
decried the technical community's use of master-slave, there is far
less discussion about white-black despite its importance. There is
even a name for this pervasive language pitfall: the association of
white with good and black with evil is known as the "bad is black
effect" [Grewal].
```

I propose adding block lists and allow lists and later deprecate and remove the offending terms.

### Steps to reproduce

Ask some black people for their opinion

### Homeserver

example.org

### Synapse Version

none

### Installation Method

Other (please mention below)

### Database

none

### Workers

I don't know

### Platform

-

### Configuration

_No response_

### Relevant log output

```shell
none
```

### Anything else that would be useful to know?

_No response_

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

No files, tests, or entry points are identified. Start by searching the repository for every occurrence of “blacklist” and “white list”, then map the affected code, configuration, and documentation before deciding the replacement scope. Done means all relevant mentions use the proposed terminology without breaking references or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.