-
Notifications
You must be signed in to change notification settings - Fork 25
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
Unknown contact handling #98
Comments
Maybe I misunderstand contacts and profiles, but what I think is that contacts are "known numbers" that may optionally be assigned a name in Signal, and profiles are what a person advertises itself to be. So in my opinion, contact names should not be assigned the profile names, instead the application should first query the contact name, and if that does not exist, fetch the profile and show that as a fallback. |
Actually in Signal-Android every person, also all the persons in all groups are transformed to a contact in the contact list. The "name" of the person/chat will be the username until i define another name in the contact. presage currently only fetches the contacts on registering from the "main" signal registration. When a "new" person sends me a message the contact isn't created and if it's created, the message doesn't contain a username. So for creating a new contact the profile has to be fetched. |
I did not think so, but if that is how Signal-Android does it, presage can also do it like that. What made me a bit sceptical was if Signal-Android auto-sets the contact name, why do some contacts of a contact sync not contain the profile name, but instead |
Some time ago they changed the registration process, that it's not possible anymore to set no username. I think the |
If i receive a message from an unknown contact it should create a new contact and fetch the profile for the username.
The text was updated successfully, but these errors were encountered: