archive
/
matrix-spec
mirror of https://github.com/matrix-org/matrix-spec
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
main
dbkr/msc4178
release/v1.12
release/v1.11
tulir/msc4142
release/v1.10
travis/msc2702-msc2701
rav/ref_objects_in_params
dkasak/foldable-sidebar
travis/knock-join
release/v1.9
release/v1.8
anoa/update_docsy
anoa/nix_flake
dbkr/3077-multi-stream-voip
release/v1.7
dbkr/2746-reliable-voip
rav/links_for_object_defs
release/v1.6
release/v1.5
release/v1.4
anoa/invite_knock_room_state
release/v1.3
push_gateway/r0.1.0
r0.0.0
0.2.0
application_service/r0.1.0
application_service/r0.1.1
application_service/r0.1.2
client-server/0.3.0
client-server/r0.1.0
client-server/r0.2.0
client-server/r0.3.0
client_server/r0.4.0
client_server/r0.5.0
client_server/r0.6.0
client_server/r0.6.1
identity_service/r0.1.0
identity_service/r0.2.0
identity_service/r0.2.1
identity_service/r0.3.0
push_gateway/r0.1.1
r0.0.1
server_server/r0.1.0
server_server/r0.1.1
server_server/r0.1.2
server_server/r0.1.3
server_server/r0.1.4
v1.1
v1.10
v1.11
v1.12
v1.2
v1.3
v1.4
v1.5
v1.6
v1.7
v1.8
v1.9
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '0f9eadd1a1'
${ noResults }
matrix-spec/proposals/3567-optional-from-on-messa...

2.6 KiB
Raw Blame History

MSC3567: Allow requesting events from the start/end of the room history

It can be useful to request the latest events in a room directly without calling /_matrix/client/v3/sync first to fetch the room state. Some use-cases include:

  • Requesting events using a different filter after receiving a /sync response.
  • A client which does not need to fully sync an account, but wishes to inspect a specific room's history (perhaps for exporting or auditing).

Proposal

The from field on the /_matrix/client/v3/rooms/{roomId}/messages becomes optional. If it is not provided, the homeserver shall return a list of messages from the first or last (per the value of the dir parameter) visible event in the room history for the requesting user.

Note that Synapse already implements this, but it is not spec-compliant. It is known to be used by Element Android 1 and Element Web, and there are other use-cases involving threads 2, which shows real-world usage that this would be valuable.

Ideally this would not be necessary and the prev_batch token received from calling /sync could be provided as the pagination token to /messages, but this will not work if you /sync with a filter that excludes a given class of event (such as threaded replies), and all the events taking place in a room are of that class. This will result in your /sync not returning an update for that room, which means that your most recent prev_batch token precedes all the excluded events. Trying to back-paginate from prev_batch using /messages will not result in seeing the excluded events.

Potential issues

None.

Alternatives

The alternative is today's status quo: a client must first make a request to /_matrix/client/v3/sync and then follow-up that request with queries to /_matrix/client/v3/rooms/{roomId}/messages. This is clunky if the client is going to throw away most of the information received from the /sync request.

The behavior also seems undefined if a different filter parameter is provided for the call to /sync compared to the one used for /messages.

Security considerations

None.

Unstable prefix

Since this is modifying the endpoint to support not including a field, no unstable prefix is necessary.

Dependencies

N/A

  1. https://github.com/matrix-org/synapse/issues/5538 ↩︎

  2. In order to list all threads in a room without pulling the history locally it uses /messages to push the filtering onto the homeserver. See https://github.com/matrix-org/matrix-js-sdk/pull/2065 ↩︎