Telepath
Telepath is a temporary name for a small project I am working on. It is going to be a piece of IM middleware that serves an IRC relay for various IM protocols such as ICQ, MSN, Jabber and Yahoo. It uses the telepathy-haze framework as backend. Telepath should in the long run be able to replace BitlBee as an IRC relay.
Short-term goals
-
Get a working event system
The Haze backend uses channels and signals (events) on those channels to transmit information. This is very lowlevel and many objects are received as IDs that can be used to look up the actual object in the D-Bus service or object. We need a more highlevel, wrapped event system that passes around actual objects.
-
Create a pseudo IRC server
In order to serve the IRC relay, we need an IRC server. This server should serve private channels and users. Every user should see the server as though they were alone.
-
Think about design
We basically need three components: The object model/event system taking care of Haze communication, the IRC server and a communication component in between to invert the dependency. The latter would allow us to create XMPP relays or even normal clients (long-term).
Middle-term goals
-
Main-channel chat
Chat with your contacts only using the main channel by addressing them by their screen name.
-
"identify $user $password" along with "identify $password"
When entering the control channel, identify $user $password will log in to the username provided regardless of the IRC nick. identify $password will infer the username from the IRC nick. After identification, the IRC nick can no longer be changed.
-
Custom away messages
I would like the ability to make use of custom status messages as well as standard custom messages.
Long-term goals
-
Protocol-Protocol relay
I wish to have the ability to create conferences with friends over different protocols so that we can communicate all in one place.
-
Filesharing
I wish to have the ability to share files with friends regardless of protocol.
