Eric Eastwood 3fee32ed6b Order heroes by stream_ordering (as spec'ed) (#17435) ... The spec specifically mentions `stream_ordering` but that's a Synapse specific concept. In any case, the essence of the spec is basically the first 5 members of the room which `stream_ordering` accomplishes. Split off from https://github.com/element-hq/synapse/pull/17419#discussion_r1671342794 ## Spec compliance > This should be the first 5 members of the room, **ordered by stream ordering**, which are joined or invited. The list must never include the client’s own user ID. When no joined or invited members are available, this should consist of the banned and left users. > > *-- https://spec.matrix.org/v1.10/client-server-api/#_matrixclientv3sync_roomsummary* Related to https://github.com/matrix-org/matrix-spec/issues/1334		2024-07-17 13:10:15 -05:00
..
admin	Finish up work to allow per-user feature flags (#17392)	2024-07-05 13:02:35 +01:00
client	Order heroes by stream_ordering (as spec'ed) (#17435)	2024-07-17 13:10:15 -05:00
key	Correctly mention previous copyright (#16820)	2024-01-23 11:26:48 +00:00
media	Fix slipped logging context when media rejected (#17239)	2024-05-29 11:14:42 +01:00
synapse	An federation whitelist query endpoint extension (#16848)	2024-05-13 19:38:45 +00:00
__init__.py	Correctly mention previous copyright (#16820)	2024-01-23 11:26:48 +00:00
test_health.py	Correctly mention previous copyright (#16820)	2024-01-23 11:26:48 +00:00
test_well_known.py	Merge remote-tracking branch 'gitlab/clokep/license-license' into new_develop	2023-12-13 15:11:56 +00:00