docs-matrix-spec/api/client-server
Mark Haines bde003fe86 Split the rooms out into a separate top level key.
Divide the rooms into separate groups in preparation for adding tag
support.

Further subdivide the rooms into "joined/invited/archived" based the
membership of the user in the room because that membership affects what
events the user can view from the room. E.g only users that are joined
to a room may see the ephemeral events for the room.
2015-10-02 16:14:24 +01:00
..
v1 Make the example room id more "random" so that people are less likely to think that it is supposed to be human readable 2015-09-21 17:31:35 +01:00
v2_alpha Split the rooms out into a separate top level key. 2015-10-02 16:14:24 +01:00
api-docs Shuffle around structure of matrix-doc and add a README. 2015-02-20 10:43:20 +00:00
api-docs-content Shuffle around structure of matrix-doc and add a README. 2015-02-20 10:43:20 +00:00
api-docs-directory Shuffle around structure of matrix-doc and add a README. 2015-02-20 10:43:20 +00:00
api-docs-events Shuffle around structure of matrix-doc and add a README. 2015-02-20 10:43:20 +00:00
api-docs-login Shuffle around structure of matrix-doc and add a README. 2015-02-20 10:43:20 +00:00
api-docs-presence Shuffle around structure of matrix-doc and add a README. 2015-02-20 10:43:20 +00:00
api-docs-profile Shuffle around structure of matrix-doc and add a README. 2015-02-20 10:43:20 +00:00
api-docs-registration Shuffle around structure of matrix-doc and add a README. 2015-02-20 10:43:20 +00:00
api-docs-rooms Test swagger commit 2015-02-20 14:29:51 +00:00