<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.1-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: New Rules of Engagement</title>
	<link>http://evolutionanddesign.blogsome.com/2006/07/09/new-rules-of-engagement/</link>
	<description>The weblog of BioEE 467, Summer 2006, Cornell University</description>
	<pubDate>Fri, 01 Jan 2010 05:49:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1-alpha</generator>

	<item>
		<title>by: ivy privy</title>
		<link>http://evolutionanddesign.blogsome.com/2006/07/09/new-rules-of-engagement/#comment-952</link>
		<pubDate>Wed, 19 Jul 2006 15:20:47 +0100</pubDate>
		<guid>http://evolutionanddesign.blogsome.com/2006/07/09/new-rules-of-engagement/#comment-952</guid>
					<description>Administrator: Lately on this site I am seeing a lot of a browser popup window that tells me this:

&lt;b&gt;A script on this page is causing mozilla to run slowly. If it continues to run, your computer may become unresponsive.

Do you want to abort the script?&lt;/b&gt;&lt;b&gt;

Could you please look into this and see if there is any streamlining that could be done? I am using Firefox on Linux.

Thanks,
&lt;/b&gt;</description>
		<content:encoded><![CDATA[	<p>Administrator: Lately on this site I am seeing a lot of a browser popup window that tells me this:</p>
	<p><b>A script on this page is causing mozilla to run slowly. If it continues to run, your computer may become unresponsive.</p>
	<p>Do you want to abort the script?</b><b></p>
	<p>Could you please look into this and see if there is any streamlining that could be done? I am using Firefox on Linux.</p>
	<p>Thanks,<br />
</b>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: ivy privy</title>
		<link>http://evolutionanddesign.blogsome.com/2006/07/09/new-rules-of-engagement/#comment-494</link>
		<pubDate>Mon, 10 Jul 2006 18:35:06 +0100</pubDate>
		<guid>http://evolutionanddesign.blogsome.com/2006/07/09/new-rules-of-engagement/#comment-494</guid>
					<description>&lt;i&gt;And BTW, the boards are now open again. Fire at Will…&lt;/i&gt;

Tomorrow's headline:
&lt;b&gt;Cornell prof calls for assassination of colleague&lt;/b&gt;
</description>
		<content:encoded><![CDATA[	<p><i>And BTW, the boards are now open again. Fire at Will…</i></p>
	<p>Tomorrow&#8217;s headline:<br />
<b>Cornell prof calls for assassination of colleague</b>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Hannah</title>
		<link>http://evolutionanddesign.blogsome.com/2006/07/09/new-rules-of-engagement/#comment-482</link>
		<pubDate>Mon, 10 Jul 2006 10:40:41 +0100</pubDate>
		<guid>http://evolutionanddesign.blogsome.com/2006/07/09/new-rules-of-engagement/#comment-482</guid>
					<description>&lt;blockquote&gt;So, can we resume commenting on last week’s posts? &lt;/blockquote&gt;
Yes, with a few provisos: all quarrels &lt;i&gt;must&lt;/i&gt; be left off, and any unanswered insults from last week must &lt;i&gt;must&lt;/i&gt; now be overlooked. Very off-topic comments should also be ignored.

Moderation will be a good deal stricter from now on, and responding to a less-than-temperate posts from last week is no excuse for  a less-than-temperate post now.</description>
		<content:encoded><![CDATA[	<blockquote><p>So, can we resume commenting on last week’s posts? </p></blockquote>
	<p>Yes, with a few provisos: all quarrels <i>must</i> be left off, and any unanswered insults from last week must <i>must</i> now be overlooked. Very off-topic comments should also be ignored.</p>
	<p>Moderation will be a good deal stricter from now on, and responding to a less-than-temperate posts from last week is no excuse for  a less-than-temperate post now.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Brian K</title>
		<link>http://evolutionanddesign.blogsome.com/2006/07/09/new-rules-of-engagement/#comment-481</link>
		<pubDate>Mon, 10 Jul 2006 09:55:28 +0100</pubDate>
		<guid>http://evolutionanddesign.blogsome.com/2006/07/09/new-rules-of-engagement/#comment-481</guid>
					<description>So, can we resume commenting on last week's posts?</description>
		<content:encoded><![CDATA[	<p>So, can we resume commenting on last week&#8217;s posts?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Art G</title>
		<link>http://evolutionanddesign.blogsome.com/2006/07/09/new-rules-of-engagement/#comment-478</link>
		<pubDate>Sun, 09 Jul 2006 23:46:30 +0100</pubDate>
		<guid>http://evolutionanddesign.blogsome.com/2006/07/09/new-rules-of-engagement/#comment-478</guid>
					<description>Hi Allen,

You forgot one rule:

Bad puns, and the inevitable pun fests that follow, will not be permitted.

You probably should report yourself, no?</description>
		<content:encoded><![CDATA[	<p>Hi Allen,</p>
	<p>You forgot one rule:</p>
	<p>Bad puns, and the inevitable pun fests that follow, will not be permitted.</p>
	<p>You probably should report yourself, no?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Hannah</title>
		<link>http://evolutionanddesign.blogsome.com/2006/07/09/new-rules-of-engagement/#comment-477</link>
		<pubDate>Sun, 09 Jul 2006 22:55:15 +0100</pubDate>
		<guid>http://evolutionanddesign.blogsome.com/2006/07/09/new-rules-of-engagement/#comment-477</guid>
					<description>As another btw-- comments &lt;i&gt;do&lt;/i&gt; sometimes get stuck in our spamguard system, so if you post a civil comment and it doesn't appear that may well be the reason. The queue there is checked at intervals, and comments not in violation of our Rules of Engagement released.

It doesn't help to repost the comment, as then we just find multiple copies when we check the queue. </description>
		<content:encoded><![CDATA[	<p>As another btw&#8211; comments <i>do</i> sometimes get stuck in our spamguard system, so if you post a civil comment and it doesn&#8217;t appear that may well be the reason. The queue there is checked at intervals, and comments not in violation of our Rules of Engagement released.</p>
	<p>It doesn&#8217;t help to repost the comment, as then we just find multiple copies when we check the queue.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Don Baccus</title>
		<link>http://evolutionanddesign.blogsome.com/2006/07/09/new-rules-of-engagement/#comment-476</link>
		<pubDate>Sun, 09 Jul 2006 22:21:27 +0100</pubDate>
		<guid>http://evolutionanddesign.blogsome.com/2006/07/09/new-rules-of-engagement/#comment-476</guid>
					<description>&lt;blockquote&gt;&lt;i&gt;Fire at Will...&lt;/i&gt;&lt;/blockquote&gt;
Did you really mean to restart the discussion by inviting &lt;i&gt;ad hom&lt;/i&gt; attacks on Will?  Poor fella, whoever he is! :)

The new rules look good.
</description>
		<content:encoded><![CDATA[	<blockquote><p><i>Fire at Will&#8230;</i></p></blockquote>
	<p>Did you really mean to restart the discussion by inviting <i>ad hom</i> attacks on Will?  Poor fella, whoever he is! :)</p>
	<p>The new rules look good.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Allen MacNeill</title>
		<link>http://evolutionanddesign.blogsome.com/2006/07/09/new-rules-of-engagement/#comment-475</link>
		<pubDate>Sun, 09 Jul 2006 21:52:30 +0100</pubDate>
		<guid>http://evolutionanddesign.blogsome.com/2006/07/09/new-rules-of-engagement/#comment-475</guid>
					<description>And BTW, the boards are now open again. Fire at Will...</description>
		<content:encoded><![CDATA[	<p>And BTW, the boards are now open again. Fire at Will&#8230;
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
