KTp/Components/Buddy List

Braindump

• use nepomuk for displaying everything.

• Nepomuk meta-contacts

Code

Skeleton Implementation, that displays a rough buddy list, but doesn't do much else can be found at:

svn://svn.kde.org/home/kde/trunk/playground/network/telepathy-contactlist

Design

• telepathy-integration-daemon pushes contacts into nepomuk and keeps them in sync with the servers through telepathy. It will get all contacts and their details when you initially connect to a account, and then it will (check periodically?) make sure that they stay up to date in nepomuk when they change on the server. It will also keep all contacts' presence set in nepomuk.

• buddy list is populated entirely from nepomuk. it only talks to Telepathy when requesting a channel to someone (ie you double click on them to chat or something). Even presence information comes from nepomuk. Metacontacts are also implemented in Nepomuk.

Why this way? Basically, we've tried every other possibility that we can think of (we being George and the Nepomuk folks mainly in this case) and all the other ideas fall apart at some point, whereas this one seems to be OK so far.