A Wisdom Archive on List of Instant Messaging Protocols

Basic general information about the protocols: creator, version, etc. Note 1: In ~usr@a.b.com, the a.b.com part is known as the "hostmask" and can either be the server being connected from or a "cloak" granted by the server administrator; a more realistic example is ~myname@myisp.example.com. The tilde generally indicates that the username provided by the IRC client on signon was not verified with the ident service. Note 2: In usr@a.b.c/home, the ...

Read more here: » Comparison of instant messaging protocols: Encyclopedia II - Comparison of instant messaging protocols - General information

Instant messaging requires the use of a client program that hooks up an instant messaging service and differs from e-mail in that conversations are then able to happen in realtime. Most services offer a presence information feature, indicating whether people on one's list of contacts are currently online and available to chat. This may be called a 'Buddy List'. In early instant messaging programs, each letter appeared as it was typed, and when letters were deleted to correct typos this was also seen in real time. This made it more like a tel ...

Read more here: » Instant messaging: Encyclopedia II - Instant messaging - Overview

Information on what features each of the clients support. Note 1: Plug-in system to add/expand the default features for the application, or protocol. Such as (but not limited to) Trillian chat client - Plugins Note 2: Third party add-ons which are usually not approved by the author of the application and are usually standalone. Such as (but not limited to) AOL Instant messenger - Third-party add-ons Note 4: Proprietary; compatible only to itself. Note 5: ICQ: SSL-encrypt ...

Read more here: » Comparison of instant messengers: Encyclopedia II - Comparison of instant messengers - Features

Information on the instant messaging protocols that each client supports. Note 1: Plugin available [3] Note 2: Plugin available Note 3: Interoperability with proprietary protocols can be achieved using server-side gateways (so-called transports) in Jabber. Note 4: Plugin available, but requires Skype to be installed. Note 5: LAN and chat protocols supported for Miranda include NetSend, WinPopup, Nov ...

Read more here: » Comparison of instant messengers: Encyclopedia II - Comparison of instant messengers - Protocol support

The operating systems the clients can run on without emulation or compatibility layers. Note 1: The Mac OS X version must be self compiled, and will only run with an X server and GTK+ installed. Note 2: Requires ANSI terminal. See e.g. Windows ANSI driver problem on how to load ANSI.SYS. Note 3: MSN Web Messenger can be used with a compatible browser and valid Microsoft Passport Network account. Note 4: Numerous talk/ytal ...

Read more here: » Comparison of instant messengers: Encyclopedia II - Comparison of instant messengers - Operating system support

There have been several attempts to create a unified standard for instant messaging: IETF's SIP (Session Initiation Protocol) and SIMPLE (SIP for Instant Messaging and Presence Leverage), APEX (Application Exchange), Prim (Presence and Instant Messaging Protocol), the open XML-based XMPP (Extensible Messaging and Presence Protocol), more commonly known as Jabber and OMA's (Open Mobile Alliance) IMPS (Instant Messaging and Presence Service) created specifically for mobile devices. Most attempts at creating a unified standard for the major IM providers (AOL, Yahoo! and Microsoft) have failed and ea ...

Read more here: » Instant messaging: Encyclopedia II - Instant messaging - Cooperation