48912a7320
Fix auth rules of redactions in v3
6 years ago
ad64af3f01
Clarify how reference hashes are done
6 years ago
01556e5b17
Clarifications and bug fixes in how v3 rooms work
6 years ago
3c17a0e53b
Mention caching
6 years ago
b971bcee7d
Accurately represent the 3 proposals and provide more detail
6 years ago
fb36757869
Merge pull request #1833 from matrix-org/travis/misc/domain-security
...
Document domain reuse concerns
6 years ago
48e4d6e412
Document domain reuse concerns
...
Fixes https://github.com/matrix-org/matrix-doc/issues/1783
6 years ago
0f3aa3fa8a
Merge pull request #1829 from matrix-org/travis/spec/c2s-caps
...
Specify how capabilities work in the c2s API
6 years ago
d2f012f4ea
Incorporate MSC1831
...
Original proposal: https://github.com/matrix-org/matrix-doc/pull/1831
Implementation proof: pending
6 years ago
00de03bddb
Merge remote-tracking branch 'origin/travis/msc/wk-before-srv' into travis/msc/wk-before-srv
6 years ago
2fe6b2cb5c
Plagiarize from richvdh for a better explanation
6 years ago
ab7876cbef
Update 1831-srv-after-wellknown.md
6 years ago
0e90cf6a0c
Proposal to change the order of .well-known and SRV discovery techniques
6 years ago
c888f3f080
Make example strings more legible
6 years ago
0347e873ef
Specify .well-known s2s discovery and X.509 validation
...
Original proposals:
* https://github.com/matrix-org/matrix-doc/pull/1708 (note: the JSON requirements were softened by https://github.com/matrix-org/matrix-doc/pull/1824 )
* https://github.com/matrix-org/matrix-doc/pull/1711
Implementation proofs:
* https://github.com/matrix-org/synapse/pull/4489
* No explicit PRs for MSC1711 could be found, however Synapse is known to implement it.
There are no intentional changes which differ from the proposals in this commit, however the author has relied upon various historical conversations outside of the proposals to gain the required context. Inaccuracies introduced by the author are purely accidental.
6 years ago
9193d57dfd
full stop
6 years ago
ccce6c196d
Specify how capabilities work in the c2s API
...
Original proposals:
* https://github.com/matrix-org/matrix-doc/pull/1753
* https://github.com/matrix-org/matrix-doc/pull/1804
Implementation proof:
* https://github.com/matrix-org/synapse/pull/4472
* https://github.com/matrix-org/matrix-js-sdk/pull/830
There is one change to MSC1753 which is included in this commit. MSC1804 remains unchanged. In the original proposal, the change password capability being present was an indication that password changes were possible. It was found that this doesn't really communicate the state very well to clients in that lack of a capability (or a 404, etc) would mean that users would erroneously not be able to change their passwords. A simple boolean flag was added to assist clients in detecting this capability.
6 years ago
72a2871021
Merge pull request #1804 from matrix-org/travis/msc/room-version-client-advertising
...
MSC1804: Advertising capable room versions to clients
6 years ago
ff75996524
Add specification for room version 3: Event IDs as hashes
...
Original proposal: https://github.com/matrix-org/matrix-doc/pull/1659
Implementation proofs (some traversing of the PR tree may be required to get all of them):
* https://github.com/matrix-org/synapse/pull/4483
* https://github.com/matrix-org/synapse/pull/4499
This doesn't intentionally change anything from the proposal.
**Implementation details**:
The simple part of this is the introduction of a rooms/v3.html document. The somewhat unclear part is the stuff done to the s2s definitions. This pulls `unsigned_pdu` out to `unsigned_pdu_base` (all fields except `event_id`) where it can be reused in `pdu` and `pdu_v3` (for rooms v3). These definitions are further moved into the room version specifications where they can highlight the exact schemas in detail.
Version 1 has been updated to include the pre-existing event format, however the core principles of the room have not been changed. The same applies to room version 2. Room versions have immutable core principles once in the spec, otherwise these format changes would land in a pre-existing version.
The client-server API event formats will need updating, however that is being punted to a different commit to try and keep these changes reviewable.
6 years ago
4437c383bb
Merge pull request #1790 from matrix-org/travis/spec/login-redirect
...
Add a mechanism for redirecting clients after login
6 years ago
1c0742ed6a
MSC 1659 Proposal: Change Event IDs to Hashes ( #1659 )
6 years ago
afd399d7d4
remove unused schema defs
6 years ago
2eae933ed6
hard wrap to 80 chars
6 years ago
4f13f5289e
Update 1819-remove-presence-lists.md
...
Add references to exactly what this proposal would remove
6 years ago
5151aa0aa7
Update proposals/1819-remove-presence-lists.md
...
Co-Authored-By: neilisfragile <neil@matrix.org>
6 years ago
c09fa6845e
Update presence.rst
6 years ago
d2b35e5150
Merge pull request #1821 from matrix-org/travis/spec/rver-make-memberships
...
Specify the room_version response property on /make_{leave|join}
6 years ago
2c3ba0b135
Merge pull request #1813 from matrix-org/erikj/make_membership_room_ver
...
MSC 1813 - Federation Make Membership Room Version
6 years ago
00adfdbf4a
Merge pull request #1820 from matrix-org/travis/spec/fed-v2-invite
...
Specification for v2 s2s invite API
6 years ago
c0039c30f2
Minor wording changes from code review
...
Co-Authored-By: turt2live <travpc@gmail.com>
6 years ago
3374d22b52
Merge pull request #1823 from matrix-org/anoa/majority_update
...
75% majority now required for FCP
6 years ago
de57d3950f
Relax the requirement for a content-type on .well-known ( #1824 )
...
The main reason for this is that Apache etc won't stick a content-type on by
default, because they don't know it's JSON, so requiring it seems like it will
require unnecessary hoop-humping for everyone who wants to use a .well-known.
6 years ago
0712fd36a2
75% majority now required for FCP
6 years ago
d12593feea
Specify the room_version response property on /make_{leave|join}
...
Original proposal: https://github.com/matrix-org/matrix-doc/pull/1813
Implementation proof: https://github.com/matrix-org/synapse/pull/4447
There are no changes from the original proposal.
6 years ago
aca9437bf3
Specification for v2 s2s invite API
...
Original proposal: https://github.com/matrix-org/matrix-doc/pull/1794
Implementation proofs:
* https://github.com/matrix-org/synapse/pull/4402
* https://github.com/matrix-org/synapse/pull/4496
There are no changes from the original proposal.
6 years ago
9f517f33ce
Create 1819-remove-presence-lists.md
6 years ago
ed68f940cd
towncrier
6 years ago
bf2b6e6daa
remove references to presence lists
6 years ago
9f443225ac
fix incorrect spelling of homeserver
6 years ago
577edeb53b
Say that !stable == unstable
6 years ago
6c7eea555a
Merge pull request #1773 from matrix-org/travis/spec/rooms
...
Add a room version specification
6 years ago
84a4ca62c3
Merge pull request #1786 from matrix-org/travis/spec/exp-caps
...
Add support for unstable feature advertising via /versions
6 years ago
052d68d83d
Merge pull request #1791 from matrix-org/travis/spec/rver-upgrades
...
Add room version upgrades
6 years ago
413bfaeb68
Add clarification that clients shouldn't use unstable things as stable
6 years ago
061f59547a
Minor wording changes
6 years ago
5cafcd103f
Fix copyright
...
> Since this is a copy-and-paste of old text, I think the copyright year should match when the original text was written, which according to git was 2017.
Co-Authored-By: turt2live <travpc@gmail.com>
6 years ago
50eba23669
Update MSC to match how room versions work
...
As per 1773.
6 years ago
0dfc64a9f4
Improve wording
6 years ago
bd5e760a0d
Simplify the description for room versions
...
Instead of trying to describe maturity, stability, and recommendedness in one list we should describe what is "safe" and "unsafe" to use. The default version is just something that servers should use, and is normally going to be stable.
6 years ago
3ec3adbc24
Proposal for add room_version to make_* fed APIs
6 years ago
Travis Ralston