Design and feature suggestions

[Christian Wisner-Carlson]

Dear Dedicated Developers,
I have, over time, accrued various ideas for the improvement of Pidgin.
As I am not a coder, I feel that I should submit my ideas for
consideration. Here they are:

*Split Pidgin and Finch from libpurple completely, so that the backend
and frontend may run on different machines, allowing multiple frontends.
This would allow people to put libpurple on their servers, leave their
accounts always signed on, and be able to roam between their computers
seamlessly. 

*MySQL/SQLite integration: The pidgin buddylist format is slow,
disorganized, and easily corruptible (I have to delete it and rename my
contacts every once in awhile). Allowing libpurple to store buddy
information, account information (encrypted hopefully), logs,
configuration, etc in a database would make it much easier to add
features as well, eliminating the need for specific file access. Plugins
could also store information in the database. This would also provide an
incentive for enterprise use, when combined with the previous
suggestion. 

I've had many other ideas that I cannot recall at the moment. I'll try
to send them when I do. Please provide me feedback on these ideas if you
have the time.

Thanks, 
Christian Wisner-Carlson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://pidgin.im/pipermail/devel/attachments/20080309/94e1ec80/attachment.sig>