Bug 302513 - Show which service is being used for the contact in the active chat window - document how on userbase
Summary: Show which service is being used for the contact in the active chat window -...
Status: RESOLVED FIXED
Alias: None
Product: telepathy
Classification: Frameworks and Libraries
Component: documentation (show other bugs)
Version: 0.4.0
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: Future
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-25 14:56 UTC by Vangelis
Modified: 2014-04-02 20:12 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vangelis 2012-06-25 14:56:22 UTC
Some of my contacts are using more than one instant messaging services like me. Some others use only one, but I do not really remember which one.
When any of them contact me, I don't know how have they reached me (using google? using MSN? using another xmpp private server?).

This is important to know as some services might be used for different purpose, offering more or less functionality.
A private xmpp server for example might be used for a company, so the chat style must be more formal.

Reproducible: Always



Expected Results:  
Show which service is being used for the contact in the active chat window.
Maybe some more information by clicking on a "More details for this contact" button.
Comment 1 Martin Klapetek 2012-06-25 15:04:18 UTC
The 0.4 release features custom toolbar icon, which you can add (right click on the toolbar in text-ui -> Configure toolbars and add 'Account Icon'. I agree we can improve this however ;)
Comment 2 Vangelis 2012-06-25 15:18:19 UTC
(In reply to comment #1)
> The 0.4 release features custom toolbar icon, which you can add (right click
> on the toolbar in text-ui -> Configure toolbars and add 'Account Icon'. I
> agree we can improve this however ;)

Thanks :)
This helped
Comment 3 David Edmundson 2012-06-26 14:03:21 UTC
This needs documenting on Userbase. Once that's done this bug can be closed.