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

system messages referring to contacts should be tappable #6702

Closed
r10s opened this issue Mar 23, 2025 · 0 comments · Fixed by #6714
Closed

system messages referring to contacts should be tappable #6702

r10s opened this issue Mar 23, 2025 · 0 comments · Fixed by #6714
Assignees

Comments

@r10s
Copy link
Contributor

r10s commented Mar 23, 2025

currently, system messages show name+email address in their text, eg. sth. as
Member Alice Atkinson ([email protected]) added by Bob Butler ([email protected])

this not only makes the message hard to read - it could be just ...
Member Alice Atkinson added by Bob Butler
... - the email address in general is not the only criterion to identify a person, and not the most important one. chat history and shared chats, acceptance etc. are at least equally important.

therefore, we should change the strings in core - and at the same time change UI to open the contact profile when tapping the system message:

  • for "Group image changed by ..." and Group name changed by ...", "Disapparing messages changed ..." the contact_id is from_id
  • for "Member ... added by ..." and "Member ... removed by ...", we probably need a new API, as the added/removed member is of major interest (from the profile on can easily check "introduced by" and see who added the member)

finally, to close this issue, the correct info type needs to be set also for received info messages and the additional info types need to be documented (currently, only few info types are used externally)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant