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
Currently Nio uses the contact information received from the Matrix server which prevents the user from using custom names and contact images for a given chat. Also, in cases of bridged accounts (i.e Telegram or Signal) appends a "(Telegram)" suffix to the accounts name. This pollutes the contact list with unnecessary information.
One thing to keep in mind when such feature is implemented is how to handle a single address book contact being assigned several Matrix handles (in case of bridged accounts).
The text was updated successfully, but these errors were encountered:
Currently Nio uses the contact information received from the Matrix server which prevents the user from using custom names and contact images for a given chat. Also, in cases of bridged accounts (i.e Telegram or Signal) appends a "(Telegram)" suffix to the accounts name. This pollutes the contact list with unnecessary information.
One thing to keep in mind when such feature is implemented is how to handle a single address book contact being assigned several Matrix handles (in case of bridged accounts).
The text was updated successfully, but these errors were encountered: