element-hq / element-hq/synapse
Unspecced `redacted_by` field in `unsigned`
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 600
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 51
Description
This issue has been migrated from [#8764](https://github.com/matrix-org/synapse/issues/8764).
---
Ran into the following event today:
```js
{
"content": {
"membership": "join"
},
"origin_server_ts": 1595256121167,
"sender": "@redacted_user_1:example.com",
"state_key": "@redacted_user_1:example.com",
"type": "m.room.member",
"unsigned": {
"redacted_by": "$redacted_id_1",
"redacted_because": {
"content": {},
"origin_server_ts": 1595261803914,
"redacts": "$redacted_id_2",
"sender": "@redacted_user_2:example.com",
"type": "m.room.redaction",
"unsigned": {
"age": 23764322
},
"event_id": "$redacted_id_1"
}
},
"event_id": "$redacted_id_2"
}
```
This event contains a `redacted_by` property in the `unsigned` data, but the client-server spec makes no mention of such a field, it only mentions `redacted_because`.
Contributor guide
Assessment
This issue has not been assessed yet.