3e06473305
Merge pull request #1859 from matrix-org/travis/fix-v2-scope
...
Change notice about room v2's scope to represent reality
6 years ago
1f05c44a0b
Merge pull request #1860 from matrix-org/travis/fix-spelling-1
...
Fix spelling mistake: endponts -> endpoints
6 years ago
0ed0fee261
Update specification/rooms/v2.rst
...
Co-Authored-By: turt2live <travpc@gmail.com>
6 years ago
772ba8dc2a
Add a table of contents to each room version spec
...
Fixes https://github.com/matrix-org/matrix-doc/issues/1852
We get clickable headers for free by doing this.
6 years ago
85578f9842
Fix spelling mistake: endponts -> endpoints
...
Fixes https://github.com/matrix-org/matrix-doc/issues/1677
6 years ago
cf11965a8e
Change notice about room v2's scope to represent reality
...
Fixes https://github.com/matrix-org/matrix-doc/issues/1851
6 years ago
8bd9ca4edd
Prep for r0.1.1 of s2s
6 years ago
bcef94ec70
Merge pull request #1847 from matrix-org/travis/s2s-unstable-warning
...
Add the "please use latest.html" warning to the s2s spec
6 years ago
3581368f1f
Add the "please use latest.html" warning to the s2s spec
...
Now that we have a release, we should be warning people who try and use the unstable spec as fact.
6 years ago
e9bac1b011
Remove wrong references to TLS fingerprints
...
Also fix some styling in the server discovery section - this didn't feel like it needed its own commit.
6 years ago
1f5783b329
fix links and wording
6 years ago
9631e4bcb1
Add a bit of text to ensure that the intro page isn't missed
6 years ago
8ace64bab7
r0.1.0 of the s2s specification
6 years ago
9364787b9c
Remove stability warning
6 years ago
fe7f582233
Fix several spelling mistakes
...
Signed-off-by: Aaron Raimist <aaron@raim.ist>
6 years ago
d94a70f49d
Warn clients about changes in event format
6 years ago
e27c83d9f8
Merge pull request #1817 from matrix-org/neilj/remove_presence_lists
...
remove references to presence lists
6 years ago
41e50d553e
Merge pull request #1830 from matrix-org/travis/spec/x509-wk
...
Specify .well-known s2s discovery and X.509 validation
6 years ago
6421582bf2
Clarifications and alter the error handling of .well-known
...
Note that MSC1831 changes the order, so the changes to MSC1708 might not make sense when combining all the proposals together. However, independently the change should make sense.
6 years ago
39b71413be
Update specification/server_server_api.rst
...
Co-Authored-By: turt2live <travpc@gmail.com>
6 years ago
1c30f5eba9
Clarify certificate usage and ports
6 years ago
df01acc6e2
Merge pull request #1828 from matrix-org/travis/spec/rooms-v3
...
Add specification for room version 3: Event IDs as hashes
6 years ago
a6243da03f
Wording changes and links
6 years ago
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
48e4d6e412
Document domain reuse concerns
...
Fixes https://github.com/matrix-org/matrix-doc/issues/1783
6 years ago
d2f012f4ea
Incorporate MSC1831
...
Original proposal: https://github.com/matrix-org/matrix-doc/pull/1831
Implementation proof: pending
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
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
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
c09fa6845e
Update presence.rst
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
0712fd36a2
75% majority now required for FCP
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
bf2b6e6daa
remove references to presence lists
6 years ago
9f443225ac
fix incorrect spelling of homeserver
6 years ago
6c7eea555a
Merge pull request #1773 from matrix-org/travis/spec/rooms
...
Add a room version specification
6 years ago
052d68d83d
Merge pull request #1791 from matrix-org/travis/spec/rver-upgrades
...
Add room version upgrades
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
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
ebe887d931
Grammar
...
Co-Authored-By: turt2live <travpc@gmail.com>
6 years ago
ba37f2d311
prompt->advertise
6 years ago
19e94815f9
Try and improve the understanding of room versions
6 years ago
0dde2489b6
Clarify what a Mandatory room version is
6 years ago
96d754f429
promote -> prompt
6 years ago
Travis Ralston