From caece4d6710c50ab35be552cd749f679b3af3a3e Mon Sep 17 00:00:00 2001 From: Andrew Ferrazzutti Date: Wed, 11 Sep 2024 13:40:42 -0400 Subject: [PATCH] Scope GET to only the requesting user's events --- proposals/4140-delayed-events-futures.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/proposals/4140-delayed-events-futures.md b/proposals/4140-delayed-events-futures.md index 40ac7daab..15888592c 100644 --- a/proposals/4140-delayed-events-futures.md +++ b/proposals/4140-delayed-events-futures.md @@ -185,8 +185,7 @@ Where the `action` is `send`, the homeserver SHOULD apply rate limiting to provi ### Getting delayed events A new authenticated client-server API endpoint `GET /_matrix/client/v1/delayed_events` allows clients to get a list of -all the delayed events that -have been scheduled to send. +all the delayed events owned by the requesting user that have been scheduled to send. The endpoint accepts a query parameter `from` which is a token that can be used to paginate the list of delayed events as per the [pagination convention](https://spec.matrix.org/v1.11/appendices/#pagination). The homeserver can choose a suitable