Problem 2 doesn't seem to be a problem of telepathy, as it can handle concurrent connections just fine. It would be nice if Sugar could do the same. This would mean problem 1 stops being important. If there is some limitation within sugar that forces it to use just one connection, a dialogue asking for a changeover to the other protocol seems like the only thing I can think of. kind regards, David Van Assche <div class="gmail_quote">On Wed, Mar 3, 2010 at 7:07 PM, Tomeu Vizoso <<a href="mailto:tomeu@tomeuvizoso.net">tomeu@tomeuvizoso.net</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi all, as part of the effort to make Sugar a more "normal" Telepathy client, Sugar should become able to deal with more than one IM account active concurrently. Up to now, Sugar's Presence Service will enable the Avahi-based one, then disable it if a connection to a Jabber server was successful. This will make easier for Sugar users to be able to interact with people using GNOME or other desktops. This raises two problems: - the same people could appear 2 times. We can fix it up to some point by announcing our JID in Avahi, then merging contacts in the UI layer. - we cannot invite a link-local contact to an activity being shared through a jabber server, nor a jabber contact to an activity shared through another server (without federation). The first is not such a big deal, but the second will require careful thought about how we expose this limitation to users. Any ideas? Thanks, Tomeu _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </blockquote></div>