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

Be clearer about errors and what to do with current room versions.

Browse source
This commit is contained in:
Patrick Cloke 2020-05-13 14:02:50 -04:00
parent bbbd9c4c33
commit 03588cbf0d
1 changed files with 11 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

14
proposals/2540-stricter-event-validation.md
View file

@ -20,18 +20,26 @@ even support these by default. One common additional feature is handling
## Proposal
In a future room version, Matrix server implementations are to strictly enforce
the JSON compliance of the Canonical JSON specification for events.
In a future room version, homeserver implementations are to strictly enforce
the JSON compliance of the Canonical JSON specification for events. Events that
do not abide by these rules should be rejected with the error code `M_NOT_JSON`.
The rationale for doing this in a future room version is to avoid a split brain
room -- where some federated servers believe an event is valid and others reject
it as invalid. Rooms will be able to opt into this behavior as part of a room
version upgrade.
Homeserver implementations are not to strictly enforce this JSON compliance in
[stable room versions](https://matrix.org/docs/spec/#complete-list-of-room-versions).
The rationale is essentially the same as why a future room version is necessary,
this ensures that all federated servers treat the same events as valid.
## Potential issues
N/A
Homeserver implementations might include JSON parsers which are stricter than
others. It may not be worthwhile or reasonable to loosen those restrictions for
stable room versions.
## Alternatives