Play as Webslides

Graham Perrin's List: etiquette on the Internet

Student Guidelines for Electronic Communication: Examples

Part of 'Electronic Communication at Penn State'.

tlt.its.psu.edu/...examples.htm - Preview

thread edit e-mail etiquette subject 2009 on 2009-01-31
- Using the Subject Line Effectively
- Edit the subject line to reflect your contribution to
  a discussion thread
- 5 more annotations...
- - Remember to use your subject line effectively
  - Be constructive
  - explain where you disagree and why
  - Respect others' thoughts and ideas
  - Use the
    "new message" function for new thoughts or ideas
Mailman Email List: User's Guide

Instructions for Email-List Users: UA TCF Depart. & SCMS

www.tcf.ua.edu/Users.html - Preview

e-mail etiquette subject thread edit 2009 on 2009-01-31
- Use descriptive
  subject lines
- replying to a message,
  make sure that the subject line describes your message as specifically
  as possible
E-lists at Cornell: Sending Messages

Part of 'Computing at Cornell'.

www.cit.cornell.edu/...post.html - Preview

e-mail etiquette subject thread edit 2009 on 2009-01-31
- change the digest-related subject line so that it
  reflects the original message's subject line
- Edit the subject line as necessary to be informative,
RFC 1855 - Netiquette Guidelines

Netiquette Guidelines

tools.ietf.org/rfcmarkup - Preview

subject 2009 on 2009-01-31
- INFORMATIONAL
- Request For Comments
- 11 more annotations...
- - October 1995
  - before initiating long
  - good practice to include the word "Long" in the
    subject header so the recipient knows the message will take time
    to read and respond to
  - Over 100 lines is considered "long"
    
    Add Sticky Note
  - Wait overnight to send emotional responses to messages
    
    Add Sticky Note
  - a subject heading which reflects
    the content of the message
  - If you include a signature keep it short. Rule of thumb
    is no longer than 4 lines.
    
    Add Sticky Note
  - Subject lines should follow the conventions of the group
  - Content of a follow-up post should exceed quoted content
  - The moderator may change your subject
    line to have your post conform to a particular thread
    
    Add Sticky Note
  - Don't get involved in flame wars. Neither post nor respond
    to incendiary material.
draft-ietf-usefor-useage-01 - Usenet Best Practice

Usenet Best Practice

tools.ietf.org/...draft-ietf-usefor-useage-01 - Preview

subject 2009 on 2009-01-31
- INTERNET-DRAFT
- Usenet Best Practice
- 17 more annotations...
- - This Internet-Draft will expire in September 2005
  - Subject headers are for humans to read
    
    Add Sticky Note
  - exceedingly complex threads can develop. Therefore, it is essential
    that user agents provide facilities
    
    Add Sticky Note
  - The Subject of the followup
  - users are able to override that default
  - encouraged to do so whenever appropriate
    
    Add Sticky Note
  - "Re" (which is an abbreviation for the Latin "In re",
    meaning "in the matter of", and not an abbreviation of "Reference"
    as is sometimes erroneously supposed) may be understood by English
    speakers
  - its
    use in a newsgroup where articles were customarily written in
    Arabic, or Hindi, or Chinese would be less than helpful
  - RECOMMENDS
    striping away any initial "Re: " when comparing Subjects
  - Software can always recognize
    that such changes have occurred from the References header
  - 3.3.2. Presentation of Articles
    
    3.3.2.1. Threading
    
    Reading agents SHOULD present the articles in each newsgroup in an
    order which ensures that the reader never sees a followup or reply to
    an article unless he has already had an opportunity to read the
    original.
    
    Add Sticky Note
  - a tree in which each article is within a sub-tree headed
    by each article mentioned in its References header, and present
    articles by a depth-first traversal of that tree, sorting the
    siblings within each branch according to their Date headers. This
    method is usually superior
  - the topic of some sub-thread might have diverged
    so far from the original topic of discussion that some
    poster decides to create a totally new Subject
    
    Add Sticky Note
  - that followup, and the whole sub-
    thread which issues from it, will still be presented in the
    midst of the other sub-threads of the original discussion
  - different readers
    can be pleased in different ways, and so it is often the case that
    reading agents provide configurable options to choose between
    several methods
  - all to be considered acceptable
    
    Add Sticky Note
  - it
    SHOULD be possible to filter out all followups to some given article,
    by filtering on the References header
RFC 1036 - Standard for interchange of USENET messages

Standard for Interchange of USENET Messages

tools.ietf.org/rfc1036 - Preview

subject 2009 on 2009-01-31
- Request for Comments
- December 1987
- 7 more annotations...
- - Standard for Interchange of USENET Messages
  - format for the interchange of
    network News messages among USENET hosts
  - tools
    include implementations of both mail and news
  - The "Subject" line (formerly "Title") tells what the message is
    about.
  - suggestive enough of the contents
  - enable a reader to make a decision whether to read the
    message based on the subject alone.
    
    Add Sticky Note
  - the "References" header is to allow messages to be
    grouped into conversations
RFC 5322 - Internet Message Format

Internet Message Format

tools.ietf.org/rfc5322 - Preview

subject 2009 on 2009-01-31 and saved by 4 people
- DRAFT STANDARD
- DRAFT
- 8 more annotations...
- - Request for Comments
  - Obsoletes: 2822
  - October 2008
  - Internet Message Format
  - the
    "References:" field may be used to identify a "thread" of
    conversation
  - Some implementations parse the "References:" field to
    display the "thread of the discussion". These implementations
    assume that each new message is a reply to a single parent and
    hence that they can walk backwards through the "References:" field
    to find the parent of each message listed there
  - The "Subject:" field is the most
    common and contains a short string identifying the topic
  - only one instance of the
    literal string "Re: " ought to be used
RFC 2822 - Internet Message Format

Internet Message Format

tools.ietf.org/rfc2822 - Preview

subject 2009 on 2009-01-31 and saved by 5 people
- PROPOSED STANDARD
- Obsoleted by: 5322
- 11 more annotations...
- - Updated by: 5335, 5336
  - Request for Comments
  - April 2001
  - Internet Message Format
  - "In-Reply-To:" and "References:" fields are used when creating a
    reply to a message
  - the message identifier of the original
    message
  - and the message identifiers of other messages
  - the
    "References:" field may be used to identify a "thread" of
    conversation
  - Some implementations parse the "References:" field to display
    the "thread of the discussion". These implementations assume that
    each new message is a reply to a single parent and hence that they
    can walk backwards through the "References:" field to find the parent
    of each message listed there
  - "Subject:" field is the most
    common and contains a short string identifying the topic of the
    message
  - only one instance of the literal string "Re: " ought
    to be used
draft-ietf-usefor-usepro-13 - Netnews Architecture and Protocols

Netnews Architecture and Protocols

tools.ietf.org/...draft-ietf-usefor-usepro-13 - Preview

subject 2009 on 2009-01-31
- Internet-Draft
- Obsoletes: 1036 (if approved)
- 4 more annotations...
- - Expires: June 17, 2009
  - Netnews Architecture and Protocols
  - The case-sensitive string "Re: " (including
    the space after the colon) MAY be prepended to the content of its
    Subject header field unless it already begins with that string
  - NOTE: Prepending "Re: " serves no protocol function and hence
    is not required, but it is widely expected and not doing so
    would be surprising.
RFC 4096 - Policy-Mandated Labels Such as "Adv:" in Email Subject Headers Considered Ineffective At Best

Policy-Mandated Labels Such as "Adv:" in Email Subject Headers Considered Ineffective At Best

tools.ietf.org/rfc4096 - Preview

2009 on 2009-02-02
- INFORMATIONAL
- Request for Comments
- 4 more annotations...
- - May 2005
  - Policy-Mandated Labels Such as "Adv:" in Email Subject Headers
    
    Considered Ineffective At Best
  - This document makes three recommendations
  - There is widespread skepticism in the technical community that
    labels of any sort will be effective. Such labels should
    probably be avoided as ineffective at best.
Broken threads in Google Mail Beta

Broken conversations/threads are a problem for users of the web interface to Google Mail (Gmail) Beta.

www.diigo.com/...gmail-fail-thread - Preview

bug edit subject thread conversation Gmail Google Mail beta mail.google.com problem 2009 on 2009-01-31
- Broken conversations/threads are a problem for users of the web interface to Google Mail (Gmail) Beta.
Plone: asking for help with errors and problems

Part of Plone documentation.

plone.org/...ask-for-help - Preview

e-mail etiquette plone subject thread edit Gmail Google Mail beta Plone (software) 2009 on 2009-01-31
- Good subject line
  Add Sticky Note
- thoughtful use of keywords/key expressions in a subject line will lead to high ranking and high relevancy in search results
- 6 more annotations...
- - encourage easy reading by concerned individuals/groups
  - A focused subject line can be very useful, especially to future readers
  - a problem topic that originates with one subject may conclude
  - with a subject that bears little or no relationship to the original
  - A well-designed mail/NNTP reader will present a thread in its entirety
  - known problems with Google Mail beta
The Home Education Mailing List

www.madrone.com/...hewelcome.html - Preview

e-mail etiquette subject thread edit on 2008-01-31
- edit the subject line so that it matches the content
  of your post
draft-ietf-usefor-usefor-12 - Netnews Article Format

Netnews Article Format

tools.ietf.org/...draft-ietf-usefor-usefor-12 - Preview

subject 2009 on 2009-01-31
- Internet-Draft
- Obsoletes: 1036 (if approved)
- 5 more annotations...
- - Expires: July 12, 2007
  - Netnews Article Format
  - The Subject header field is the same as that specified in Section
    3.6.5 of [RFC2822]
  - [I-D.ietf-usefor-usepro]
    
    Add Sticky Note
  - [I-D.ietf-usefor-useage]
    
    Add Sticky Note
Gordon's Notes: Gmail feature request: the ability to edit subject lines

Commentary: politics, science, technology and humanity.

notes.kateva.org/...e-request-ability-to-edit.html - Preview

e-mail etiquette subject thread edit 2009 on 2009-01-31
- Gmail Suggestion
  Add Sticky Note
- Editing subject lines allows one to both add terms important in search, and increases the value of search results. Since results always display subject lines, good subject lines make search returns more useful.
- 1 more annotations...
- - I depend on this feature
organizing discussion threads

An October 2007 post in Google Groups Help Forum.

groups.google.com/...8239487f748f7b25 - Preview

edit subject 2009 on 2009-01-31
- altering one comma or period will create
  a new thread
  Add Sticky Note
Netiquette Home Page -- A Service of Albion.com

www.albion.com/...index.html - Preview

etiquette 2009 on 2009-01-31 and saved by 18 people
freenode philosophy: catalysts

freenode.net/catalysts.shtml - Preview

2009 freenode on 2009-10-02
- No one is required to be a catalyst, but the users who perform this
  role ensure the smooth and efficient functioning of the network.
- Even in cases where cooperation is intended,
  misunderstandings and personality incompatibilities can result
- 15 more annotations...
- - Catalysts help prevent and
    resolve misunderstanding, calm the waters when users have difficulties
    dealing with each other and provide examples of constructive behavior in
    environments where such behavior might not otherwise be the norm.
  - An effective catalyst is:
  - Relaxed
  - Catalysts
  - Open-minded
  - Responsible
  - Unobtrusive
  - Realistic
  - Careful
  - Attentive
  - Minimalist
  - Courteous
  - Cooperative
  - Someone with an internal locus of control
  - A user
Official Shrub.com Blog » Blog Archive » “Check my what?” On privilege and what we can do about it

Some tips on going from pro-equality in spirit to pro-equality in deed

blog.shrub.com/...2006-03-08_146 - Preview

2009 2009-11 2009-11-09 unread on 2009-11-09 and saved by 7 people
- Responses to ““Check my what?” On privilege and what we can do about it”
- “Check my what?” On
  privilege and what we can do about it
- 8 more annotations...
- - March 8, 2006
  - privilege and what we can do about it
  - Andrea Rubenstein
  - a resource for anti-oppression activists dealing with privileged groups
  - re
    ach the people who were well-meaning but didn’t get why people who weren’t in their privileged groups got so angry
  - privilege as a general concept
  - Last Updated: June 30, 2008
  - 173 Responses
So you made a mistake - Geek Feminism Wiki

geekfeminism.wikia.com/...So_you_made_a_mistake - Preview

2009 2009-11 2009-11-09 unread on 2009-11-09

1 - 20 of 20

Showing 20▼ items per page

List Comments (0)

List Info

Graham Perrin

20 items | 51 visits

Some highlights relating to netiquette, including: reference headers, threading and subject lines. Attention is drawn to a separate Diigo list for problems with Google Mail beta.

Updated on 2009-11-09
Created on 2008-12-24

Category: Computers & Internet

Internet guidelines philosophy netiquette subject edit thread references

URL:

Graham Perrin's List: etiquette on the Internet

Student Guidelines for Electronic Communication: Examples

Mailman Email List: User's Guide

E-lists at Cornell: Sending Messages

RFC 1855 - Netiquette Guidelines

draft-ietf-usefor-useage-01 - Usenet Best Practice

3.3.2. Presentation of Articles

3.3.2.1. Threading

RFC 1036 - Standard for interchange of USENET messages

RFC 5322 - Internet Message Format

RFC 2822 - Internet Message Format

draft-ietf-usefor-usepro-13 - Netnews Architecture and Protocols

RFC 4096 - Policy-Mandated Labels Such as "Adv:" in Email Subject Headers Considered Ineffective At Best

Policy-Mandated Labels Such as "Adv:" in Email Subject Headers

Considered Ineffective At Best

Broken threads in Google Mail Beta

Plone: asking for help with errors and problems

The Home Education Mailing List

draft-ietf-usefor-usefor-12 - Netnews Article Format

Gordon's Notes: Gmail feature request: the ability to edit subject lines

organizing discussion threads

Netiquette Home Page -- A Service of Albion.com

freenode philosophy: catalysts

Official Shrub.com Blog » Blog Archive » “Check my what?” On privilege and what we can do about it

So you made a mistake - Geek Feminism Wiki

List Info

Sponsored Links

Graham Perrin's Public Lists (42)