Jump to content

Pidgin (software): Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Blooooo (talk | contribs)
54 edits
→Features: Working on setting this in prose, perhaps need editing help
Blooooo (talk | contribs)
54 edits
m Minor moving criticism and de-prosifieng
Line 24: Line 24:


{{Prose|date=January 2008}}
{{Prose|date=January 2008}}
Pidgin features most of the standard tools for an instant messaging client, such as a [[contact list|Contact list]], tabbed conversations, file transfer on supported protocols, and conversation and chat logging.
Pidgin features most of the standard tools for an instant messaging client, such as tabbed conversations, a [[contact list|Contact list]], file transfer on supported protocols, and conversation and chat logging.

⚫
Tabbed conversations is an optional feature on Pidgin. They work the way tabs do, you know? Someone should edit this better than me. The IM window consists of the message window, formatting tools, and an edit box. Recent controversy has centered on the fact that version 2.4 lacks the ability to manually resize the text input box of conversations. It automatically resizes to either 2,3, or 4 lines depending on how much is typed. Developers are working on a better solution but are reluctant to bring back manual resizing at this time.<ref>{{cite web|url=http://developer.pidgin.im/ticket/4986 |title=Text box resizing issue |accessdate=2008-03-08}}</ref>


Contacts (usually known as "Buddies") are added by the "Buddy List" window or by the IM window. As a client that supports IRC and other chat programs, it can also add different IRC channels and IM Chats. Contacts with multiple protocols can be grouped into one single contact instead of managing multiple protocols and contacts can be given aliases as well or placed into groups.
Contacts (usually known as "Buddies") are added by the "Buddy List" window or by the IM window. As a client that supports IRC and other chat programs, it can also add different IRC channels and IM Chats. Contacts with multiple protocols can be grouped into one single contact instead of managing multiple protocols and contacts can be given aliases as well or placed into groups.


To reach users as they log on or a status change occurs (such as moving from "Away" to "Avaliable"), Pidgin supports on-action automated scripts called ''Buddy Pounces'' to automatically reach the user in customizable ways.
To reach users as they log on or a status change occurs (such as moving from "Away" to "Avaliable"), Pidgin supports on-action automated scripts called ''Buddy Pounces'' to automatically reach the user in customizable ways.

⚫
Pidgin well supports file transfers, with the ability to pause, resume, and cancel transfers and observe multiple transfers in a separate window. However, they are used through the .NET protocol, and therefore are slow, as data is routed through MSN servers to the receiver, instead of utilizing a faster peer-to-peer functionality.<ref>{{cite web |url=http://developer.pidgin.im/wiki/Protocol%20Specific%20Questions#Whyarefiletransferssoslow |title=Protocol Specific Questions — FAQ — Pidgin |accessdate=2007-05-12}}</ref> A [[Google Summer of Code]] project aimed to add peer-to-peer functionality in 2007.<ref>{{cite web |url=http://developer.pidgin.im/wiki/UpdateMsnSupport |title=UpdateMsnSupport — Pidgin — Trac |accessdate=2007-07-18}}</ref>


*Notification pop-ups available through the [http://gaim.guifications.org/ Guifications] plug-in and ''libnotify'' plug-in
*Notification pop-ups available through the [http://gaim.guifications.org/ Guifications] plug-in and ''libnotify'' plug-in
Line 79: Line 83:
*Due to the Pidgin project's use of reverse-engineering to interact with some [[proprietary software|proprietary]] protocols, there are disparities in functionality between official clients and the Pidgin client.
*Due to the Pidgin project's use of reverse-engineering to interact with some [[proprietary software|proprietary]] protocols, there are disparities in functionality between official clients and the Pidgin client.



⚫
*File transfers through the .NET protocol are slow, as data is routed through MSN servers to the receiver, instead of utilizing a faster peer-to-peer functionality.<ref>{{cite web |url=http://developer.pidgin.im/wiki/Protocol%20Specific%20Questions#Whyarefiletransferssoslow |title=Protocol Specific Questions — FAQ — Pidgin |accessdate=2007-05-12}}</ref> A [[Google Summer of Code]] project aimed to add peer-to-peer functionality in 2007.<ref>{{cite web |url=http://developer.pidgin.im/wiki/UpdateMsnSupport |title=UpdateMsnSupport — Pidgin — Trac |accessdate=2007-07-18}}</ref>


*Like similar programs, saved [[password]]s are stored in a [[cleartext]] file. This password file is readable by anyone who uses the same user account on that computer, or to anyone who has access to the administrative account. (The developers' stated reason for this is that saved passwords must be stored in a way that is readily accessible to the program. If they were encrypted by the application, decryption by third parties would require only access to the application's source code, including any encryption [[key (cryptography)|key]]. The developers believe that saving the passwords in a cleartext format avoids a false illusion of security.<ref>{{cite web |url=http://developer.pidgin.im/wiki/PlainTextPasswords |title=Plain Text Passwords — Pidgin |accessdate=2007-05-18}}</ref>)
*Like similar programs, saved [[password]]s are stored in a [[cleartext]] file. This password file is readable by anyone who uses the same user account on that computer, or to anyone who has access to the administrative account. (The developers' stated reason for this is that saved passwords must be stored in a way that is readily accessible to the program. If they were encrypted by the application, decryption by third parties would require only access to the application's source code, including any encryption [[key (cryptography)|key]]. The developers believe that saving the passwords in a cleartext format avoids a false illusion of security.<ref>{{cite web |url=http://developer.pidgin.im/wiki/PlainTextPasswords |title=Plain Text Passwords — Pidgin |accessdate=2007-05-18}}</ref>)
Line 88: Line 92:


*Pidgin does not currently support "skins", though its "sister project" [[Adium]] does.
*Pidgin does not currently support "skins", though its "sister project" [[Adium]] does.

⚫
*Recent controversy has centered on the fact that version 2.4 lacks the ability to manually resize the text input box of conversations. It automatically resizes to either 2,3, or 4 lines depending on how much is typed. Developers are working on a better solution but are reluctant to bring back manual resizing at this time.<ref>{{cite web|url=http://developer.pidgin.im/ticket/4986 |title=Text box resizing issue |accessdate=2008-03-08}}</ref>


== Related software ==
== Related software ==

Revision as of 17:33, 20 March 2008

Pidgin
Developer(s)Sean Egan et al.
Initial release1999
Preview releaseNone [±]
Repository
Written inC, C#, Perl, Python, Tcl
PlatformCross-platform
Available inMultiple
TypeInstant messaging client
LicenseGNU General Public License
Websitewww.pidgin.im

Pidgin (formerly named Gaim) is a multi-platform instant messaging client. The software supports many commonly used instant messaging protocols, allowing the user to log into various different services from one application.

The number of Pidgin users was estimated to be over 3 million in 2007.[1] Released under the terms of the GNU General Public License, Pidgin is free software.

Features

Pidgin has support for multiple operating systems, including Windows as well as many Unix-like systems such as Linux, BSD, and AmigaOS (through the X11 engine). It is notable for its support for multiple instant messaging protocols. It has built-in support for NSS, offering client-to-server message encryption for protocols that support it. The program is extendable through plugins, including "Off-the-Record Messaging" and Pidgin encryption, providing end-to-end message encryption.

Pidgin features most of the standard tools for an instant messaging client, such as tabbed conversations, a Contact list, file transfer on supported protocols, and conversation and chat logging.

Tabbed conversations is an optional feature on Pidgin. They work the way tabs do, you know? Someone should edit this better than me. The IM window consists of the message window, formatting tools, and an edit box. Recent controversy has centered on the fact that version 2.4 lacks the ability to manually resize the text input box of conversations. It automatically resizes to either 2,3, or 4 lines depending on how much is typed. Developers are working on a better solution but are reluctant to bring back manual resizing at this time.[2]

Contacts (usually known as "Buddies") are added by the "Buddy List" window or by the IM window. As a client that supports IRC and other chat programs, it can also add different IRC channels and IM Chats. Contacts with multiple protocols can be grouped into one single contact instead of managing multiple protocols and contacts can be given aliases as well or placed into groups.

To reach users as they log on or a status change occurs (such as moving from "Away" to "Avaliable"), Pidgin supports on-action automated scripts called Buddy Pounces to automatically reach the user in customizable ways.

Pidgin well supports file transfers, with the ability to pause, resume, and cancel transfers and observe multiple transfers in a separate window. However, they are used through the .NET protocol, and therefore are slow, as data is routed through MSN servers to the receiver, instead of utilizing a faster peer-to-peer functionality.[3] A Google Summer of Code project aimed to add peer-to-peer functionality in 2007.[4]

Supported protocols

Encryption

Messages can be encrypted using an Off-the-Record Messaging (OTR) plug-in.[9]

There is also a Pidgin-Encryption plugin, which uses RSA Encryption.[10]

History

The program was originally written in or before 1999 by Mark Spencer, an Auburn University sophomore, as an emulation of AOL's IM program AOL Instant Messenger on Linux using the GTK+ toolkit.[11] It was named GAIM (GTK+ AOL Instant Messenger) accordingly. The emulation was not based on reverse engineering, but instead relied on information about the protocol that AOL had published on the web; development was also assisted by some of AOL's technical staff.[12][11] Support for other IM protocols was added soon.[11]

Naming dispute

Gaim 2.0.0 beta 6 running under GNOME 2.16.0

In response to pressure from AOL, the program was renamed to the acronymous-but-lowercase Gaim. As AOL Instant Messenger gained popularity, AOL trademarked its acronym, "AIM", leading to a lengthy legal struggle with the program's creators, who kept the matter largely secret.

On April 6 2007, the project development team announced the results of their settlement with AOL, which included a series of name changes: Gaim became Pidgin, libgaim became libpurple, and gaim-text became finch.[13] The name Pidgin was chosen in reference to the term "pidgin", which describes communication between people who do not share a common language.[14] It also harks back to its original name, as the pigeon bird is a popular game bird and messenger. The name "purple" refers to "prpl", the internal libgaim name for an IM protocol plugin.

Due to the legal issues, version 2.0 of the software was frozen in beta stages. Following the settlement, it was announced that the first official release of Pidgin 2.0.0 was hoped to occur during the two weeks from April 8, 2007.[15] However, Pidgin 2.0 did not release as scheduled, and on April 22, 2007, Pidgin developers announced the reason for the delay having to do with the preferences folder ".gaim".[16]

Pidgin 2.0.0 was released on May 3, 2007. This was the first release version to be called Pidgin, and contained a completely new graphics design.[17]

Criticisms and current deficiencies

  • Due to the Pidgin project's use of reverse-engineering to interact with some proprietary protocols, there are disparities in functionality between official clients and the Pidgin client.


  • Like similar programs, saved passwords are stored in a cleartext file. This password file is readable by anyone who uses the same user account on that computer, or to anyone who has access to the administrative account. (The developers' stated reason for this is that saved passwords must be stored in a way that is readily accessible to the program. If they were encrypted by the application, decryption by third parties would require only access to the application's source code, including any encryption key. The developers believe that saving the passwords in a cleartext format avoids a false illusion of security.[18])
  • Pidgin does not currently support video and audio conferencing, nor any form of audio/video communication.[19] The developers plan on implementing multimedia messaging in the future.[20][21] Parallel development was planned with the uncompleted gaim-vv library but the project has been declared dead by the developers.[22]
  • The GTK+ build packaged with Pidgin has been known to cause errors with GIMP in Windows.[23] This was, however, determined to be a bug in GIMP, which made improper assumptions about configuration files.[24]
  • Pidgin does not currently support "skins", though its "sister project" Adium does.
  • Adium and Proteus are instant messaging clients for Mac OS X that support multiple protocols through libpurple.
  • ScatterChat is an encrypted instant messaging client based on Pidgin.
  • Meebo is a multi-protocol web-based instant messaging client that uses libpurple.[25]
  • OpenWengo is a hybrid SIP-based VoIP and Instant messaging client which uses libpurple for messaging support.
  • PhoneGaim is a SIP-based Voice over IP communications client; it is based on Pidgin and thus is also available under the GPL.

See also

References

  1. ^ Luke Schierer discusses Pidgin, Open source and life. Interview by PC World Australia, 10 October 2007
  2. ^ "Text box resizing issue". Retrieved 2008-03-08.
  3. ^ "Protocol Specific Questions — FAQ — Pidgin". Retrieved 2007-05-12.
  4. ^ "UpdateMsnSupport — Pidgin — Trac". Retrieved 2007-07-18.
  5. ^ "About Pidgin". Retrieved 2007-05-12.
  6. ^ Pidgin Tlen – Download of the Tlen.pl plugin for Pidgin
  7. ^ Gfire – Download of the Gfire plugin for Pidgin
  8. ^ Skype API Plugin – Download of the Skype API plugin for Pidgin
  9. ^ Off-the-Record Messaging – Download of the OTR-Plug-in for Pidgin
  10. ^ Pidgin Encryption
  11. ^ a b c Matthew Herper: Better Instant Messaging Through Linux Forbes.com, , 16 July 2002
  12. ^ GAIM: GTK+ America OnLine Instant Messenger Original project home page as February 10, 1999 (copy at the Internet Archive)
  13. ^ "SourceForge.net: gaim-i18n". Retrieved 2007-04-11. "Pidgin" for gaim itself, "libpurple" for libgaim, …and "finch" for gaim-text.
  14. ^ "Important and Long Delayed News". Retrieved 2007-05-01.
  15. ^ "News — Pidgin". Retrieved 2007-04-11. Now that the settlement is signed, we hope to have the final Pidgin 2.0.0 release late this week or early next.
  16. ^ "Working towards 2.0.0". Retrieved 2007-04-22.
  17. ^ "Identity vs. Account Orientation". Retrieved 2007-05-01.
  18. ^ "Plain Text Passwords — Pidgin". Retrieved 2007-05-18.
  19. ^ "Pidgin 2.0.1 Review". Retrieved 2007-06-14.
  20. ^ "FAQ — Pidgin". Retrieved 2008-03-02.
  21. ^ "Sean Egan tells here that vv support won't necessarily come with 3.0.0". Retrieved 2007-05-18.
  22. ^ "Peter Lawler declares that gaim-vv is "completely dead now."". Retrieved 2008-01-25.
  23. ^ "Bug 314529 (on BugZilla)". Retrieved 2007-04-11.
  24. ^ "Bug 458457 (on BugZilla)". Retrieved 2007-08-15.
  25. ^ Blog posting about the beginnings of Meebo
Wikimedia Commons has media related to Pidgin (instant messaging client).
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=Pidgin_(software)&oldid=199632654"