Should Gwibber have plugins?

[crashsystems]

I've found that one of the great things about microblogging services is all of the third-party services designed to be used with microblogging, such as twitpic, tinyurl, etc. Since I just switched to Gwibber (which is awesome, btw!), I was wondering if it might be a good idea to add support for any of these services. However, the problem is that there are bunch of them, and they tend to appear, grow in popularity or disappear rather quickly. Furthermore, there is probably no single service that is used by the majority of Gwibber users.

I think the solution could be a plugin feature. At startup, Gwibber could check the $HOME/.gwibber/plugins directory for Python modules to load. The client could then have a set of API that plugin developers could use to interface with Gwibber.

Being somewhat new to Python, I'm not quite ready to work on the Gwibber code itself. However, I would be very interested in writing plugins for Gwibber if such a feature was implemented.

[Ryan Paul (segphault)]

I'm not convinced that this is a good idea. Creating plugin hooks would be difficult and it would be hard to guarantee API stability for plugin developers.