Commit Graph

133 Commits (a0316f67941d845252cf9c748356be0b445cd589)

Author SHA1 Message Date
Erik Johnston d01d1a07a6 Add changelog 8 years ago
Erik Johnston 212a4b5fce Add changelog entry 8 years ago
Richard van der Hoff 4f1c2f23ee Changelog fix
store-and-forward -> send-to-device
8 years ago
Richard van der Hoff ccd7bb32d5 Specification for direct-to-device messages 8 years ago
Benjamin Saunders cade909e25 Fix inconsistencies regarding redacted_because
Signed-off-by: Benjamin Saunders <ben.e.saunders@gmail.com>
8 years ago
Richard van der Hoff 7478e7f3cf Add top-level account_data to /sync response 8 years ago
Benjamin Saunders 77b668a5dc Fix some obsolete uses of user_id key in events
Signed-off-by: Benjamin Saunders <ben.e.saunders@gmail.com>
8 years ago
David Baker 311c0a6eb5 Hopefully correct indentation on changelog 8 years ago
David Baker 9fb68f54ce Changelog 8 years ago
Richard van der Hoff 6a4f65d78f update c-s changelog 8 years ago
Richard van der Hoff 07fa64d73d Update changelog 8 years ago
Richard van der Hoff 8328e485ea Clean up the pushrules API doc
* make it clearer which fields go in which parts of the rule
* the example given appeared to be for a content rule, so use a content rule
  consistently through the examples.
8 years ago
Richard van der Hoff 9a2af4fbc1 Changelog: Add /upload tweak 8 years ago
Richard van der Hoff ec20f15407 /tokenrefresh should expire the access token
It's possible for clients to call /tokenrefresh before the access_token has
expired, potentially leading to a proliferation of valid access_tokens.
8 years ago
Richard van der Hoff 2370a4c970 Spell out the state algorithm for createRoom
Fixes https://matrix.org/jira/browse/SPEC-429.

Synapse currently follows the specified ordering, but does *not* give the
specified error when the state is invalid (instead it creates the room anyway
but gives a 403 M_FORBIDDEN). Still, I don't think that should be a real
problem for any real clients, and nothing would break if we changed this in
synapse, so it might as well go in the spec anyway.
8 years ago
Richard van der Hoff 76ec390c73 changelog: Add "unreleased" placeholder 8 years ago
Richard van der Hoff 005a71ab00 Bump version in changelog 8 years ago
Richard van der Hoff 0ac04f5649 Merge branch 'master' into release/client-server/r0.2.0 8 years ago
Erik Johnston 06d379ed5e Add to changelog 8 years ago
Richard van der Hoff 4d2bee4b56 Prepare changelog for 0.2.0 release 8 years ago
Richard van der Hoff adb5768731 m.room.power_levels: clarify documentation
- clarify description and add text for invite, ban, etc.
- the keys aren't required. Document their defaults
- add 'invite' to example
9 years ago
Richard van der Hoff 7bbb664784 Improve documentation of directory API 9 years ago
Richard van der Hoff 590c55b760 Next release will be 0.1.0, not 1.0.0
Since synapse is already doing the new behavior on r0 endpoints, and nobody
wants to support the old behaviour, we're defining the new behaviour as r0.1.
9 years ago
Richard van der Hoff e7e9f5fa46 Document the /logout api
We have one, and it's useful, so we really ought to document it
9 years ago
Richard van der Hoff 8f304f3b3e C-S API will be released as r1.0.0, not r0.1.0 9 years ago
Richard van der Hoff 663fbf2323 Add link to device-specific push rules branch 9 years ago
Richard van der Hoff 5a50db2eac Update the changelog in preparation for releasing CS spec 0.1.0 9 years ago
Richard van der Hoff b59d16c4d1 Clarify `history_visibility` behaviour
Clear up some lies in the history_visibility section, and clarify behaviour for
`m.room.history_visibility` and the user's own `m.room.member` events.
9 years ago
Richard van der Hoff 91fa78eb53 Start development on next spec version 9 years ago
Richard van der Hoff e6af0441e1 Final r0.0.1 changelog entries 9 years ago
Richard van der Hoff e22135c099 Add a changelog for r0.0.1 9 years ago
Daniel Wagner-Hall ff45142663 Flesh out changelog
I forgot to push this before merging PR 215
9 years ago
Daniel Wagner-Hall 39f43abbb7 Add per-API changelogs 9 years ago