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
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
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: