You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 15, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: docs/Protocol Specifications/core.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ weight: 0
12
12
13
13
!!! warning
14
14
15
-
The polyproto specification document is in an **alpha** phase. Please report any inconsistencies,
15
+
The polyproto specification document is in an early **beta** phase. Please report any inconsistencies,
16
16
missing or duplicate information and other mistakes at [github.com/polyphony-chat/docs/issues](https://github.com/polyphony-chat/docs/issues).
17
17
18
18
[Semantic versioning v2.0.0](https://semver.org/spec/v2.0.0.html) is used to version this specification.
@@ -776,7 +776,7 @@ situations:
776
776
|`4007`| Invalid sequence number(s) | The client has sent a heartbeat containing sequence numbers that were invalid. | x | x ||
777
777
|`4008`| Rate limited | The client has sent payloads too quickly. || x ||
778
778
|`4009`| Timeout | The session has been deemed to be timed out. This can happen if a heartbeat or heartbeat ACK has not been sent in due time. | x (If sent by server) | x | x |
779
-
|`4010`|Unresumeable| The server has determined that this session cannot be resumed. The client should initiate a new, fresh connection to the gateway instead. || x ||
779
+
|`4010`|Unresumable | The server has determined that this session cannot be resumed. The client should initiate a new, fresh connection to the gateway instead. || x ||
780
780
781
781
#### 3.2.6 Guaranteed delivery of gateway messages through package acknowledgement
782
782
@@ -946,7 +946,7 @@ token. This verification must be done by proving the following facts:
946
946
- The presented ID-Cert has not been revoked. See [section 6.4.1](#641-verifying-that-a-newly-retrieved-id-cert-is-not-out-of-date)
947
947
for information on how this is done.
948
948
- The client is in possession of the private key that corresponds to the presented ID-Certs' subject
949
-
public key. Must be proven using a [challenge string](#42-challenge-strings-and-key-trials).
949
+
public key. Must be proven using a [key trial](#42-key-trials).
950
950
951
951
#### 4.1.2 Sensitive actions
952
952
@@ -1045,7 +1045,7 @@ servers from generating federation tokens for users without their consent and kn
1045
1045
However, it can be mitigated a bit by making it more difficult for malicious home servers to do
1046
1046
something like this without the actor noticing.
1047
1047
1048
-
Polyproto servers need to inform users of new sessions. This visibility hampers malicious home
1048
+
polyproto servers need to inform users of new sessions. This visibility hampers malicious home
1049
1049
servers, but does not solve the issue of them being able to create federation tokens for servers the
1050
1050
actor does not connect to. This is because, naturally, users cannot receive notifications without a
1051
1051
connection. Clients re-establishing server connections must be updated on any new sessions
@@ -1277,7 +1277,7 @@ an ID-Cert consists of:
1277
1277
A client that has this second factor of authentication stored
1278
1278
should renew the ID-Cert of the authenticated actor without further interaction.
1279
1279
1280
-
Server ID-Certs should be rotated way less often (every 1-3 years). Only rotate a server ID-Cert
1280
+
Server ID-Certs should be rotated way less often (every 1–3 years). Only rotate a server ID-Cert
1281
1281
if it is suspected to be compromised, is lost, or has expired.
1282
1282
1283
1283
```mermaid
@@ -2444,7 +2444,7 @@ The API routes for managing discoverability are documented in the
2444
2444
2445
2445
### 9.1.1 Changing a primary service provider
2446
2446
2447
-
Keys are unique in the actor-scoped service->service-provider table. Actors wanting
2447
+
Keys are unique in the actor-scoped service → service-provider table. Actors wanting
2448
2448
to register for two or more different implementations of the same service must select which
2449
2449
service provider to use as a "primary service provider" for that service.
0 commit comments