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

Fix typos

Browse source
This commit is contained in:
iinuwa 2020-09-23 16:37:26 -05:00 • committed by GitHub
parent 9be28c5ade
commit 07dbdab898
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
proposals/2414-optional-content-reporting-reason.md
View file

@ -15,13 +15,13 @@ seems to be a contradiction.
Note that the kicking and banning endpoints already have optional `reason` Note that the kicking and banning endpoints already have optional `reason`
parameters. The other membership endpoints mentioned in parameters. The other membership endpoints mentioned in
[#2367][membership-endpoints] will also add optional `reason` parameters, [#2367][membership-endpoints] will also add optional `reason` parameters,
so it seems that it would be more more consistent with the rest of the spec so it would be more more consistent with the rest of the spec to make this
to make this optional as well. optional as well.
### `score` Parameter ### `score` Parameter
The spec also requires the `score` parameter, but its usefulness is limited. The spec also requires the `score` parameter, but its usefulness is limited.
Offensiveness is difficult to measure, and is likely not going to be applied Offensiveness is difficult to measure and is likely not going to be applied
consistently across several rooms. Because of this ambiguity, it seems, many consistently across several rooms. Because of this ambiguity, it seems, many
clients [simply hard-code the integer value][hard-code]. clients [simply hard-code the integer value][hard-code].
@ -35,8 +35,8 @@ while not forcing clients to support the ambiguity it brings.
## Backwards Compatibility ## Backwards Compatibility
Since servers currently expect these field to be sent by all clients, making Since servers currently expect these fields to be sent by all clients, making
theme optional is a breaking change. Clients should check the spec versions them optional is a breaking change. Clients should check the spec versions
the homeserver supports to detect this change. the homeserver supports to detect this change.
[membership-endpoints]: https://github.com/matrix-org/matrix-doc/pull/2367 [membership-endpoints]: https://github.com/matrix-org/matrix-doc/pull/2367