c6dd5951a1
Clients can cache the hash details if they want to
5 years ago
2a2dddab94
Merge pull request #2151 from reivilibre/push_id_event_id
...
Fix Push Gateway API example: Field renamed to event_id
5 years ago
8f3e588708
pepper is not a secret val. Still needs to be around.
5 years ago
bf9f2cd1b6
Merge pull request #2183 from lucavb/master
...
Spec clarification regarding authorisation rules in v1
5 years ago
f4d6b6c261
Fixed broken indentations
5 years ago
c7a23557d4
Last cosmetic changes
...
switched back to the use of `.. NOTE::`
5 years ago
3b8c57e06c
Don't require servers/clients to support "none"
5 years ago
3031df79cc
Add example for none algo
5 years ago
9fd6bd3184
Add details about why this proposal should exist
5 years ago
b26a9ed1fd
Expand on why we can't trust dirty homeservers
5 years ago
577021f12b
resolve some comments
5 years ago
d43111cdd2
Incorporated @turt2live suggestions.
...
Used **Note** to describe notes around the authorisation rules. Otherwise restored the original state for the consequences from the auth rules.
Moved the clarification regarding default power levels up above the auth rules. Removed third sentence. And followed @turt2live's example, but opted for "for users in that room" because the default user power level is applied to all users.
5 years ago
887cd5e7d0
I really hope someone doesn't invest none-hash
5 years ago
0444c8016b
review comments
5 years ago
4503327450
Add some compatibility hacks.
5 years ago
094005dca1
Incorporated @turt2live suggestions.
...
Added missing added and removed to the rule, because these keys are not required for m.room.power_levels. Also moved the note down to the Note section.
5 years ago
8aece4f644
Incorporated @richvdh suggestions
5 years ago
15994c61a5
Clarification regarding authorisation rules
...
The rules for m.room.power_levels power were somewhat unclear regarding the behaviour towards the always present keys, such as kick and ban. Additionally, it is now also clarified that in the users and events dictionary also added and removed keys are taken into consideration.
5 years ago
9ebcff5758
fix typo, add section on html details element
5 years ago
36cb8ed894
none -> m.none
5 years ago
1f786ae6dc
commit image into repo, fix typo
5 years ago
d9269b084f
Exclude pubkey endpoints from auth
5 years ago
a1de6ff634
Hopefully clarify some bits
5 years ago
b09d48a9f7
Spec link
5 years ago
78d46b2890
Proposal to move the `redacts` key to a sane place
5 years ago
25a47afa32
unnecessary capital mk. 2
...
Co-Authored-By: J. Ryan Stinnett <jryans@gmail.com>
5 years ago
6e061b1baf
unnecessary capital
...
Co-Authored-By: J. Ryan Stinnett <jryans@gmail.com>
5 years ago
f474b31f5f
typo
...
Co-Authored-By: J. Ryan Stinnett <jryans@gmail.com>
5 years ago
3514437d24
Ability for client/server to decide on no hashing
5 years ago
9bb6ad80d1
typo
5 years ago
7b0f5ea77b
Merge pull request #2159 from jimmycuadra/reference-hash-purpose
...
Clarify the purpose of reference hashes.
5 years ago
a3d2d14dae
Rephrase explanation of the purpose of reference hashes and link to the
...
room version spec.
Signed-off-by: Jimmy Cuadra <jimmy@jimmycuadra.com>
5 years ago
52643a92c6
Less confusing wording on Application Service's Legacy Routes ( #2160 )
...
https://matrix.org/docs/spec/application_service/r0.1.1#legacy-routes
The "becomes" wording made it a little bit confusing for which was the new route and which was the old.
5 years ago
5df86dabe0
Clarify the purpose of reference hashes.
...
The server-server specification describes a "reference hash" of an event
and how to calculate it, but is otherwise not mentioned anywhere else in
the document. This change adds a sentence to explain that they are used
for event identifiers in later room versions, which are described in
other documents.
Signed-off-by: Jimmy Cuadra <jimmy@jimmycuadra.com>
5 years ago
ee04b778cf
Merge pull request #2157 from a-andreyev/aa13q/api-client-server-device-keys
...
Client-server: Fix upload keys example request
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
ed67e26037
pepper must not be an empty string, append medium
5 years ago
1963a24832
fix attacks paragraph
5 years ago
dd8a6549c9
Address review comments
5 years ago
701d340da1
Remove exception for request/submitToken
5 years ago
bf8a1e5d5f
Add way to get the HS to bind/unbind existing 3pids
5 years ago
3702669424
update from comments
5 years ago
30dcc28f9b
try & clarify that HS signature isn't the only acceptable auth for unbind
5 years ago
f4a1e02884
simple method once more
5 years ago
db5ce0c69e
Merge pull request #2152 from matrix-org/jryans/room-one-to-one-push-rule
...
Clarify `.m.rule.room_one_to_one` push rule
5 years ago
9208c5cd13
Add changelog
5 years ago
4c65660b96
Clarify `.m.rule.room_one_to_one` push rule
...
This clarifies the `.m.rule.room_one_to_one` push rule by adding a condition on
event type. Some parts of the spec already had this info, while others were
missing it. Synapse has had this behaviour since the push rule appeared.
Fixes https://github.com/matrix-org/matrix-doc/issues/2150
5 years ago
8033ab1c86
Fix Push Gateway API example: Field renamed to event_id
...
I believe this was forgotten in:
71cb646541
5 years ago
53bd384f2e
Clarify salting
5 years ago
1a669348d8
http status code
5 years ago
Andrew Morgan