<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>

<channel>
	<title>willnorris.com &#187; netiquette</title>
	<atom:link href="http://willnorris.com/tag/netiquette/feed" rel="self" type="application/rss+xml" />
	<link>http://willnorris.com</link>
	<description>there&#039;s more to life than this</description>
	<lastBuildDate>Tue, 15 May 2012 21:57:32 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-beta3-20574</generator>
<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
		<item>
		<title>Email Etiquette: Replying to Mailing Lists</title>
		<link>http://willnorris.com/2008/12/email-etiquette-replying-to-mailing-lists</link>
		<comments>http://willnorris.com/2008/12/email-etiquette-replying-to-mailing-lists#comments</comments>
		<pubDate>Thu, 25 Dec 2008 22:23:44 +0000</pubDate>
		<dc:creator>Will Norris</dc:creator>
				<category><![CDATA[technology]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[mailing lists]]></category>
		<category><![CDATA[netiquette]]></category>

		<guid isPermaLink="false">http://willnorris.com/?p=467</guid>
		<description><![CDATA[Most email clients support the idea of &#8220;threaded messages&#8221;&#8230; that is, the client can group together individual email messages that are part of the same conversation, or &#8220;thread&#8221;. This is a particularly useful feature on mailing lists where multiple conversations are happening at the same time. For example, the following screenshot of the OpenID General [...]]]></description>
			<content:encoded><![CDATA[<p>Most email clients <a href="http://www.flickr.com/photos/wnorris/3135621059/in/photostream/">support the idea</a> of &#8220;threaded messages&#8221;&#8230; that is, the client can group together individual email messages that are part of the same conversation, or &#8220;thread&#8221;.  This is a particularly useful feature on mailing lists where multiple conversations are happening at the same time.  For example, the following screenshot of the <a href="http://openid.net/mailman/listinfo/general">OpenID General Discussion</a> list shows two distinct message threads in Apple&#8217;s Mail application:</p>

<p><img src="http://farm4.static.flickr.com/3227/3136438166_b8313d4de9_o.png" alt="Example of message threading" /></p>

<p>In order to match up messages that belong to the same conversation, email clients use two techniques.  First, they match emails with the same subject line, which is mostly accurate.  Occasionally this will result in &#8220;false positives&#8221; where unrelated emails are grouped together because the senders happened to use the same subject.  The second method is far more accurate and makes use of a hidden portion of the email message which most people never see.  Emails, just like web page requests include a number of hidden &#8220;headers&#8221; that carry extra information about the message.</p>

<p><img src="http://farm4.static.flickr.com/3102/3135669251_6d0428531b_o.png" alt="Email Headers" /></p>

<p>This includes information about the email client the sender used, the message priority, and the different servers that handled the message along the way.  Each email message also includes a unique identification string called the &#8220;Message-Id&#8221;.  This string is unique for every email message in the world&#8230; no two are ever identical.  In the screenshot above, the Message-Id is <code>&lt;49518270.7010405@degeneration.co.uk&gt;</code>.  If someone were to reply to that message, the Message-Id of the original email would be included in the reply email as another hidden header aptly named In-Reply-To:</p>

<p><img src="http://farm4.static.flickr.com/3096/3136500952_a2a5996464_o.png" alt="Email Reply" /></p>

<p>Any future replies would continue to include an In-Reply-To header with this value so that email clients can recognize that they all belong to together and group them accordingly.  This method of conversation tracking is far more accurate, but has one problem.  That problem occurs when some lazy person comes along and wants to send a message to the mailing list, but instead of clicking on &#8220;New Message&#8221; in their mail client, they pick a message at random from the list, click &#8220;Reply&#8221;, and then clear out the subject and body of the message.  While this <strong>looks</strong> like a new message about a new topic, because the person &#8220;replied&#8221; to a previous email instead of starting a new message, the previous Message-Id got attached.  Note the following reply to the same email above, but now the subject has been changed from talking about a Google sign-in button, to the BBC being an OpenID provider.  These are completely different discussions!</p>

<p><img src="http://farm4.static.flickr.com/3263/3136581064_faf84dec4b_o.png" alt="Incorrect Reply" /></p>

<p>If we go back to our first screenshot of the two message threads, we can see the this new message (as well as any of its replies) get lumped right together with the original discussion.</p>

<p><img src="http://farm4.static.flickr.com/3119/3135772283_3b54c129d2_o.png" alt="Merged Discussions" /></p>

<p>So today&#8217;s lesson in email etiquette: If you&#8217;re not actually replying to a particular email, <strong>DON&#8217;T CLICK &#8220;REPLY&#8221;</strong>.  Copy and paste the &#8220;To:&#8221; email address if you have to, but don&#8217;t click reply!  There might be some grace here for emails between individuals, but not on mailing lists, <strong>especially</strong> not on technical mailing lists.  (Not meaning to pick on Peter in the screenshots above&#8230; he is not the only offender on the OpenID mailing lists, that just happened to be the most recent occurrence).</p>

<p>Okay, that&#8217;s my rant for the day&#8230; I&#8217;m good now.  Oh, and Merry Christmas. :)</p>
]]></content:encoded>
			<wfw:commentRss>http://willnorris.com/2008/12/email-etiquette-replying-to-mailing-lists/feed</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>reach out and touch someone</title>
		<link>http://willnorris.com/2007/08/reach-out-and-touch-someone</link>
		<comments>http://willnorris.com/2007/08/reach-out-and-touch-someone#comments</comments>
		<pubDate>Wed, 15 Aug 2007 06:35:58 +0000</pubDate>
		<dc:creator>Will Norris</dc:creator>
				<category><![CDATA[identity]]></category>
		<category><![CDATA[personal]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[australia]]></category>
		<category><![CDATA[netiquette]]></category>
		<category><![CDATA[skype]]></category>
		<category><![CDATA[you-know-I-learned-something-today]]></category>

		<guid isPermaLink="false">http://willnorris.com/2007/08/reach-out-and-touch-someone</guid>
		<description><![CDATA[I just love the communication tools we have at our disposal in this day and age. Earlier tonight I received a rather unpleasant email from an apparently frustrated individual (let&#8217;s call him Joe) in reply to a message I sent to a mailing list. He quite insistently requested to be taken off said mailing list, [...]]]></description>
			<content:encoded><![CDATA[<p>I just love the communication tools we have at our disposal in this day and age.  Earlier tonight I received a rather unpleasant email from an apparently frustrated individual (let&#8217;s call him Joe) in reply to a message I sent to a mailing list.  He quite insistently requested to be taken off said mailing list, tossing in a few colloquial phrases and threats of legal action.  Since his reply came only to me and not the entire list, I alone had been chosen by Fate to rescue this distraught soul from the tyranny of <strike>unsolicited</strike> no-longer-desired <strike>constant emails</strike> message about once a month.</p>

<p><span id="more-192"></span></p>

<p>Rather than just reply with a big fat arrow pointing to the unsubscribe link at the bottom of every list message, I decided to try a more personal touch.  First I googled Joe&#8217;s name which he provided in the email along with the company name shown in the From header just to make sure this was a legitimate person (those spammers and phishers are getting pretty crafty these days).  I found that his company indeed existed in Australia and had a couple of domains that pointed to his website.  Now I could have tried the contact number on the website itself, but I decided to dig a little deeper.  Checking the whois entries on two of the domains, I found one registered to Joe with the same PO Box and phone number as the website, but the other had a Tasmanian residential address (thanks Google Maps), a different phone number, and was registered in a female&#8217;s name.  A little more googling and I found someone by that name listed as a 2006 graduate of a Tasmanian high school not 9 km from the listed residence.  Figuring this must be the right one, I decided to try the number.</p>

<p>I was down to $0.04 from my Skype trial, so I added some time to my account and dialed the number.  The gentleman who answered had an obvious Australian accent, as did the voices on the television I could hear in the background.  I asked for Joe but was told he wasn&#8217;t at this number.  I asked if he knew who Joe was, and he confirmed that he was Joe&#8217;s father-in-law.  I explained that I was calling from Los Angeles and asked if he had a number where I could reach Joe.  He provided me the number, but before hanging up inquired as to how I had gotten his name.  When I explained to him that a website domain was registered to this number, I learned that the female name listed was his granddaughter (presumably Joe&#8217;s daughter).  Having to learn a little about Australian phone numbers (replace the leading zero with +61 when calling internationally), I discovered that this new number was most likely a cell phone.  I dialed the number, waited some time for the call to connect, and then finally, I had reached Joe.</p>

<p>Not surprisingly, he sounded a little confused at first.  The colorful epithets had been replaced by embarrassment and repeated apologies.  I told him it was quite alright and that I understood he wasn&#8217;t really angry with me, but rather was frustrated with the fact that his continual requests to be unsubscribed proved fruitless.  I then directed his attention back to my email and the the auto-attached footer which contained the link for unsubscribing.  A couple more apologies and &#8220;it&#8217;s okay, I understand&#8220;&#8216;s and we were bidding each other &#8220;Cheerio!&#8221; (that&#8217;s England isn&#8217;t it, not Australia&#8230; nevermind, then).</p>

<p>So first, it&#8217;s kinda cool that I was able to find this guy and call him within just a few minutes to help solve his problem.  All the tools are right there to do the research, and technology like Skype makes international calling affordable (if not free).  Depending on how you want to look at it though, you could also say it&#8217;s rather scary that I was able to find this guy and call him within just a few minutes.  Not only that, I discovered his (presumed) daughter&#8217;s name, approximate age, and high school, as well as his father-in-law&#8217;s phone number and home address (along with a nice satellite photo courtesy of Google Earth).  Were I not the nice guy that I am, I might have taken offense to his reply and sought to do unkindly things to him and his family.  But then again, I put myself right out there on the web, so I guess the same could be done to me.  (Although for me, it kinda comes with the territory.)</p>

<p><a href="http://www.google.com/search?q=%22you+know,+I+learned+something+today%22">You know, I learned something today</a>.  I learned that people on the Internet&#8230; they&#8217;re just people, like you and me.  They may say hurtful things in an email, but it may just be that they&#8217;re frustrated with technology.  I&#8217;ve learned that sometimes they just need a helping hand to get off that email list, and that they really didn&#8217;t mean for those hurtful words to be directed at you personally.  But I&#8217;ve also learned that if they did, it&#8217;s really easy to find their family and cause them some real grief!  (Just kidding, Joe) :)</p>
]]></content:encoded>
			<wfw:commentRss>http://willnorris.com/2007/08/reach-out-and-touch-someone/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Bottom posting in Mail.app (with Quicksilver)</title>
		<link>http://willnorris.com/2007/07/bottom-posting-in-mailapp-with-quicksilver</link>
		<comments>http://willnorris.com/2007/07/bottom-posting-in-mailapp-with-quicksilver#comments</comments>
		<pubDate>Wed, 18 Jul 2007 20:23:43 +0000</pubDate>
		<dc:creator>Will Norris</dc:creator>
				<category><![CDATA[technology]]></category>
		<category><![CDATA[applescript]]></category>
		<category><![CDATA[bottom-posting]]></category>
		<category><![CDATA[mail.app]]></category>
		<category><![CDATA[netiquette]]></category>
		<category><![CDATA[top-posting]]></category>

		<guid isPermaLink="false">http://willnorris.com/2007/07/bottom-posting-in-mailapp-with-quicksilver</guid>
		<description><![CDATA[John Gruber posted his applescript for Mail.app to &#8220;bottom-post&#8221; reply to an email last week (and I&#8217;m just now reading it, sigh). However, he talks about using FastScripts to invoke the script whereas I prefer Quicksilver for things like this if possible. The advantage of FastScripts is that it grabs the keystroke before the application [...]]]></description>
			<content:encoded><![CDATA[<p>John Gruber posted <a href="http://daringfireball.net/2007/07/non_top_posting_scripts">his applescript</a> for Mail.app to &#8220;bottom-post&#8221; reply to an email last week (and I&#8217;m just now reading it, <em>sigh</em>).  However, he talks about using <a href="http://www.red-sweater.com/fastscripts/">FastScripts</a> to invoke the script whereas I prefer <a href="http://quicksilver.blacktree.com/">Quicksilver</a> for things like this if possible.  The advantage of FastScripts is that it grabs the keystroke before the application does, so no other modification is necessary.  It&#8217;s still possible with Quicksilver, but you need to take a few extra steps.</p>

<p>First set alternate shortcuts for the normal menu options by opening the Keyboard Preference Pane and click on the last tab &#8220;Keyboard Shortcuts&#8221;.  Add a new shortcut, selecting &#8220;Mail&#8221; as the application, &#8220;Reply&#8221; as the menu title, and give it some obscure shortcut (I&#8217;m using &#8984;&#8997;R).  Repeat to remap &#8220;Reply All&#8221; as well (I&#8217;m adding a &#8679; to the previous shortcut).  Relaunch Mail.app for the changes to take effect.  Then you can setup the scripts and assign them as triggers within Quicksilver for use specifically within Mail.app.</p>
]]></content:encoded>
			<wfw:commentRss>http://willnorris.com/2007/07/bottom-posting-in-mailapp-with-quicksilver/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>E-mail is not a platform for design</title>
		<link>http://willnorris.com/2007/06/e-mail-is-not-a-platform-for-design</link>
		<comments>http://willnorris.com/2007/06/e-mail-is-not-a-platform-for-design#comments</comments>
		<pubDate>Mon, 11 Jun 2007 04:51:55 +0000</pubDate>
		<dc:creator>Will Norris</dc:creator>
				<category><![CDATA[technology]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[netiquette]]></category>

		<guid isPermaLink="false">http://willnorris.com/2007/06/e-mail-is-not-a-platform-for-design</guid>
		<description><![CDATA[I&#8217;ve been away from my blog for quite a while due to some various medical problems, but I really do have a number of posts in the works. It&#8217;s a a little lame to return with just a link, but this one is near and dear to my heart: E-mail is not a platform for [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been away from my blog for quite a while due to some various medical problems, but I really do have a number of posts in the works.  It&#8217;s a a little lame to return with just a link, but this one is near and dear to my heart:</p>

<p><a href="http://www.zeldman.com/2007/06/08/e-mail-is-not-a-platform-for-design/">E-mail is not a platform for design</a></p>
]]></content:encoded>
			<wfw:commentRss>http://willnorris.com/2007/06/e-mail-is-not-a-platform-for-design/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

