<?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: Email etiquette guides for online tourists</title>
	<atom:link href="http://stormyscorner.com/2008/08/email-etiquette-guides-for-online-tourists.html/feed" rel="self" type="application/rss+xml" />
	<link>http://stormyscorner.com/2008/08/email-etiquette-guides-for-online-tourists.html</link>
	<description></description>
	<lastBuildDate>Thu, 02 Feb 2012 12:13:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: rawsausage</title>
		<link>http://stormyscorner.com/2008/08/email-etiquette-guides-for-online-tourists.html/comment-page-1#comment-1184</link>
		<dc:creator>rawsausage</dc:creator>
		<pubDate>Sun, 24 Aug 2008 10:50:52 +0000</pubDate>
		<guid isPermaLink="false">http://stormyscorner.com/2008/08/email-etiquette-guides-for-online-tourists.html#comment-1184</guid>
		<description>I have to add one thing that I think I did not remember to mention. Actually, such archival procedure is illegal in some countries without the explicit approval of the people on the mailing list. In fact if any of these sites such as mail-archive.com were on my home country, I would instantly sue them and force them to be closed down. The reason is simply that they are doing WRONG.
</description>
		<content:encoded><![CDATA[<p>I have to add one thing that I think I did not remember to mention. Actually, such archival procedure is illegal in some countries without the explicit approval of the people on the mailing list. In fact if any of these sites such as mail-archive.com were on my home country, I would instantly sue them and force them to be closed down. The reason is simply that they are doing WRONG.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://stormyscorner.com/2008/08/email-etiquette-guides-for-online-tourists.html/comment-page-1#comment-1183</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Fri, 15 Aug 2008 08:15:56 +0000</pubDate>
		<guid isPermaLink="false">http://stormyscorner.com/2008/08/email-etiquette-guides-for-online-tourists.html#comment-1183</guid>
		<description>Note &quot;Linuix&quot; is a typo in the previous post. It
should read &quot;Linux&quot;.
In addition to the advantage listed above, Linux
is immune to the hundreds of thousands of Windows
based virii and other malware currently active
on the web and so is safe to run without any of
that stupid performance sapping (and I might add,
pretty much totally ineffective ) virus scanner
software.
For those who will attempt to claim the Linux is
in danger from viruses as well, allow me to retort
snidely &quot;Not so much&quot;.
I have been running literally hundreds of
installations of Linux systems (starting in 1995)
connected directly to the web and have never
had even a single malware infestation. (Nor any
manually installed rootkits either). Because
the security design of UNIX/Linux has had to
contend with the issue of unauthorized privilege
escalation since the 1970&#039;s the current systems
have been architected in such a way that makes
unauthorized privilege escalation orders of magnitude
more difficult to achieve. ( Not impossible , of course.
As Gene Spafford and Bruce Schneier are
wont to say, there is no such thing
as unbreakable security. Anything man can create
another man can undo.)
(Please note that Linux has not been around since
the 1970&#039;s but, yes it did inherit the design
benefits of the UNIX decades prior to it
and so has the same level of protection. In fact,
Linux may have a bit more since its designers
decided that SUID shell scripts would not be
allowed to have privilege escalation at all. )
(Final note - for those who want to claim &quot;virii&quot;
isn&#039;t a word, please go look at your linguistics
text book on how words come into existence. You
will will see clearly that there is NO rule
requiring that newly formed words conform to the
rules for Latin (which is not the language English
is derived from any and also it happens to be DEAD
anyway!) The idea that the word virii must conform
to those rules is a festering hallucination in
the overheated minds of spinster middle school
grammar teacher whose existence has lost almost
all relevant purpose. Miss Grundy, Mr. Fentwhistle
- its time to retire and take your
unrealistic &quot;prescriptivism&quot; with you. Please
look at the the new words added to the dictionary
in the past ten years, especially those from the
tech sector and see how many follow ANY rules for
Latin. :-D One extreme example would be &quot;W00t&quot;
What? They added w00t to the dictionary? Yes, yes
they did. Who really uses that anyway? Frankly, I
have no idea. :-)
</description>
		<content:encoded><![CDATA[<p>Note &#8220;Linuix&#8221; is a typo in the previous post. It<br />
should read &#8220;Linux&#8221;.<br />
In addition to the advantage listed above, Linux<br />
is immune to the hundreds of thousands of Windows<br />
based virii and other malware currently active<br />
on the web and so is safe to run without any of<br />
that stupid performance sapping (and I might add,<br />
pretty much totally ineffective ) virus scanner<br />
software.<br />
For those who will attempt to claim the Linux is<br />
in danger from viruses as well, allow me to retort<br />
snidely &#8220;Not so much&#8221;.<br />
I have been running literally hundreds of<br />
installations of Linux systems (starting in 1995)<br />
connected directly to the web and have never<br />
had even a single malware infestation. (Nor any<br />
manually installed rootkits either). Because<br />
the security design of UNIX/Linux has had to<br />
contend with the issue of unauthorized privilege<br />
escalation since the 1970&#8242;s the current systems<br />
have been architected in such a way that makes<br />
unauthorized privilege escalation orders of magnitude<br />
more difficult to achieve. ( Not impossible , of course.<br />
As Gene Spafford and Bruce Schneier are<br />
wont to say, there is no such thing<br />
as unbreakable security. Anything man can create<br />
another man can undo.)<br />
(Please note that Linux has not been around since<br />
the 1970&#8242;s but, yes it did inherit the design<br />
benefits of the UNIX decades prior to it<br />
and so has the same level of protection. In fact,<br />
Linux may have a bit more since its designers<br />
decided that SUID shell scripts would not be<br />
allowed to have privilege escalation at all. )<br />
(Final note &#8211; for those who want to claim &#8220;virii&#8221;<br />
isn&#8217;t a word, please go look at your linguistics<br />
text book on how words come into existence. You<br />
will will see clearly that there is NO rule<br />
requiring that newly formed words conform to the<br />
rules for Latin (which is not the language English<br />
is derived from any and also it happens to be DEAD<br />
anyway!) The idea that the word virii must conform<br />
to those rules is a festering hallucination in<br />
the overheated minds of spinster middle school<br />
grammar teacher whose existence has lost almost<br />
all relevant purpose. Miss Grundy, Mr. Fentwhistle<br />
- its time to retire and take your<br />
unrealistic &#8220;prescriptivism&#8221; with you. Please<br />
look at the the new words added to the dictionary<br />
in the past ten years, especially those from the<br />
tech sector and see how many follow ANY rules for<br />
Latin. <img src='http://stormyscorner.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':-D' class='wp-smiley' />  One extreme example would be &#8220;W00t&#8221;<br />
What? They added w00t to the dictionary? Yes, yes<br />
they did. Who really uses that anyway? Frankly, I<br />
have no idea. <img src='http://stormyscorner.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stormy</title>
		<link>http://stormyscorner.com/2008/08/email-etiquette-guides-for-online-tourists.html/comment-page-1#comment-1182</link>
		<dc:creator>Stormy</dc:creator>
		<pubDate>Fri, 15 Aug 2008 07:45:56 +0000</pubDate>
		<guid isPermaLink="false">http://stormyscorner.com/2008/08/email-etiquette-guides-for-online-tourists.html#comment-1182</guid>
		<description>It&#039;s not that the software doesn&#039;t do it ...
In many cultures (like large companies), you are supposed to take the topic &quot;offline&quot; when the discussion ends up going back and forth between just a couple of people or if it&#039;s clearly an action item with an identified owner. Then you come back and report later. So it&#039;s a conscious decision to un-cc everyone to save them from getting too much mail that&#039;s not relevant to them. Moving from that world to a mailing list, open source type world, I had to consciously remember to cc everyone. Or rather consciously remember not to un-cc everyone.
</description>
		<content:encoded><![CDATA[<p>It&#8217;s not that the software doesn&#8217;t do it &#8230;<br />
In many cultures (like large companies), you are supposed to take the topic &#8220;offline&#8221; when the discussion ends up going back and forth between just a couple of people or if it&#8217;s clearly an action item with an identified owner. Then you come back and report later. So it&#8217;s a conscious decision to un-cc everyone to save them from getting too much mail that&#8217;s not relevant to them. Moving from that world to a mailing list, open source type world, I had to consciously remember to cc everyone. Or rather consciously remember not to un-cc everyone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://stormyscorner.com/2008/08/email-etiquette-guides-for-online-tourists.html/comment-page-1#comment-1181</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Fri, 15 Aug 2008 07:23:09 +0000</pubDate>
		<guid isPermaLink="false">http://stormyscorner.com/2008/08/email-etiquette-guides-for-online-tourists.html#comment-1181</guid>
		<description>&quot;Remember to cc &#039;the LIST&#039; &quot; WTF????
Excuse me, dont these people have computers?  Why should they have to remember this?  Why doesnt the computer
AUTOMATICALLY DO IT FOR THEM?
If your email client software doesnt recognize when you are responding to an email list and automatically default to sending your response directly to the list (with an option to send ONLY to a specific person(s) ) then you need to get  a better email client program!
I&#039;ve been using email since 1979 and frankly anyone who is putting up with an email client that can&#039;t do this for them is, frankly, doing the computer&#039;s job for  it rather than the computer doing the job for the human.
If you can&#039;t find software that works for you rather than the other way around, I suggest you start looking for email programs that run on UNIX or Linuix platforms rather that garbage Microsoft has been putting out for the past 20 years.
</description>
		<content:encoded><![CDATA[<p>&#8220;Remember to cc &#8216;the LIST&#8217; &#8221; WTF????<br />
Excuse me, dont these people have computers?  Why should they have to remember this?  Why doesnt the computer<br />
AUTOMATICALLY DO IT FOR THEM?<br />
If your email client software doesnt recognize when you are responding to an email list and automatically default to sending your response directly to the list (with an option to send ONLY to a specific person(s) ) then you need to get  a better email client program!<br />
I&#8217;ve been using email since 1979 and frankly anyone who is putting up with an email client that can&#8217;t do this for them is, frankly, doing the computer&#8217;s job for  it rather than the computer doing the job for the human.<br />
If you can&#8217;t find software that works for you rather than the other way around, I suggest you start looking for email programs that run on UNIX or Linuix platforms rather that garbage Microsoft has been putting out for the past 20 years.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rawsausage</title>
		<link>http://stormyscorner.com/2008/08/email-etiquette-guides-for-online-tourists.html/comment-page-1#comment-1180</link>
		<dc:creator>rawsausage</dc:creator>
		<pubDate>Fri, 15 Aug 2008 07:15:01 +0000</pubDate>
		<guid isPermaLink="false">http://stormyscorner.com/2008/08/email-etiquette-guides-for-online-tourists.html#comment-1180</guid>
		<description>Not really. The civilized projects don&#039;t let spiders index everything. That would be  yet another privacy violation. And indeed, those external sites are plain scum as well.
</description>
		<content:encoded><![CDATA[<p>Not really. The civilized projects don&#8217;t let spiders index everything. That would be  yet another privacy violation. And indeed, those external sites are plain scum as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Livingston</title>
		<link>http://stormyscorner.com/2008/08/email-etiquette-guides-for-online-tourists.html/comment-page-1#comment-1179</link>
		<dc:creator>James Livingston</dc:creator>
		<pubDate>Fri, 15 Aug 2008 02:07:10 +0000</pubDate>
		<guid isPermaLink="false">http://stormyscorner.com/2008/08/email-etiquette-guides-for-online-tourists.html#comment-1179</guid>
		<description>rawsausage: I don&#039;t see how sending all bug reports to a &quot;myproject-bugs&quot; mailing list is a privacy violation, anyone who can search the mailing list archives can almost certainly search the bug tracker too.
Opting out of having your post stored in the mailing list archives wouldn&#039;t help much either, as there are a large number of external sites who also archive them. A quick google seems to indicate that sites archiving gnome.org mailing lists include: gmane, mail-archive.com, osdir.com and nabble.com, as well as quite a few others.
</description>
		<content:encoded><![CDATA[<p>rawsausage: I don&#8217;t see how sending all bug reports to a &#8220;myproject-bugs&#8221; mailing list is a privacy violation, anyone who can search the mailing list archives can almost certainly search the bug tracker too.<br />
Opting out of having your post stored in the mailing list archives wouldn&#8217;t help much either, as there are a large number of external sites who also archive them. A quick google seems to indicate that sites archiving gnome.org mailing lists include: gmane, mail-archive.com, osdir.com and nabble.com, as well as quite a few others.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rawsausage</title>
		<link>http://stormyscorner.com/2008/08/email-etiquette-guides-for-online-tourists.html/comment-page-1#comment-1178</link>
		<dc:creator>rawsausage</dc:creator>
		<pubDate>Thu, 14 Aug 2008 14:49:07 +0000</pubDate>
		<guid isPermaLink="false">http://stormyscorner.com/2008/08/email-etiquette-guides-for-online-tourists.html#comment-1178</guid>
		<description>One thing that people don&#039;t understand is that it should be made really clear (impossible to pass by) that the emails will be archived for nearly eternity, and they will be very visible to search engines. It&#039;s bad privacy policy. It&#039;s not opt-in, it&#039;s not even opt-out. It&#039;s more like suckered-in.
Some services set up by open source projects echo for instance bug tickets into mailing lists. Doing that without telling about it in advance clearly violates the privacy of the bug reporter, just like the other services too that are not very clear with how they will be archiving the posts.
Perhaps open source projects should clean up their acts...
</description>
		<content:encoded><![CDATA[<p>One thing that people don&#8217;t understand is that it should be made really clear (impossible to pass by) that the emails will be archived for nearly eternity, and they will be very visible to search engines. It&#8217;s bad privacy policy. It&#8217;s not opt-in, it&#8217;s not even opt-out. It&#8217;s more like suckered-in.<br />
Some services set up by open source projects echo for instance bug tickets into mailing lists. Doing that without telling about it in advance clearly violates the privacy of the bug reporter, just like the other services too that are not very clear with how they will be archiving the posts.<br />
Perhaps open source projects should clean up their acts&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

