|
|
|
@ -15,13 +15,13 @@ seems to be a contradiction.
|
|
|
|
|
Note that the kicking and banning endpoints already have optional `reason`
|
|
|
|
|
parameters. The other membership endpoints mentioned in
|
|
|
|
|
[#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
|
|
|
|
|
to make this optional as well.
|
|
|
|
|
so it would be more more consistent with the rest of the spec to make this
|
|
|
|
|
optional as well.
|
|
|
|
|
|
|
|
|
|
### `score` Parameter
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
Since servers currently expect these field to be sent by all clients, making
|
|
|
|
|
theme optional is a breaking change. Clients should check the spec versions
|
|
|
|
|
Since servers currently expect these fields to be sent by all clients, making
|
|
|
|
|
them optional is a breaking change. Clients should check the spec versions
|
|
|
|
|
the homeserver supports to detect this change.
|
|
|
|
|
|
|
|
|
|
[membership-endpoints]: https://github.com/matrix-org/matrix-doc/pull/2367
|
|
|
|
|