(whoops - accidentally sent to Max's private email rather than to the list.)
Retroshare doesn't really look like the kind of protocol I'm interested in - getting everything through XMPP is my main goal these days although IRC is stubborn, as always. If telepathy doesn't allow you to model (your?) IM protocol directly, probably best to chat with the telepathy developers directly about it. They've been quite forthcoming on the few contacts I've had with them. Actual nuts-and-bolts-and-guts of it is something I've not touched much - yet. I've got a CM proxy of some kind to work out and write before I start writing new CMs of my own. I guess what you do depends on what your project actually is. meegomessenger or retroshare-meego? I know which is the one I'd be interested in ;). /Nick On Fri, 2010-03-12 at 00:45 +0100, Max wrote: > Hi thomas > no one could add retroshare to telepathy right now. > maybe you can do it? > Regards Max > > On Fri, Mar 12, 2010 at 12:45 AM, Nicholas Thomas <[email protected]> wrote: > > On Thu, 2010-03-11 at 23:52 +0100, Max wrote: > >> Hi > >> is anyone interested to join us creating a mobile messenger c++ Qt > >> http://sourceforge.net/projects/meegomessenger/ > >> > > > > Personally, I'd rather see Maemo's use of telepathy continue into MeeGo. > > If you're going to write a messenger, why not get it to use telepathy > > and write a telepathy connection manager for this retroshare thing if > > you need it? > > > > I am quite interested in a 'proper' IM client for MeeGo - with file > > sharing and chatroom (XMPP MUC, IRC) capabilities embedded. I'm not sure > > if a project tied to a particular network is the way forward there... > > > > /Nick > > > > > > _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
