-
Notifications
You must be signed in to change notification settings - Fork 474
Closed
Labels
enhancementfeature: WebRTC 🚡WebRTC connection between browsers and/or mobile clientsWebRTC connection between browsers and/or mobile clients
Milestone
Description
The nickname that is shown below the avatar is currently distributed through the datachannel by sending a nickChanged
event to the status
channel.
This is done once at call establishment and whenever the (guest) user changes the name.
We should change this to use the name from the participant list. This avoids having different places where the name of a user is stored / updated and allows removing the workaround for the MCU that periodically updates the name through the DataChannel (see #398).
@Ivansss adding this as issue so what we discussed doesn't get lost
Metadata
Metadata
Assignees
Labels
enhancementfeature: WebRTC 🚡WebRTC connection between browsers and/or mobile clientsWebRTC connection between browsers and/or mobile clients
Type
Projects
Relationships
Development
Select code repository
Activity
nickvergessen commentedon Jun 22, 2018
since we now store the guest name in the DB, I guess that should work fine
Ivansss commentedon Jun 22, 2018
Also display names for logged-in users should be retrieved from there.
So we no longer need
peer.nick
for users' display name.nickvergessen commentedon Mar 21, 2019
This should be a subset of #397 as we need to get rid of datachannels anyway