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

New users in group do not see my name #500

Open
pcworld opened this issue Apr 15, 2024 · 2 comments
Open

New users in group do not see my name #500

pcworld opened this issue Apr 15, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@pcworld
Copy link

pcworld commented Apr 15, 2024

I use mautrix-signal as my main client, I do not use an official Signal app.
I originally set up my account via signal-cli, and then linked the Signal bridge to it. I joined some chat groups, and in order for others to see my name, I set my name via signal-cli updateProfile --given-name <my name>. This worked successfully, and other Signal users within the group could see my name in the group chat member list on the official Signal clients.

However, after some time passed, some users have reported to me that they do not see my name, they just see my phone number in the group chat member list. So far, these users have in common that they joined the group after I originally set my display name (however, this could also be coincidence). I then issued signal-cli updateProfile --given-name ... again and now they do see my name.

I wonder whether the Signal protocol requires that my profile name needs to be broadcast once new users join a group, and maybe the Signal bridge could implement that?

@pcworld pcworld added the bug Something isn't working label Apr 15, 2024
@maltee1
Copy link
Contributor

maltee1 commented Apr 16, 2024

This is probably unrelated to the bridge and should be filed with Signal-cli

@pcworld
Copy link
Author

pcworld commented Apr 17, 2024

If my hypothesis is true and the profile name needs to be broadcast after new joins, I don't really see how signal-cli could fix this, since I only invoke signal-cli manually when needed and there is no way to run it as a daemon afaik.

Or is it out of scope for the bridge to handle such kind of things because it's not supposed to work as a main device? Though in that case I'm not really sure which kind of component should be responsible when one doesn't use one of the official Signal clients.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

2 participants