Skip to content

Commit aeadae8

Browse files
committed
Remove arbitrary limits
1 parent 853bed2 commit aeadae8

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

proposals/2762-widget-event-receiving.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -255,10 +255,9 @@ the widget requested 25, it will only ever get 5 maximum back. When `limit` is n
255255
assumed that the widget wants as many events as the client will give it. When negative, the client
256256
can reject the request with an error.
257257

258-
The recommended maximum `limit`s are:
259-
260-
* For `m.room.member` state events, no limit per room.
261-
* For all other events, 25 per room.
258+
There is no recommended maximum `limit`, though clients will want to consider local limitations in
259+
being able to send events. Web clients, for example, may be more able to send *every* event it knows
260+
about. The default assumption is that the client will send over as much as possible as an upper limit.
262261

263262
The client is not required to backfill (use the `/messages` endpoint) to get more events for the
264263
widget, and is able to return less than the requested amount of events. When returning state events,

0 commit comments

Comments
 (0)