Conversation threading

Last updated
Thread view in a discussion group. At the top level, a discussion with several posts. Next to the subject, number of lines, sender and date is shown for each post. Nntp.jpg
Thread view in a discussion group. At the top level, a discussion with several posts. Next to the subject, number of lines, sender and date is shown for each post.

Conversation threading is a feature used by many email clients, bulletin boards, newsgroups, and Internet forums in which the software aids the user by visually grouping messages with their replies. These groups are called a conversation, topic thread, or simply a thread. A discussion forum, e-mail client or news client is said to have a "conversation view", "threaded topics" or a "threaded mode" if messages can be grouped in this manner. [1]

Contents

Threads can be displayed in a variety of ways. Early messaging systems (and most modern email clients) will automatically include original message text in a reply, making each individual email into its own copy of the entire thread. Software may also arrange threads of messages within lists, such as an email inbox. These arrangements can be hierarchical or nested, arranging messages close to their replies in a tree, or they can be linear or flat, displaying all messages in chronological order regardless of reply relationships.

Conversation threading as a form of interactive journalism became popular on Twitter from around 2016 onward. Authors, such as Eric Garland and Seth Abramson, began to post essays in real time, constructing them as a series of numbered tweets, each limited to 140 or 280 characters. [2]

Mechanism

Internet email clients compliant with the RFC 822 standard (and its successor RFC 5322) add a unique message identifier in the Message-ID: header field of each message, e.g.

Message-ID: <xNCx2XP2qgUc9Qd2uR99iHsiAaJfVoqj91ocj3tdWT@wikimedia.org>

If a user creates message B by replying to message A, the mail client will add the unique message ID of message A in form of the fields

In-Reply-To: <xNCx2XP2qgUc9Qd2uR99iHsiAaJfVoqj91ocj3tdWT@wikimedia.org> References: <xNCx2XP2qgUc9Qd2uR99iHsiAaJfVoqj91ocj3tdWT@wikimedia.org>

to the header of reply B. RFC 5322 defines the following algorithm for populating these fields:

The "In-Reply-To:" field will contain the contents of the "Message-ID:" field of the message to which this one is a reply (the "parent message").  If there is more than one parent message, then the "In-Reply-To:" field will contain the contents of all of the parents' "Message-ID:" fields.  If there is no "Message-ID:" field in any of the parent messages, then the new message will have no "In- Reply-To:" field.  The "References:" field will contain the contents of the parent's "References:" field (if any) followed by the contents of the parent's "Message-ID:" field (if any).  If the parent message does not contain a "References:" field but does have an "In-Reply-To:" field containing a single message identifier, then the "References:" field will contain the contents of the parent's "In-Reply-To:" field followed by the contents of the parent's "Message-ID:" field (if any).  If the parent has none of the "References:", "In-Reply-To:", or "Message-ID:" fields, then the new message will have no "References:" field.

Modern email clients then can use the unique message identifiers found in the RFC 822 Message-ID, In-Reply-To: and References: fields of all received email headers to locate the parent and root message in the hierarchy, reconstruct the chain of reply-to actions that created them, and display them as a discussion tree. The purpose of the References: field is to enable reconstruction of the discussion tree even if some replies in it are missing.

Advantages

Eliminates turn-taking & time constraints

Threaded discussions allow readers to quickly grasp the overall structure of a conversation, isolate specific points of conversations nested within the threads, and as a result, post new messages to extend discussions in any existing thread or sub-thread without time constraints. With linear threads on the other hand, once the topic shifts to a new point of discussion, users are: 1) less inclined to make posts to revisit and expand on earlier points of discussion in order to avoid fragmenting the linear conversation similar to what occurs with turn-taking in face-to-face conversations; and/or 2) obligated to make a motion to stay on topic or move to change the topic of discussion. Given this advantage, threaded discussion is most useful for facilitating extended conversations or debates [3] involving complex multi-step tasks (e.g., identify major premises → challenge veracity → share evidence → question accuracy, validity, or relevance of presented evidence) – as often found in newsgroups and complicated email chains – as opposed to simple single-step tasks (e.g., posting or share answers to a simple question).

Message targeting

Email allows messages to be targeted at particular members of the audience by using the "To" and "CC" lines. However, some message systems do not have this option. As a result, it can be difficult to determine the intended recipient of a particular message. When messages are displayed hierarchically, it is easier to visually identify the author of the previous message.

Eliminating list clutter

It can be difficult to process, analyze, evaluate, synthesize, and integrate important information when viewing large lists of messages. Grouping messages by thread makes the process of reviewing large numbers of messages in context to a given discussion topic more time efficient and with less mental effort, thus making more time and mental resources available to further extend and advance discussions within each individual topic/thread.

In group forums, allowing users to reply to threads will reduce the number of new posts shown in the list.

Some clients allow operations on entire threads of messages. For example, the text-based newsreader nn has a "kill" function which automatically deletes incoming messages based on the rules set up by the user matching the message's subject or author. This can dramatically reduce the number of messages one has to manually check and delete.

Real time feedback

When an author, usually a journalist, posts threads via Twitter, users are able to respond to each 140- or 280-character tweet in the thread, often before the author posts the next message. This allows the author the option of including the feedback as part of subsequent messages. [2]

Disadvantages

Reliability

Accurate threading of messages requires the email software to identify messages that are replies to other messages.

Some algorithms used for this purpose can be unreliable. For example, email clients that use the subject line to relate messages can be fooled by two unrelated messages that happen to have the same subject line. [4]

Modern email clients use unique identifiers in email headers to locate the parent and root message in the hierarchy. When non-compliant clients participate in discussions, they can confuse message threading as it depends on all clients respecting these optional mail standards when composing replies to messages. [5] [6]

Individual message control

Messages within a thread do not always provide the user with the same options as individual messages. For example, it may not be possible to move, star, reply to, archive, or delete individual messages that are contained within a thread.

The lack of individual message control can prevent messaging systems from being used as to-do lists (a common function of email folders). Individual messages that contain information relevant to a to-do item can easily get lost in a long thread of messages.

Parallel Discussions

With conversational threading, it is much easier to reply to individual messages that are not the most recent message in the thread. As a result, multiple threads of discussions often occur in parallel. Following, revisiting, and participating in parallel discussions at the same time can be mentally challenging. Following parallel discussions can be particularly disorienting and can inhibit discussions [7] when discussion threads are not organized in a coherent, conceptual, or logical structure (e.g., threads presenting arguments in support of a given claim under debate intermingled with threads presenting arguments in opposition to the claim).

Temporal Fragmentation

Thread fragmentation can be particularly problematic for systems that allow users to choose different display modes (hierarchical vs. linear). Users of the hierarchical display mode will reply to older messages, confusing users of the linear display mode.

Examples

The following messaging software can group and display messages by thread.

Client-based

Web-based

See also

Related Research Articles

Email Method of exchanging digital messages between people over a network

Electronic mail is a method of exchanging messages ("mail") between people using electronic devices. Email entered limited use in the 1960s, but users could only send to users of the same computer, and some early email systems required the author and the recipient to both be online simultaneously, similar to instant messaging. Ray Tomlinson is credited as the inventor of email; in 1971, he developed the first system able to send mail between users on different hosts across the ARPANET, using the @ sign to link the user name with a destination server. By the mid-1970s, this was the form recognized as email.

In computing, the Internet Message Access Protocol (IMAP) is an Internet standard protocol used by email clients to retrieve email messages from a mail server over a TCP/IP connection. IMAP is defined by RFC 3501.

The Internet Control Message Protocol (ICMP) is a supporting protocol in the Internet protocol suite. It is used by network devices, including routers, to send error messages and operational information indicating success or failure when communicating with another IP address, for example, an error is indicated when a requested service is not available or that a host or router could not be reached. ICMP differs from transport protocols such as TCP and UDP in that it is not typically used to exchange data between systems, nor is it regularly employed by end-user network applications.

Multipurpose Internet Mail Extensions (MIME) is an Internet standard that extends the format of email messages to support text in character sets other than ASCII, as well as attachments of audio, video, images, and application programs. Message bodies may consist of multiple parts, and header information may be specified in non-ASCII character sets. Email messages with MIME formatting are typically transmitted with standard protocols, such as the Simple Mail Transfer Protocol (SMTP), the Post Office Protocol (POP), and the Internet Message Access Protocol (IMAP).

Within the Internet email system, a message transfer agent or mail transfer agent (MTA) or mail relay is software that transfers electronic mail messages from one computer to another using SMTP. The terms mail server, mail exchanger, and MX host are also used in some contexts.

The Simple Mail Transfer Protocol (SMTP) is a communication protocol for electronic mail transmission. As an Internet standard, SMTP was first defined in 1982 by RFC 821, and updated in 2008 by RFC 5321 to Extended SMTP additions, which is the protocol variety in widespread use today. Mail servers and other message transfer agents use SMTP to send and receive mail messages. SMTP servers commonly use the Transmission Control Protocol on port number 25.

Email client

An email client, email reader or more formally mail user agent (MUA) is a computer program used to access and manage a user's email.

Mbox is a generic term for a family of related file formats used for holding collections of email messages, first implemented for Fifth Edition Unix.

Internet forum Online discussion site

An Internet forum, or message board, is an online discussion site where people can hold conversations in the form of posted messages. They differ from chat rooms in that messages are often longer than one line of text, and are at least temporarily archived. Also, depending on the access level of a user or the forum set-up, a posted message might need to be approved by a moderator before it becomes publicly visible.

When a message is replied to in e-mail, Internet forums, or Usenet, the original can often be included, or "quoted", in a variety of different posting styles.

Sender Policy Framework (SPF) is an email authentication method designed to detect forging sender addresses during the delivery of the email. SPF alone, though, is limited to detecting a forged sender claim in the envelope of the email, which is used when the mail gets bounced. Only in combination with DMARC can it be used to detect the forging of the visible sender in emails, a technique often used in phishing and email spam.

Sender ID is an historic anti-spoofing proposal from the former MARID IETF working group that tried to join Sender Policy Framework (SPF) and Caller ID. Sender ID is defined primarily in Experimental RFC 4406, but there are additional parts in RFC 4405, RFC 4407 and RFC 4408.

The following tables compare general and technical features of a number of notable email client programs.

Email authentication, or validation, is a collection of techniques aimed at providing verifiable information about the origin of email messages by validating the domain ownership of any message transfer agents (MTA) who participated in transferring and possibly modifying a message.

Many email clients now offer some support for Unicode. Some clients will automatically choose between a legacy encoding and Unicode depending on the mail's content, either automatically or when the user requests it.

DomainKeys Identified Mail (DKIM) is an email authentication method designed to detect forged sender addresses in emails, a technique often used in phishing and email spam.

DMARC is an email authentication protocol. It is designed to give email domain owners the ability to protect their domain from unauthorized use, commonly known as email spoofing. The purpose and primary outcome of implementing DMARC is to protect a domain from being used in business email compromise attacks, phishing emails, email scams and other cyber threat activities.

Email forwarding generically refers to the operation of re-sending an email message delivered to one email address to one or more different email addresses.

International email arises from the combined provision of internationalized domain names (IDN) and email address internationalization (EAI). The result is email that contains international characters, encoded as UTF-8, in the email header and in supporting mail transfer protocols. The most significant aspect of this is the allowance of email addresses in most of the world's writing systems, at both interface and transport levels.

Gmail interface

The Gmail interface makes Gmail unique amongst webmail systems for several reasons. Most evident to users are its search-oriented features and means of managing e-mail in a "conversation view" that is similar to an Internet forum.

References

  1. Hines, Elise (2017-05-05). "What Is an Email Thread?". Lifewire . Retrieved 2017-12-18.
  2. 1 2 Heffernan, Virginia. "The Rise of the Twitter Thread". POLITICO Magazine. Retrieved 2019-05-07.
  3. Jeong, Allan (2005). "The combined effects of response time and message content on growth patterns of discussion threads in computer-supported collaborative argumentation". International Journal of E-Learning & Distance Education. 19 (1).
  4. Bienvenu, David. "Mail with strict threading like news". Bugzilla. Mozilla. Retrieved 16 May 2017.
  5. Resnick, Peter W. (October 2008). "Internet Message Format". IETF Tools. Archived from the original on 2019-04-24. Retrieved 2019-04-24.
  6. Klyne, Graham; Palme, Jacob (March 2005). "Registration of Mail and MIME Header Fields". IETF Tools. Archived from the original on 2019-04-24. Retrieved 2019-04-24.
  7. Brooks, D. & Jeong, A. (2006). "Brooks, C. D., & Jeong, A. (2006). Effects of pre‐structuring discussion threads on group interaction and group performance in computer‐supported collaborative argumentation". Distance Education. 27 (3): 371–390. CiteSeerX   10.1.1.523.6207 . doi:10.1080/01587910600940448.CS1 maint: multiple names: authors list (link)