@@ -51,7 +51,7 @@ There are some common reasons why an error occurred. These are encoded in the
51
51
totally legitimate to “handle” an event by doing nothing and not throwing this
52
52
error. It is at the discretion of the bridge author to find a good balance
53
53
between informing the user and preventing unnecessary spam. Throwing this
54
- error only for some subtypes of an event if fine.
54
+ error only for some subtypes of an event is fine.
55
55
56
56
* ` m.bridge_unavailable ` The homeserver couldn't reach the bridge.
57
57
@@ -130,7 +130,7 @@ error(s) having a sender of the same bridge as the revocation event are
130
130
considered revoked. Clients can show a revoke error e.g. as “Delivered to
131
131
Discord at 14:52.” besides the original event.
132
132
133
- On an unsuccessful retry the bridge may edit the errors content to reflect the
133
+ On an unsuccessful retry the bridge may edit the error's content to reflect the
134
134
new state, e.g. because the type of error changed or to communicate the new
135
135
time.
136
136
@@ -163,14 +163,15 @@ Example of the new retry events:
163
163
Overview of the relations between the different event types:
164
164
165
165
```
166
+ m.references
166
167
________________ _____________________
167
168
| | | |
168
169
| Original Event |-+-| Bridge Error |
169
170
|________________| | |_____________________|
170
171
| _____________________
171
172
| | |
172
173
+-| Retry Request |
173
- m.references | |_____________________|
174
+ | |_____________________|
174
175
| _____________________
175
176
| | |
176
177
+-| Bridge Error Revoke |
@@ -187,7 +188,7 @@ otherwise.
187
188
In the case the bridge is down or otherwise disconnected from the homeserver, it
188
189
naturally has no way to inform its users about the unavailability. In this case
189
190
the homeserver can stand in as an agent for the bridge and answer requests in
190
- its responsibility .
191
+ its absence .
191
192
192
193
For this to happen, the homeserver will send out a bridge error event in the
193
194
moment a transaction delivery to the bridge failed. The clients at this point
0 commit comments