mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-08-05 07:27:52 +02:00
Compare commits
No commits in common. "96438321bd8e4d2782337d0d15e440acef1b49e1" and "e81ffe115dc9f977a3e3b58403b82c263e8168b7" have entirely different histories.
96438321bd
...
e81ffe115d
2
.github/CODEOWNERS
vendored
2
.github/CODEOWNERS
vendored
|
|
@ -1 +1 @@
|
||||||
* @matrix-org/spec-core-team @zecakeh
|
* @matrix-org/spec-core-team
|
||||||
|
|
|
||||||
|
|
@ -1 +0,0 @@
|
||||||
Fix various typos throughout the specification.
|
|
||||||
|
|
@ -1 +0,0 @@
|
||||||
Update CODEOWNERS file.
|
|
||||||
|
|
@ -1 +0,0 @@
|
||||||
Fix various typos throughout the specification.
|
|
||||||
|
|
@ -51,7 +51,7 @@ interoperability.
|
||||||
|
|
||||||
URL-safe unpadded Base64 is identical to standard unpadded Base64, except that
|
URL-safe unpadded Base64 is identical to standard unpadded Base64, except that
|
||||||
it uses `-` (minus) as the 62nd character in the alphabet, and `_` (underscore)
|
it uses `-` (minus) as the 62nd character in the alphabet, and `_` (underscore)
|
||||||
as the 63rd. This matches [RFC4648’s definition of URL-safe base64](https://tools.ietf.org/html/rfc4648#section-5).
|
as the 63rd.
|
||||||
|
|
||||||
## Binary data
|
## Binary data
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -276,8 +276,9 @@ internal state of the hash function.
|
||||||
|
|
||||||
After formatting each query, the string is run through SHA-256 as
|
After formatting each query, the string is run through SHA-256 as
|
||||||
defined by [RFC 4634](https://tools.ietf.org/html/rfc4634). The
|
defined by [RFC 4634](https://tools.ietf.org/html/rfc4634). The
|
||||||
resulting bytes are then encoded using [URL-Safe unpadded
|
resulting bytes are then encoded using URL-Safe [Unpadded
|
||||||
Base64](/appendices/#url-safe-unpadded-base64).
|
Base64](/appendices#unpadded-base64) (similar to [room version
|
||||||
|
4's event ID format](/rooms/v4#event-ids)).
|
||||||
|
|
||||||
An example set of queries when using the pepper `matrixrocks` would be:
|
An example set of queries when using the pepper `matrixrocks` would be:
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -2,8 +2,11 @@
|
||||||
---
|
---
|
||||||
{{% added-in v=4 %}} The event ID is the [reference
|
{{% added-in v=4 %}} The event ID is the [reference
|
||||||
hash](/server-server-api#calculating-the-reference-hash-for-an-event) of
|
hash](/server-server-api#calculating-the-reference-hash-for-an-event) of
|
||||||
the event encoded using [URL-safe unpadded
|
the event encoded using a variation of [Unpadded
|
||||||
Base64](/appendices/#url-safe-unpadded-base64).
|
Base64](/appendices#unpadded-base64) which replaces the 62nd and
|
||||||
|
63rd characters with `-` and `_` instead of using `+` and `/`. This
|
||||||
|
matches [RFC4648's definition of URL-safe
|
||||||
|
base64](https://tools.ietf.org/html/rfc4648#section-5).
|
||||||
|
|
||||||
Event IDs are still prefixed with `$` and might result in looking like
|
Event IDs are still prefixed with `$` and might result in looking like
|
||||||
`$Rqnc-F-dvnEYJTyHq_iKxU2bZ1CI92-kuZq3a5lr5Zg`.
|
`$Rqnc-F-dvnEYJTyHq_iKxU2bZ1CI92-kuZq3a5lr5Zg`.
|
||||||
|
|
|
||||||
|
|
@ -156,7 +156,7 @@ paths:
|
||||||
public_key:
|
public_key:
|
||||||
type: string
|
type: string
|
||||||
description: |
|
description: |
|
||||||
The public key, encoded using [standard unpadded Base64](/appendices/#unpadded-base64) or [URL-safe unpadded Base64](/appendices/#url-safe-unpadded-base64).
|
The public key, encoded using standard or URL-safe [unpadded Base64](/appendices/#unpadded-base64).
|
||||||
key_validity_url:
|
key_validity_url:
|
||||||
type: string
|
type: string
|
||||||
description: |
|
description: |
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue