Skip to content
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

Invited users don't trigger device_list updates via /sync at the point of being invited. #3503

Open
Tracked by #2411
matrixbot opened this issue Dec 16, 2023 · 1 comment

Comments

@matrixbot
Copy link
Collaborator

matrixbot commented Dec 16, 2023

This issue has been migrated from #3503.


I implemented matrix-org/synapse#3484 with the assumption that it would cause invited users to trigger a /device_list update via /sync (as joined users do).

In practice it doesn't work (but clients are okay anyway as they query the device list via /unstable/keys/query whenever the membership list changes anyway).

@matrixbot matrixbot changed the title Dummy issue Invited users don't trigger device_list updates via /sync at the point of being invited. Dec 21, 2023
@matrixbot matrixbot reopened this Dec 21, 2023
@richvdh
Copy link
Member

richvdh commented Apr 30, 2024

This issue isn't very clear, but I think it's trying to say something like:

When you first join a room with a user, or a user joins a room with you, that user is listed under device_lists: changed in the /sync response (cf https://spec.matrix.org/v1.10/client-server-api/#e2e-extensions-to-sync). The suggestion is that should also happen when a user is invited to a room, since invited users also receive copies of the message keys in suitably-configured rooms.

In practice there are bigger problems around tracking the device lists of invited users: see #3504.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants