From 519b95d0f991f6d78ff1858822f2ce38a1257c25 Mon Sep 17 00:00:00 2001 From: "DeepBlueV7.X" Date: Tue, 24 May 2022 18:33:03 +0000 Subject: [PATCH] Update proposals/3664-notifications-for-relations.md Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> --- proposals/3664-notifications-for-relations.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/proposals/3664-notifications-for-relations.md b/proposals/3664-notifications-for-relations.md index e96d3776c..916a712ed 100644 --- a/proposals/3664-notifications-for-relations.md +++ b/proposals/3664-notifications-for-relations.md @@ -45,7 +45,8 @@ messages. the related event should be matched using `pattern` and `key`. - `include_fallbacks` decides if the relation should be followed even for fallbacks (i.e. relations with the `is_falling_back` property set to `true` - like for threads). Defaults to false so only actual relations are counted. + like for [threads](https://github.com/matrix-org/matrix-spec-proposals/blob/main/proposals/3440-threading-via-relations.md#backwards-compatibility). + Defaults to `false` so only actual relations are counted. - `key` (optional): The dot-separated field of the event to match, e.g. `content.body` or `sender`. If it is not present, the condition should match all events, that have a relation of type `rel_type`.