Instant messaging offers real-time communication and allows easy collaboration, which might be considered more akin to genuine conversation than email's "letter" format. In contrast to e-mail, the parties know whether the peer is available. Most systems allow the user to set an online status or away message so peers are notified when the user is available, busy, or away from the computer. On the other hand, people are not forced to reply immediately to incoming messages. For this reason, some people consider communication via instant messaging to be less intrusive than communication via phone. However, some systems allow the sending of messages to people not currently logged on (offline messages), thus removing much of the difference between IM and email.
Instant messaging allows instantaneous communication between a number of parties simultaneously, by transmitting information quickly and efficiently, featuring immediate receipt of acknowledgment or reply. In certain cases IM involves additional features, which make it even more popular, i.e. to see the other party, e.g. by using web-cams, or to talk directly for free over the internet.
It is possible to save a conversation for later reference. Instant messages are typically logged in a local message history which closes the gap to the persistent nature of e-mails and facilitates quick exchange of information like URLs or document snippets (which can be unwieldy when communicated via telephone).
In early instant messaging programs each character appeared when it was typed. The UNIX "talk" command shown in these screenshots was popular in the 1980s and early 1990s.
Instant messaging actually predates the internet, first appearing on multi-user operating systems like CTSS and Multics in the mid-1960s. Initially, many of these systems, such as CTSS'.SAVED, were used as notification systems for services like printing, but quickly were used to facilitate communication with other users logged in to the same machine. As networks developed, the protocols spread with the networks. Some of these used a peer-to-peer protocol (eg talk, ntalk and ytalk), while others required peers to connect to a server (see talker and IRC)
In the last half of the 1980s and into the early 1990s, the Quantum Link online service for Commodore 64 computers offered user-to-user messages between currently connected customers which they called "On-Line Messages" (or OLM for short). Quantum Link's better known later incarnation, America Online, offers a similar product under the name "AOL Instant Messages" (AIM). While the Quantum Link service ran on a Commodore 64, using only the Commodore's PETSCII text-graphics, the screen was visually divided up into sections and OLMs would appear as a yellow bar saying "Message From:" and the name of the sender along with the message across the top of whatever the user was already doing, and presented a list of options for responding. As such, it could be considered a sort of GUI, albeit much more primitive than the later Unix, Windows and Macintosh based GUI IM programs. OLMs were what Q-Link called "Plus Services" meaning they charged an extra per-minute fee on top of the monthly Q-Link access costs.
Modern, Internet-wide, GUI-based messaging clients, as they are known today, began to take off in the mid 1990s with ICQ (1996) being the first, followed by AOL Instant Messenger (AOL Instant Messenger, 1997). AOL later acquired Mirabilis, the creators of ICQ. A few years later ICQ (by now owned by AOL) was awarded two patents for instant messaging by the U.S. patent office. Meanwhile, other companies developed their own applications (Excite, MSN, Ubique, and Yahoo), each with its own proprietary protocoland client; users therefore had to run multiple client applications if they wished to use more than one of these networks. In 1998 IBM released IBM Lotus Sametime, a product based on technology acquired when IBM bought Haifa-based Ubique and Lexington-based Databeam.
In 2000, an open source application and open standards-based protocol called Jabber was launched. Jabber servers could act as gateways to other IM protocols, reducing the need to run multiple clients. Modern multi-protocol clients such as Pidgin, Trillian, Adium and Miranda can use any of the popular IM protocols without the need for a server gateway. IBM Lotus Sametime's November 2007 release added server-gateway support for XMPP.
Recently, many instant messaging services have begun to offer video conferencing features, Voice Over IP (VoIP) and web conferencing services. Web conferencing services integrate both video conferencing and instant messaging capabilities. Some newer instant messaging companies are offering desktop sharing, IP radio, and IPTV to the voice and video features.
The term "instant messenger" is a service mark of Time Warner and may not be used in software not affiliated with AOL in the United States. For this reason, the instant messaging client formerly known as Gaim or gaim announced in April 2007 that they would be renamed "Pidgin".
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 Leveraging Extensions), 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 each continues to use its own proprietary protocol.
However, while discussions at IETF were stalled, Reuters head of collaboration services, David Gurle (the founder of Microsoft's Real Time Communication and Collaboration business), surprised everybody by signing the first inter-service provider connectivity agreement on September 2003. This historic agreement enabled AIM, ICQ and MSN Messenger users to talk with Reuters Messaging counterparts and vice-versa against an access fee. Following this breakthrough agreement between networks Microsoft, Yahoo! and AOL came to a deal where Microsoft's Live Communication Server 2005 (which is interestingly also used by Reuters for its Reuters Messaging service) users would also have the possibility to talk to public instant messaging users. This deal settled once for all the protocol for interconnectivity in the market as SIP/SIMPLE and established a connectivity fee for accessing public instant messaging clouds. Separately, on October 13, 2005 Microsoft and Yahoo! announced that by (the Northern Hemisphere) summer of 2006 they would interoperate using SIP/SIMPLE which is followed on December 2005 by the AOL and Google strategic partnership deal where Google Talk users would be able to talk with AIM and ICQ users provided they have an identity at AOL.
There are two ways to combine the many disparate protocols:
One way is to combine the many disparate protocols inside the IM client application.
The other way is to combine the many disparate protocols inside the IM server application. This approach moves the task of communicating to the other services to the server. Clients need not know or care about other IM protocols. For example, LCS 2005 Public IM Connectivity. This approach is popular in Jabber/XMPP servers however the so-called transport projects suffer the same reverse engineering difficulties as any other project involved with closed protocols or formats.
Some approaches, such as that adopted by the Sonork enterprise IM software or the Jabber/XMPP network or Winpopup LAN Messenger, allow organizations to create their own private instant messaging network by enabling them to limit access to the server (often with the IM network entirely behind their firewall) and administer user permissions. Other corporate messaging systems allow registered users to also connect from outside the corporation LAN, by using a secure firewall-friendly HTTPS based protocol. Typically, a dedicated corporate IM server has several advantages such as pre-populated contact lists, integrated authentication, and better security and privacy.
Some networks have made changes to prevent them from being utilized by such multi-network IM clients. For example, Trillian had to release several revisions and patches to allow its users to access the MSN, AOL, and Yahoo! networks, after changes were made to these networks. The major IM providers typically cite the need for formal agreements as well as security concerns as reasons for making these changes.