f352de90c3
Merge pull request #2536 from uhoreg/cross-signing-spec
...
initial spec for cross-signing
4 years ago
a5ebedc131
apply suggestions from review
4 years ago
5a699f2650
Merge pull request #2518 from matrix-org/kitsune/cleanup
...
Assorted cleanup pieces
4 years ago
6da06383e8
Allow `/make_join` to return a 404 ( #2688 )
...
Specify that `GET /_matrix/federation/v1/make_join/{roomId}/{userId}` can
return a 404 if the room is unknown.
4 years ago
465ed38416
Merge pull request #2647 from jplatte/event-titles
...
Make event's title fields UpperCamelCase and distinguish /sync ones
5 years ago
763e5654cc
Make event's title fields UpperCamelCase and distinguish /sync ones
5 years ago
049275c33b
Consistently use the title UnsignedData for the unsigned object
5 years ago
efebba62de
result may also include signatures
5 years ago
8e7c0dfb93
Merge remote-tracking branch 'origin/master' into kitsune/cleanup
5 years ago
ec0b9badc7
Merge remote-tracking branch 'origin/master' into cross-signing-spec
5 years ago
040a91f42d
api/: More cleanup in descriptions
...
(and a fix in one example).
5 years ago
db72e7caea
Merge pull request #2575 from matrix-org/travis/clarification/send-join
...
Clarify the auth_chain and state requirements for /send_join
5 years ago
669377888e
Fix more typos throughout the specification
...
Fixes https://github.com/matrix-org/matrix-doc/issues/2193
5 years ago
67d46fa881
Clarify the auth_chain and state for send_join
...
Fixes https://github.com/matrix-org/matrix-doc/issues/2467
Fixes https://github.com/matrix-org/matrix-doc/issues/2464
This is based on looking at Synapse, not actually testing it. Within the send_join handling functions, an "event context" is acquired [here](d14c4d6b6d/synapse/handlers/federation.py (L1472)d14c4d6b6d/synapse/state/__init__.py (L286-L289)d14c4d6b6d/synapse/handlers/federation.py (L1494-L1501)d14c4d6b6d/synapse/state/__init__.py (L351)
5 years ago
06b0c1762a
Move the send_join response to its own definition
...
Both APIs need clarification, so dedupe the changes.
We should also probably deprecate some of this stuff so we can eventually remove it.
5 years ago
36ed6e94a2
Re-introduce signature schemas
5 years ago
6a8ba9b1d6
improve description of key object in CS and include a link in Fed
5 years ago
5b38c04e19
make definition of signatures fields more consistent
5 years ago
74b627ac0b
Fix the response format of the `/send` endpoint
...
Fixes https://github.com/matrix-org/matrix-doc/issues/2236
5 years ago
fc91946e5a
Update api/server-server/backfill.yaml
...
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
5 years ago
9765116c47
Make backfill wording clearer
5 years ago
05e83f2e7d
Fix more describes -> describe
5 years ago
7c0046ffc7
describes -> describe
5 years ago
d419e3b38a
Remove extraneous spaces
5 years ago
a2a1694c35
Spec v2 send_join and send_leave endpoints
...
MSC: https://github.com/matrix-org/matrix-doc/pull/1802
Fixes https://github.com/matrix-org/matrix-doc/issues/2541
This also adds the v2 invite endpoint to the ACL protected list as that appears to be an omission.
5 years ago
42ae5c966a
Clarify the limits of prev_events and auth_events
...
Fixes https://github.com/matrix-org/matrix-doc/issues/2307
These restrictions are due to a Synapse change which never made it to the spec prior to the MSC process. This is therefore documenting an omission.
Synapse's numbers are verified here: 207b1737ee/synapse/handlers/federation.py (L1183-L1213)207b1737ee/synapse/handlers/federation.py (L829-L837)https://github.com/matrix-org/matrix-doc/pull/1594 should render the `auth_events` limitation unnecessary.
No changes are required to the the "checks on receipt of a PDU" section of the server-server spec as it starts with "must be a valid event", to which an event is invalid if it contains too many prev or auth events.
5 years ago
a8910fe323
initial spec for cross-signing
5 years ago
6b8b31ce63
correct use of required annotation in json-schema
...
https://tools.ietf.org/html/draft-handrews-json-schema-validation-02#section-6.5.3
5 years ago
fc03f7faa6
Remove query_auth from the specification per MSC2451.
5 years ago
8d865ca53a
Add s2s POST /publicRooms per MSC2197
...
See https://github.com/matrix-org/matrix-doc/pull/2197
5 years ago
9ed19a37ad
Client-server: Fix upload keys example request
...
Contributes to #1733
Signed-off-by: Alexey Andreyev <aa13q@ya.ru>
5 years ago
8ac555f870
Merge pull request #2083 from matrix-org/travis/1.0/key-object
...
Clarify the key object definition for the key management API
6 years ago
8b7887dfc2
Link to key algorithms section
6 years ago
6d60258e25
Merge pull request #2080 from matrix-org/travis/1.0/msc2076-msc2077-v5-rooms
...
Spec v5 rooms: Key validity
6 years ago
b7378a860a
Merge pull request #2097 from matrix-org/travis/1.0/common-themes
...
Specify some of the common concepts for Matrix in the index
6 years ago
cf19f52576
Enforce 7 day validity requirement everywhere
...
also misc formatting fixes
6 years ago
6d62a1b444
Merge pull request #2084 from matrix-org/travis/1.0/s2s-swagger-touchups
...
Touchups on the s2s swagger definitions
6 years ago
70da564e2b
Merge pull request #2067 from matrix-org/travis/1.0/stripped-state
...
Clarify exactly what StrippedState is
6 years ago
b9c9396c11
Specify some of the common concepts for Matrix in the index
...
See https://github.com/matrix-org/matrix-doc/pull/2061
Fixes https://github.com/matrix-org/matrix-doc/issues/1468
Fixes https://github.com/matrix-org/matrix-doc/issues/1528
The section is not referenced by the specifications yet - they do a fairly good job of explaining it over and over. In future, it would be good to point all the references to the index.
6 years ago
9bf0103ef3
Clarify how many PDUs are in a given transaction object
...
Fixes https://github.com/matrix-org/matrix-doc/issues/2093
6 years ago
e115e3439d
Touchups on the s2s swagger definitions
...
Duplicate properties, wrong types, etc.
6 years ago
a19eb59f13
Clarify the key object definition for the key management API
...
Fixes https://github.com/matrix-org/matrix-doc/issues/1907
One too far
6 years ago
a6314df44c
Spec v5 rooms: Key validity
...
Proposals:
* [MSC2076](https://github.com/matrix-org/matrix-doc/pull/2076 )
* [MSC2077](https://github.com/matrix-org/matrix-doc/pull/2077 )
Implementation references:
* 00bf99fa62https://github.com/matrix-org/synapse/pull/5354
* https://github.com/matrix-org/synapse/pull/5321
No known differences from the proposals are included here - alterations are accidental.
6 years ago
0b45f3795b
Rename example to invite_room_state
...
This is a better representation of what it actually is
6 years ago
237d585e07
Shorten references to StrippedState in s2s spec
6 years ago
b9c4a2561f
Fix examples of StrippedState in s2s spec
6 years ago
7a07a6b358
Clarify exactly what StrippedState is
...
Fixes https://github.com/matrix-org/matrix-doc/issues/2066
The expectation everywhere is that the `sender` is required. `/initialSync` references StrippedState through a `m.room.member` event reference, and does not need editing.
6 years ago
699cafe670
v4 is v4, not v3
6 years ago
3b0e194ff7
Add version 4 rooms to the spec
...
As per [MSC1884](https://github.com/matrix-org/matrix-doc/pull/1884 ) and [MSC2002](https://github.com/matrix-org/matrix-doc/pull/2002 ).
No known changes since the proposals were accepted.
Due to being in the area: This fixes https://github.com/matrix-org/matrix-doc/issues/1863
6 years ago
3c62b90dfb
Add missing punctuation
6 years ago
Hubert Chathi