Voice and Video for Pidgin
Add support for voice and video chat in Pidgin. It must work using the MSN, XMPP, SIP, AIM and Yahoo messenger protocols, and it must work at least as fully and reliably as the most current proprietary clients.
Sponsor This Project
Sponsor This Project
You currently need to log in to sponsor a project. We apologize for the inconvenience.
Note: You can propose changes using the forum below.
Add support for voice and video chat in Pidgin. It must work using the MSN, XMPP, SIP, AIM and Yahoo messenger protocols, and it must work at least as fully and reliably as the most current proprietary clients.
The deliverable should be as patches against the latest release versions of Pidgin and libpurple, whatever they happen to be at the time. And the separation of code between Pidgin and libpurple should be done cleanly, in a way that the official Pidgin developers would reasonably expect.
The following is a quote from the relevant section of Pidgin's FAQ:
"We aim to have an abstracted, protocol-agnostic API for voice and video, which makes the task harder. Also adding to the difficulty is that now that we have a completely split core (libpurple) and UI (Pidgin and Finch), we refuse to take a step backward and violate this split. The protocol plugins can NOT have any code in them that is UI-dependent, or we break the libpurple/UI split. This imposes additional restrictions that make it a very painstaking process to implement voice and video correctly."
Accordingly, part of this task is to provide a design for a voice and video API (as an extension of libpurple?) which the official Pidgin developers could reasonably be expected to approve.
As it stands, the Pidgin developers have provided no target date for the availability of this feature. (According to the FAQ: "It could be tomorrow, or it could be in 2099.") Hopefully this project will help to speed things up.
The deliverable should be as patches against the latest release versions of Pidgin and libpurple, whatever they happen to be at the time. And the separation of code between Pidgin and libpurple should be done cleanly, in a way that the official Pidgin developers would reasonably expect.
The following is a quote from the relevant section of Pidgin's FAQ:
"We aim to have an abstracted, protocol-agnostic API for voice and video, which makes the task harder. Also adding to the difficulty is that now that we have a completely split core (libpurple) and UI (Pidgin and Finch), we refuse to take a step backward and violate this split. The protocol plugins can NOT have any code in them that is UI-dependent, or we break the libpurple/UI split. This imposes additional restrictions that make it a very painstaking process to implement voice and video correctly."
Accordingly, part of this task is to provide a design for a voice and video API (as an extension of libpurple?) which the official Pidgin developers could reasonably be expected to approve.
As it stands, the Pidgin developers have provided no target date for the availability of this feature. (According to the FAQ: "It could be tomorrow, or it could be in 2099.") Hopefully this project will help to speed things up.
Change History:
- 2009-08-31 15:48 EDT [ACCEPTED] SIP support?
- 2008-07-27 13:29 EDT [ACCEPTED] More protocols
