matrix-org / matrix-spec

The Matrix protocol specification
Apache License 2.0
197 stars 97 forks source link

Contact List & Renaming Contacts #741

Open trymeouteh opened 3 years ago

trymeouteh commented 3 years ago

To add a layer to Synapse to allow matrix accounts to store a encrypted contacts list of their matrix friends will be handy and here is what can be done with such as feature.

By having contacts, you can set a name you will know to a friend who has an obscure name and matrix address such as cyberguy2001 to something like John Smith that you will know or renaming a room name to something more familiar. Additional contact fields could be added such as email, notes, birthday, anniversary, phone number, etc but I think the bare minimum that is needed is Name, Matrix address/room and groups.

This will mean contacts will be kept more private since using a contacts application on a phone which people use to save their emails and phone numbers can be read by other apps, by having a built in matrix contacts system that does backup to your account and is encrypted will be a more private answer.

clokep commented 3 years ago

This sounds like it is probably a spec issue since it is talking about features that span both homeservers and clients. I've transferred this to the relevant repo.

Thatoo commented 2 years ago

If matrix-server could sync contacts with carddav, it would be really nice.

Mart-Bogdan commented 7 months ago

It would be really useful!

As most other messaging apps allows this (not for rooms but for contacts, but for rooms it would be extra ++).

I even know few persons who are using Emoji or Unicode Space character as display name in Telegram.

I think only Facebook Messenger won't allow one to rename contacts, but IDK, I didn't use it much.

Mart-Bogdan commented 7 months ago

related to https://github.com/matrix-org/matrix-spec-proposals/pull/3015

vranki commented 1 month ago
* Contact list is encrypted, it cannot be stored unencrypted

Just make sure this doesn't require full E2EE capability. Users and clients must have option not to use E2EE if they don't want to. Metadata of which users are interacted with is anyway available to server.