Hi, <div>On 10/19/06, Robert McQueen <<a href="mailto:robert.mcqueen@collabora.co.uk">robert.mcqueen@collabora.co.uk</a>> wrote:<blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex"> We found a thread about chat states in the archives which kinda died out, so I thought I'd resuscitate it. The patch from Luiz [1] looks reasonable - I agree that the original proposal [2] didn't make it clear that the state was per member rather than for the entire channel. Maybe "Member State" would be better interface name? Also, if the interface is not going to be entirely chat-specific, the descriptions should be modified to not refer to "chat", but "channel". </blockquote></div> I agreed with MemberState if we are planning not only use it to chat states, but Im not sure if other channels can and will use it. Another thing is that this interface may confuse the applications, it has to be clear that this is to be use with notifications not presence and others possible states, because that it might be a good idea to add Notification so it becomes MemberStateNotification. Also there is in Channel.Type.Text interface a type called  CHANNEL_TEXT_MESSAGE_TYPE_NOTICE that we could use if we found just chat has this type of notifications. I would like to raise another question here, why telepathy dont use some event mechanism like publish/subscribe/notify that SIP has. I find it much simpler to use and also pretty extensible.