<mattr|laptop> DaSkreech: what do you mean?
<DaSkreech> The mailing list at least I guess
<DaSkreech> I just want to know how the stack works
<DaSkreech> Telepathy -> Decibel -> Apps?
<mattr|laptop> we don't know yet
<DaSkreech> mattr|laptop: was it you asking the other day on the mailing list?
<mattr|laptop> DaSkreech: yeah
<DaSkreech> No response I see :)
<mattr|laptop> DaSkreech: it's more like Telepathy -> Tapioca -> Decibel -> Apps
<DaSkreech> Really? I thought that Telepathy == tapioca
<mattr|laptop> DaSkreech: no, i've gotten a response i think
<DaSkreech> On the list?
<mattr|laptop> DaSkreech: afaik
* DaSkreech goes back to browse the digests
<DaSkreech> Weren't the Tapioca people throwing in lot with Telepathy?
<mattr|laptop> yes, tapioca is implementing the telepathy spec
<DaSkreech> But they are still two stand alone projects?
<mattr|laptop> i'm not completely sure
<DaSkreech> Ha :-) Ok I'll post and ask for a chart
<DaSkreech> This is all selfishly routed back to me wanting emoticons per protocol btw
<andrunko> there is no telepathy <-> tapioca difference, tapioca is just a layer on top of telepathy, a bunch of libraries to use the telepathy spec
<andrunko> and some cms
<CIA-4> rjarosz * r579845 kopete/ (20 files in 3 dirs):
<CIA-4> Add remaining user info items to userinfo dialog.
<CIA-4> Update list of languages and countries to ICQ 5.1 version.
<andrunko> and there is no tapioca using telepathy, as tapioca uses dbus directly to implement the telepathy spec
<andrunko> so if you are using tapioca, you are just using dbus/qt, dbus/glib to talk to cms implementing the telepathy spec, and tapioca intends to make things easier for developers
<andrunko> i think i need to update the tapioca wiki page