<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Gruber&#8217;s bottom-posting scripts for Mail.app</title>
	<atom:link href="http://www.hawkwings.net/2007/07/18/grubers-bottom-posting-scripts-for-mailapp/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hawkwings.net/2007/07/18/grubers-bottom-posting-scripts-for-mailapp/</link>
	<description>Tips and add-ons to make Apple Mail / Mail.app even better</description>
	<lastBuildDate>Mon, 21 Nov 2011 18:23:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Carroll</title>
		<link>http://www.hawkwings.net/2007/07/18/grubers-bottom-posting-scripts-for-mailapp/comment-page-1/#comment-273662</link>
		<dc:creator>Carroll</dc:creator>
		<pubDate>Fri, 16 Nov 2007 02:43:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2007/07/18/grubers-bottom-posting-scripts-for-mailapp/#comment-273662</guid>
		<description>Philosophy aside, I&#039;ve been using Gruber&#039;s script since Hawk Wings linked to it, except I use Shift-Command-R since I use Command-R frequently in the Finder to &quot;Show [Reveal] Original.&quot; It&#039;s always worked fine until today, the day after I updated to 10.4.11 (perhaps a coincidence). I changed the 0.5-second delay in the script to 1 second and all is OK now. Could be 0.5 second was always &quot;on the edge&quot; in my setup.</description>
		<content:encoded><![CDATA[<p>Philosophy aside, I&#8217;ve been using Gruber&#8217;s script since Hawk Wings linked to it, except I use Shift-Command-R since I use Command-R frequently in the Finder to &#8220;Show [Reveal] Original.&#8221; It&#8217;s always worked fine until today, the day after I updated to 10.4.11 (perhaps a coincidence). I changed the 0.5-second delay in the script to 1 second and all is OK now. Could be 0.5 second was always &#8220;on the edge&#8221; in my setup.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ryan</title>
		<link>http://www.hawkwings.net/2007/07/18/grubers-bottom-posting-scripts-for-mailapp/comment-page-1/#comment-193189</link>
		<dc:creator>ryan</dc:creator>
		<pubDate>Fri, 10 Aug 2007 12:37:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2007/07/18/grubers-bottom-posting-scripts-for-mailapp/#comment-193189</guid>
		<description>@earth2kelly:

A: It destroys the flow of conversation.
Q: What&#039;s wrong with top-posting?

You&#039;re missing the arguments main point. The main point of bottom posting is that it makes it less of a hassle to NOT quote the entire message at all! Why should you &quot;have to re-read a full conversation before getting on with the latest post?&quot; -- Good question! Why are you quoting the full original post?

Regular conversations on the street do not sometimes last for weeks, if they did it would be understood to have a little context before you continue.

A: &quot;Hey remember that project we were talking about last week?&quot;
B: &quot;Yes.&quot;
A: &quot;Well to hell with it.&quot;

As opposed to:

A: &quot;Hey... To hell with it.&quot;
B: &quot;Uhh, wha--&quot;
A: 
B: &quot;Oh... uhh... that was unneccessary...&quot;

The idea is to only quote what will provide context to your NEW comments. If I&#039;m a busy guy and I have, at any given moment, something like 10-50 email conversations going on at once (not to mention real world conversations in between) then it is not entirely shocking that I might want to reread a little of what was said previously. In that case WHY would I want to scroll PAST the new stuff, find the relevant parts in paragraphs and paragraphs of old replies and then scroll BACK UP to read the new stuff... It should be inline, and it should be snipped to only include the relevant parts.

So, don&#039;t be so literal. &quot;Bottom posting&quot; doesn&#039;t mean to literally go to the bottom of every email to write your response, it means to be smart about what you are quoting in the first place and write your response with context in a logical way.

That said, keep in mind that for a 1on1 conversation where you are saying things like:

A: &quot;Want to come over saturday?&quot;
B: &quot;Sure.&quot;

It&#039;s unnecessary for context at all so just stick with tacking your response on top, it&#039;s simpler, the person wont need context (unless they maybe come back month from now to read the conversation) -- it all depends on what you&#039;re emailing about. Responding to a flame war thread RE: GPLv3 in the Linux kernel mailing list requires more thoughtful quoting/context than telling your grandma you loved the cookies.

Thank you,
    Ryan</description>
		<content:encoded><![CDATA[<p>@earth2kelly:</p>
<p>A: It destroys the flow of conversation.<br />
Q: What&#8217;s wrong with top-posting?</p>
<p>You&#8217;re missing the arguments main point. The main point of bottom posting is that it makes it less of a hassle to NOT quote the entire message at all! Why should you &#8220;have to re-read a full conversation before getting on with the latest post?&#8221; &#8212; Good question! Why are you quoting the full original post?</p>
<p>Regular conversations on the street do not sometimes last for weeks, if they did it would be understood to have a little context before you continue.</p>
<p>A: &#8220;Hey remember that project we were talking about last week?&#8221;<br />
B: &#8220;Yes.&#8221;<br />
A: &#8220;Well to hell with it.&#8221;</p>
<p>As opposed to:</p>
<p>A: &#8220;Hey&#8230; To hell with it.&#8221;<br />
B: &#8220;Uhh, wha&#8211;&#8221;<br />
A:<br />
B: &#8220;Oh&#8230; uhh&#8230; that was unneccessary&#8230;&#8221;</p>
<p>The idea is to only quote what will provide context to your NEW comments. If I&#8217;m a busy guy and I have, at any given moment, something like 10-50 email conversations going on at once (not to mention real world conversations in between) then it is not entirely shocking that I might want to reread a little of what was said previously. In that case WHY would I want to scroll PAST the new stuff, find the relevant parts in paragraphs and paragraphs of old replies and then scroll BACK UP to read the new stuff&#8230; It should be inline, and it should be snipped to only include the relevant parts.</p>
<p>So, don&#8217;t be so literal. &#8220;Bottom posting&#8221; doesn&#8217;t mean to literally go to the bottom of every email to write your response, it means to be smart about what you are quoting in the first place and write your response with context in a logical way.</p>
<p>That said, keep in mind that for a 1on1 conversation where you are saying things like:</p>
<p>A: &#8220;Want to come over saturday?&#8221;<br />
B: &#8220;Sure.&#8221;</p>
<p>It&#8217;s unnecessary for context at all so just stick with tacking your response on top, it&#8217;s simpler, the person wont need context (unless they maybe come back month from now to read the conversation) &#8212; it all depends on what you&#8217;re emailing about. Responding to a flame war thread RE: GPLv3 in the Linux kernel mailing list requires more thoughtful quoting/context than telling your grandma you loved the cookies.</p>
<p>Thank you,<br />
    Ryan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EugÃ©ne</title>
		<link>http://www.hawkwings.net/2007/07/18/grubers-bottom-posting-scripts-for-mailapp/comment-page-1/#comment-187922</link>
		<dc:creator>EugÃ©ne</dc:creator>
		<pubDate>Wed, 01 Aug 2007 18:23:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2007/07/18/grubers-bottom-posting-scripts-for-mailapp/#comment-187922</guid>
		<description>On my side, again, I find top posting an abhorrent practice.

Interleaved posting (what most people mean when they refer to bottom posting) allows me to keep track of which portions of an email you agree or disagree with. Which portions you feel I should pay particular attention to. Which portion, exactly, you feel should be for my attention.

Unlike the previous poster, I am one of those geeks. And, also apparently unlike the previous poster, I have more than one email &quot;conversation&quot; I attempt to keep track of at any one time. And since I need to respond with an informed decision, view or opinion, I do find that I can not always remember the context of the issue under discussion in an email.

Expecting me to reread the whole email (and in reverse yet!) just because you&#039;re too lazy or ignorant to trim to the relevant data is rude, obnoxious and arrogant. And it certainly tells me that the sender considers their time infinitely more important than mine.

With the current state of top posting the full email gets sent hither and thither, normally with a very informative and thought-provoking &quot;FYI&quot; or &quot;I agree&quot; as the only addition added to the top of the email. Well, either say something useful or be quiet, is my normal stance on that. Otherwise rather quote nothing and post &quot;I agree&quot; if you expect me to refer to the mail thread.

Or do the sane, civilised and respectful thing. Quote what exactly it is that you agree to or with, if you find that your sole contribution to the conversation must be an &quot;I agree&quot;.</description>
		<content:encoded><![CDATA[<p>On my side, again, I find top posting an abhorrent practice.</p>
<p>Interleaved posting (what most people mean when they refer to bottom posting) allows me to keep track of which portions of an email you agree or disagree with. Which portions you feel I should pay particular attention to. Which portion, exactly, you feel should be for my attention.</p>
<p>Unlike the previous poster, I am one of those geeks. And, also apparently unlike the previous poster, I have more than one email &#8220;conversation&#8221; I attempt to keep track of at any one time. And since I need to respond with an informed decision, view or opinion, I do find that I can not always remember the context of the issue under discussion in an email.</p>
<p>Expecting me to reread the whole email (and in reverse yet!) just because you&#8217;re too lazy or ignorant to trim to the relevant data is rude, obnoxious and arrogant. And it certainly tells me that the sender considers their time infinitely more important than mine.</p>
<p>With the current state of top posting the full email gets sent hither and thither, normally with a very informative and thought-provoking &#8220;FYI&#8221; or &#8220;I agree&#8221; as the only addition added to the top of the email. Well, either say something useful or be quiet, is my normal stance on that. Otherwise rather quote nothing and post &#8220;I agree&#8221; if you expect me to refer to the mail thread.</p>
<p>Or do the sane, civilised and respectful thing. Quote what exactly it is that you agree to or with, if you find that your sole contribution to the conversation must be an &#8220;I agree&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Travis Bell</title>
		<link>http://www.hawkwings.net/2007/07/18/grubers-bottom-posting-scripts-for-mailapp/comment-page-1/#comment-180270</link>
		<dc:creator>Travis Bell</dc:creator>
		<pubDate>Wed, 18 Jul 2007 23:51:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2007/07/18/grubers-bottom-posting-scripts-for-mailapp/#comment-180270</guid>
		<description>http://travisbell.com/post/5416573

Heh, I don&#039;t agree with it. But here&#039;s to all who do. :)</description>
		<content:encoded><![CDATA[<p><a href="http://travisbell.com/post/5416573" rel="nofollow">http://travisbell.com/post/5416573</a></p>
<p>Heh, I don&#8217;t agree with it. But here&#8217;s to all who do. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: earth2kelly</title>
		<link>http://www.hawkwings.net/2007/07/18/grubers-bottom-posting-scripts-for-mailapp/comment-page-1/#comment-180259</link>
		<dc:creator>earth2kelly</dc:creator>
		<pubDate>Wed, 18 Jul 2007 23:03:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2007/07/18/grubers-bottom-posting-scripts-for-mailapp/#comment-180259</guid>
		<description>I think bottom posting is an abomination! It&#039;s an unfortunate holdover from when geeks controlled usenet and e-mail rules. Why should I have to re-read a full conversation before getting on with the latest post? The main argument seems to be that I would be so dull witted that I can&#039;t keep the prior conversation strait and would somehow be unable to refer to what&#039;s posted below if I needed to refresh my memory. Can you imagine what it would be like if in order to  say something to someone on the street, you would have to repeat everything that was said prior to that?</description>
		<content:encoded><![CDATA[<p>I think bottom posting is an abomination! It&#8217;s an unfortunate holdover from when geeks controlled usenet and e-mail rules. Why should I have to re-read a full conversation before getting on with the latest post? The main argument seems to be that I would be so dull witted that I can&#8217;t keep the prior conversation strait and would somehow be unable to refer to what&#8217;s posted below if I needed to refresh my memory. Can you imagine what it would be like if in order to  say something to someone on the street, you would have to repeat everything that was said prior to that?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.hawkwings.net/2007/07/18/grubers-bottom-posting-scripts-for-mailapp/comment-page-1/#comment-180115</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 18 Jul 2007 15:36:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2007/07/18/grubers-bottom-posting-scripts-for-mailapp/#comment-180115</guid>
		<description>&gt; John Gruber is not so relaxed. He calls top-posting â€œan uncouth and illiterate practiceâ€.

However, in a second post on the subject he says that by &quot;bottom posting&quot; he meant, as most people do, interleaving--as described here:

http://mailformat.dan.info/quoting/bottom-posting.html

If one is going to edit the original message down and insert answers inline, which seems a sensible enough practice--not quote everything and begin under it--I can&#039;t see it matters if the cursor starts at the top.

But I&#039;d agree that Mail assumes the user will be top-posting, because it doesn&#039;t add sig-delimters to signatures and can&#039;t recognize and strip them and the following sig-block on replies.

I found out recently that--surprisingly--Entourage, unlike Mail.app, has got signature-handling. So it seems not all of Microsoft is wedded to the top-posting paradigm.

http://blog.entourage.mvps.org/2007/06/signature_blocks_and_netiquett.html</description>
		<content:encoded><![CDATA[<p>&gt; John Gruber is not so relaxed. He calls top-posting â€œan uncouth and illiterate practiceâ€.</p>
<p>However, in a second post on the subject he says that by &#8220;bottom posting&#8221; he meant, as most people do, interleaving&#8211;as described here:</p>
<p><a href="http://mailformat.dan.info/quoting/bottom-posting.html" rel="nofollow">http://mailformat.dan.info/quoting/bottom-posting.html</a></p>
<p>If one is going to edit the original message down and insert answers inline, which seems a sensible enough practice&#8211;not quote everything and begin under it&#8211;I can&#8217;t see it matters if the cursor starts at the top.</p>
<p>But I&#8217;d agree that Mail assumes the user will be top-posting, because it doesn&#8217;t add sig-delimters to signatures and can&#8217;t recognize and strip them and the following sig-block on replies.</p>
<p>I found out recently that&#8211;surprisingly&#8211;Entourage, unlike Mail.app, has got signature-handling. So it seems not all of Microsoft is wedded to the top-posting paradigm.</p>
<p><a href="http://blog.entourage.mvps.org/2007/06/signature_blocks_and_netiquett.html" rel="nofollow">http://blog.entourage.mvps.org/2007/06/signature_blocks_and_netiquett.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

