wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Remove 'Table of Contents'

Browse source
This commit is contained in:
Will 2021-01-19 15:32:30 -08:00
parent 9d4803c8af
commit 74adbfc1ec
No known key found for this signature in database
GPG key ID: 385872BB265E8BF8
12 changed files with 0 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

2
content/application-service-api.md
View file

@ -14,8 +14,6 @@ Application Service API (AS API) defines a standard API to allow such
extensible functionality to be implemented irrespective of the
underlying homeserver implementation.
Table of Contents
## Changelog
**Version: %APPSERVICE\_RELEASE\_LABEL%**

2
content/client-server-api/_index.md
View file

@ -12,8 +12,6 @@ designed to support both lightweight clients which store no state and
lazy-load data from the server as required - as well as heavyweight
clients which maintain a full local persistent copy of server state.
Table of Contents
## Changelog
**Version: %CLIENT\_RELEASE\_LABEL%**

2
content/identity-service-api.md
View file

@ -15,8 +15,6 @@ can be established, validated, and used. This description technically
may apply to any 3PID, but in practice has only been applied
specifically to email addresses and phone numbers.
Table of Contents
## Changelog
**Version: %IDENTITY\_RELEASE\_LABEL%**

2
content/proposals.md
View file

@ -8,8 +8,6 @@ type: docs
Proposals for Spec Changes to Matrix
Table of Contents
If you are interested in submitting a change to the Matrix
Specification, please take note of the following guidelines.

2
content/push-gateway-api.md
View file

@ -10,8 +10,6 @@ Clients may want to receive push notifications when events are received
at the homeserver. This is managed by a distinct entity called the Push
Gateway.
Table of Contents
## Changelog
**Version: %PUSH\_GATEWAY\_RELEASE\_LABEL%**

2
content/rooms/v1.md
View file

@ -7,8 +7,6 @@ weight: 10
This room version is the first ever version for rooms, and contains the
building blocks for other room versions.
Table of Contents
## Client considerations
Clients may need to consider some algorithms performed by the server for

2
content/rooms/v2.md
View file

@ -7,8 +7,6 @@ weight: 20
This room version builds off of [version 1](v1.html) with an improved
state resolution algorithm.
Table of Contents
## Server implementation components
Warning

2
content/rooms/v3.md
View file

@ -7,8 +7,6 @@ weight: 30
This room version builds on [version 2](v2.html) with an improved event
format.
Table of Contents
## Client considerations
This room version changes the format for event IDs sent to clients.

2
content/rooms/v4.md
View file

@ -7,8 +7,6 @@ weight: 40
This room version builds on [version 3](v3.html) using a different
encoding for event IDs.
Table of Contents
## Client considerations
This room version changes the format form event IDs sent to clients.

2
content/rooms/v5.md
View file

@ -7,8 +7,6 @@ weight: 50
This room version builds on [version 4](v4.html) while enforcing signing
key validity periods for events.
Table of Contents
## Client considerations
There are no specific requirements for clients in this room version.

2
content/rooms/v6.md
View file

@ -7,8 +7,6 @@ weight: 60
This room version builds on [version 5](v5.html) while changing various
authorization rules performed on events.
Table of Contents
## Client considerations
The redaction algorithm has changed from [room version 1](v1.html) to

2
content/server-server-api.md
View file

@ -47,8 +47,6 @@ EDUs and PDUs are further wrapped in an envelope called a Transaction,
which is transferred from the origin to the destination homeserver using
an HTTPS PUT request.
Table of Contents
## Changelog
**Version: %SERVER\_RELEASE\_LABEL%**