-
Notifications
You must be signed in to change notification settings - Fork 348
Add Sliding Sync /sync/e2ee
endpoint for To-Device messages
#17167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 9 commits
f9e6e53
1e05a05
5e925f6
69f9143
d4ff933
371ec57
06d12e5
b8b70ba
c60a4f8
10ffae6
6bf4896
8871dac
0892283
adb7e20
f098355
6b7cfd7
b9e5379
9bdfa16
7331401
b23abca
821a1b3
35ca937
4ad7a8b
3092ab5
3539abe
5f194f9
02cecfa
f6122ff
2f112e7
c2221bb
717b160
514aba5
9749795
06ac1da
3da6bc1
d4b41aa
6606ac1
ab0b844
a482545
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
Add experimental [MSC3575](https://github.com/matrix-org/matrix-spec-proposals/pull/3575) Sliding Sync `/sync/e2ee` endpoint for To-Device messages. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thinking more on that "relieving pressure on the Sliding Sync proxy now" point. Since the proxy is just another Matrix client which uses the
( Am I missing something? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🤔 I think I wasn't taking into account that the proxy will be its own device that can be separate from device we can use for this endpoint. So acknowledging the To-Device messages for one device doesn't affect the other. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Discussed this point in a meeting with @erikjohnston today and I think this might be a problem since it will be one device consuming everything. Would probably require updates to the Sliding Sync proxy to utilize both properly. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would have thought you'd either have a device using the proxy entirely or you have a device using Synapse's SS impl entirely, not a weird mixture of both. If so, this is not a problem afaict? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The idea of this endpoint isn't to remove pressure from the proxy directly.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
This isn't true though, because the proxy will consume to-device messages that would have been delivered via There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hmm indeed. So the migration should ideally be all-on-synapse, instead of half-proxy, half-synapse. Gotcha. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
You could probably use a whole another device for all e2ee operations, but it's quite ugly and a workaround. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. A lot of this is just sharing and summarizing the clarifications from @erikjohnston 🙇 Discussed this point a bit further and got a little more clarification. The main aim of This means that this endpoint probably won't be useful until we have a Sliding Sync implementation in Synapse itself. I started working on It may very well turn out that [1] Sliding sync proxy shares the same device as the ElementX client (as far as it has been explained to me). The way it works is that EX calls the SS proxy with that token, and then the SS proxy caches it to make the requests. [2] For onlookers, the
MadLittleMods marked this conversation as resolved.
Show resolved
Hide resolved
|
Uh oh!
There was an error while loading. Please reload this page.