Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-03-22 11:24:08 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Changing client config to account data in more places

Browse source 
changing the URL fragments in a few missed spaces
This commit is contained in:
yoyodragon 2024-12-19 01:50:31 +05:30
parent 478af3ae22
commit 7ce9e0546d
3 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
content/client-server-api/modules/read_markers.md
View file

@ -12,7 +12,7 @@ read receipt marks the last event of the second section.
##### Events ##### Events
The user's fully read marker is kept as an event in the room's [account The user's fully read marker is kept as an event in the room's [account
data](#client-config). The event may be read to determine the user's data](#account-data). The event may be read to determine the user's
current fully read marker location in the room, and just like other current fully read marker location in the room, and just like other
account data events the event will be pushed down the event stream when account data events the event will be pushed down the event stream when
updated. updated.
@ -66,7 +66,7 @@ attention irrespective of [read receipts](#receipts) or
##### Events ##### Events
The user's unread marker in a room is kept under an `m.marked_unread` The user's unread marker in a room is kept under an `m.marked_unread`
event in the room's [account data](#client-config). The event may be read event in the room's [account data](#account-data). The event may be read
to determine the user's current unread marker state in the room. Just to determine the user's current unread marker state in the room. Just
like other account data events, the event will be pushed down the event like other account data events, the event will be pushed down the event
stream when updated. stream when updated.

2
content/client-server-api/modules/secrets.md
View file

@ -21,7 +21,7 @@ sharing", "SSSS", or "4S".
#### Storage #### Storage
When secrets are stored on the server, they are stored in the user's When secrets are stored on the server, they are stored in the user's
[account-data](#client-config), using an event type equal to the [account-data](#account-data), using an event type equal to the
secret's identifier. The keys that secrets are encrypted with are secret's identifier. The keys that secrets are encrypted with are
described by data that is also stored in the user's account-data. Users described by data that is also stored in the user's account-data. Users
can have multiple keys, allowing them to control what sets of secrets can have multiple keys, allowing them to control what sets of secrets

2
data/api/client-server/registration.yaml
View file

@ -635,7 +635,7 @@ paths:
might still serve unredacted copies. might still serve unredacted copies.
The server should additionally erase any non-event data The server should additionally erase any non-event data
associated with the user, such as [account data](/client-server-api/#client-config) associated with the user, such as [account data](/client-server-api/#account-data)
and [contact 3PIDs](/client-server-api/#adding-account-administrative-contact-information). and [contact 3PIDs](/client-server-api/#adding-account-administrative-contact-information).
Defaults to `false` if not present. Defaults to `false` if not present.