Bug 26846

Summary:	Contact classification interface
Product:	Telepathy	Reporter:	Mikhail Zabaluev <mikhail.zabaluev>
Component:	tp-spec	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED MOVED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	enhancement
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:
Bug Blocks:	25185

Description Mikhail Zabaluev 2010-03-02 11:35:32 UTC

There are cases in which it is useful to distinguish classes of contacts within one connection for UI purposes.

These include:
- Undisclosed callers in Skype: The handles can be made unique (no idea yet if Skype can reuse the temporary contact IDs), but the ID is meaningless and should not be displayed.
- Undisclosed callers in telephony: coming from a pseudo-contact because it's too weird to have a call with nobody in StreamedMedia (the new Call channel could help with that). The pseudo-contact could be one for all anonymous calls or unique per call, but there is no meaninful handle ID either way, and relying on the CM to supply special case display labels for the UI is bollocks.
- Emergency communications: it's useful to see that a contact resolved by regular mechanisms (e.g. by requesting handle "112") is in fact an emergency contact.

There should be an interface and a contact property to obtain contact classes or "tags".

Comment 1 GitLab Migration User 2019-12-03 20:21:03 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/62.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.