Would a plain-text log file be out of question?

If we separate by account, year and month we will have a small number of files (one for each conversation) in each directory of the tree, it will be very amenable to synchronization between different hosts.

This is pretty much what tp-logger is trying to do. Currently we have soon plan to move to SqLite. Comment, recommendation, interesting links, warning appreciated.

(In reply to comment #2)
> This is pretty much what tp-logger is trying to do. Currently we have soon plan
> to move to SqLite. Comment, recommendation, interesting links, warning
> appreciated.

Right now I'm developing Chato, a program to centralize chat logs incoming from any other program.

You can check its status here: http://code.google.com/p/chato/

It's far from stable, but I try to develop it as much and as good as I can.

(In reply to comment #3)
> (In reply to comment #2)
> > This is pretty much what tp-logger is trying to do. Currently we have soon plan
> > to move to SqLite. Comment, recommendation, interesting links, warning
> > appreciated.
> 
> Right now I'm developing Chato, a program to centralize chat logs incoming from
> any other program.
> 
> You can check its status here: http://code.google.com/p/chato/
> 
> It's far from stable, but I try to develop it as much and as good as I can.

We recently refactored the Telepathy Logger to store more then just text chat. One of our goal is to be able to also store delivery report, audio and video calls (already experimental). Note that we don't work against any other project, we know it's sometimes tricky to track and store Telepathy communication, and would be please if the Logger can help project like yours. This could be accomplish by adding proper plugin system to the Logger, but this is out-of-scope for this bug, which propose enhancing and simplifying the log backend for all of the event types using SQLite.

(In reply to comment #4)
> We recently refactored the Telepathy Logger to store more then just text chat.
> One of our goal is to be able to also store delivery report, audio and video
> calls (already experimental).

Since the beginning this is one of my project's goals too.

It is still not clear, but I think that I will use mime types to be able to store anything.

But for now I'm working first in text logs, because I think it's the best place to start.

> Note that we don't work against any other
> project, we know it's sometimes tricky to track and store Telepathy
> communication, and would be please if the Logger can help project like yours.

I know, and I thank you very much. I am a regular Empathy user, and I would love being able to integrate it with my project.

> This could be accomplish by adding proper plugin system to the Logger, but this
> is out-of-scope for this bug, which propose enhancing and simplifying the log
> backend for all of the event types using SQLite.

My project amis to provide a plugin-based backend, trying to keep the plugin interface as simple as possible, in order to be able to quickly write plugins for Postgres, Mysql, XML, YAML, etc.

The first and default plugin I'm working on is SqLite.

Do you think that the plugin-based logger could be a nice future goal?

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-logger/issues/3.