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

Figure out how to deal with device names and keep them in sync with Synapse #3919

Open
4 tasks
reivilibre opened this issue Jan 29, 2025 · 0 comments
Open
4 tasks
Labels
A-Device-Management Related to sessions and device management

Comments

@reivilibre
Copy link
Contributor

Even in MAS mode, users can view and edit device names through the Synapse client-server API. (Maybe the device can only edit its own name, but it doesn't matter on the exact details.)

That said, we'd like to show device names in the MAS device management UI (because this makes each device more relatable).

However, we can't simply remove them from Synapse, because devices are the individual units acting as cryptographic parties, so clients have to have a client-server API to inspect those.

This seems to suggest that we need to keep device names in sync between MAS and Synapse, though maybe name changes can be funnelled through MAS.

Specific points to be addressed:

  • we ignore the initial display name clients send us on /login, we should probably still get those and record them
  • we should compute a human-readable device name from MAS and give that to Synapse when we provision them — this is tricky because it depends on the user locale
  • we should have a feature to let users rename their sessions in MAS
  • we should catch device renames from Synapse and get them into MAS
@reivilibre reivilibre added the A-Device-Management Related to sessions and device management label Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Device-Management Related to sessions and device management
Projects
None yet
Development

No branches or pull requests

1 participant