From 883e6b5d55b3ea0ecfc8eb0f86cfa336de07ed83 Mon Sep 17 00:00:00 2001 From: Andrew Ferrazzutti Date: Wed, 11 Sep 2024 11:13:34 -0400 Subject: [PATCH] Revert "Expose transaction ID in GET response" This reverts commit 772590f6bac61bd026e8a60dc055b76637cce8f7. Clients should keep track of transaction IDs themselves. --- proposals/4140-delayed-events-futures.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/proposals/4140-delayed-events-futures.md b/proposals/4140-delayed-events-futures.md index 2a1beac69..40ac7daab 100644 --- a/proposals/4140-delayed-events-futures.md +++ b/proposals/4140-delayed-events-futures.md @@ -199,7 +199,6 @@ The response is a JSON object containing the following fields: - `room_id` - Required. The room ID of the delayed event. - `type` - Required. The event type of the delayed event. - `state_key` - Optional. The state key of the delayed event if it is a state event. - - `transaction_id` - Optional. The transaction ID of the delayed event if it is a regular (non-state) event. - `delay` - Required. The delay in milliseconds before the event is sent. - `running_since` - Required. The timestamp (as unix time in milliseconds) when the delayed event was scheduled or last restarted. @@ -221,7 +220,6 @@ Content-Type: application/json "type": "m.room.message", "delay": 15000, "running_since": 1721732853284, - "transaction_id": "abcdefgh", "content":{ "msgtype": "m.text", "body": "I am now offline"