Remove my misunderstanding of push rule naming in synapse.

Signed-off-by: Nicolas Werner <nicolas.werner@hotmail.de>
pull/3664/head
Nicolas Werner 4 years ago
parent 53a46071f1
commit fa8fc978d3
No known key found for this signature in database
GPG Key ID: C8D75E610773F2D9

@ -140,8 +140,8 @@ writing this MSC to decrease dependencies.
`event_match` could be a good alternative. `event_match` could be a good alternative.
- Beeper has a - Beeper has a
[similar feature in their synapse](https://gitlab.com/beeper/synapse/-/commit/44a1728b6b021f97900c89e0c00f7d1a23ce0d43), [similar feature in their synapse](https://gitlab.com/beeper/synapse/-/commit/44a1728b6b021f97900c89e0c00f7d1a23ce0d43),
but it does not allow you to filter by relation type and also differs but it does not allow you to filter by relation type.
otherwise from the usual naming of push rule condition.
## Security considerations ## Security considerations

Loading…
Cancel
Save