<?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: Why I&#8217;ll Never Use Outlook</title>
	<atom:link href="http://www.fibiger.org/2003/02/147/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fibiger.org/2003/02/147/</link>
	<description>It crossed my mind that you might consider that a possibility...</description>
	<lastBuildDate>Mon, 20 Apr 2009 00:36:37 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: spivey</title>
		<link>http://www.fibiger.org/2003/02/147/comment-page-1/#comment-98</link>
		<dc:creator>spivey</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.fibiger.org/2003/02/147/#comment-98</guid>
		<description>um... that&#039;s not so good.</description>
		<content:encoded><![CDATA[<p>um&#8230; that&#8217;s not so good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.fibiger.org/2003/02/147/comment-page-1/#comment-99</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.fibiger.org/2003/02/147/#comment-99</guid>
		<description>Brilliant and EVIL!</description>
		<content:encoded><![CDATA[<p>Brilliant and EVIL!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: leonard</title>
		<link>http://www.fibiger.org/2003/02/147/comment-page-1/#comment-100</link>
		<dc:creator>leonard</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.fibiger.org/2003/02/147/#comment-100</guid>
		<description>watch out andre! &gt;;)</description>
		<content:encoded><![CDATA[<p>watch out andre! >;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Reinacker</title>
		<link>http://www.fibiger.org/2003/02/147/comment-page-1/#comment-101</link>
		<dc:creator>Greg Reinacker</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.fibiger.org/2003/02/147/#comment-101</guid>
		<description>I have posted comments related to NewsGator and this issue at &lt;a href=&quot;http://www.newsgator.com/news/archive.aspx?post=3.&quot;&gt;http://www.newsgator.com/news/archive.aspx?post=3.&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I have posted comments related to NewsGator and this issue at <a href="http://www.newsgator.com/news/archive.aspx?post=3."></a><a href="http://www.newsgator.com/news/archive.aspx?post=3" rel="nofollow">http://www.newsgator.com/news/archive.aspx?post=3</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Kearney</title>
		<link>http://www.fibiger.org/2003/02/147/comment-page-1/#comment-102</link>
		<dc:creator>Bill Kearney</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.fibiger.org/2003/02/147/#comment-102</guid>
		<description>This is not a new issue.  It&#039;s been raised many times in the past.  Putting scripting inside RSS items it evil.  Anything that handles RSS should attempt to neuter said scripts if it finds it.  This is an extra, and possibly tedious, step but one that cannot be reasonably argued against.  The one argument being a customized channel that has legitimate intentions.  This isn&#039;t an unreasonable idea.  But it seems like it&#039;d be something that required a per-feed preference setting of some kind that allowed that channel to get away with that sort of stuff.

This opens the can of worms about digitally signed scripts and embedded code.  If a feed intended to have such wonderful things done that it required scripting then it aught then take the bigger step up to using PKI.  An ugly analogy, perhaps, is if you want promiscuity then bring protection.</description>
		<content:encoded><![CDATA[<p>This is not a new issue.  It&#8217;s been raised many times in the past.  Putting scripting inside RSS items it evil.  Anything that handles RSS should attempt to neuter said scripts if it finds it.  This is an extra, and possibly tedious, step but one that cannot be reasonably argued against.  The one argument being a customized channel that has legitimate intentions.  This isn&#8217;t an unreasonable idea.  But it seems like it&#8217;d be something that required a per-feed preference setting of some kind that allowed that channel to get away with that sort of stuff.</p>
<p>This opens the can of worms about digitally signed scripts and embedded code.  If a feed intended to have such wonderful things done that it required scripting then it aught then take the bigger step up to using PKI.  An ugly analogy, perhaps, is if you want promiscuity then bring protection.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andy</title>
		<link>http://www.fibiger.org/2003/02/147/comment-page-1/#comment-103</link>
		<dc:creator>andy</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.fibiger.org/2003/02/147/#comment-103</guid>
		<description>Still, the problem seems to me to rest solely with outlook.  Why should any &#039;foreign&#039; script be allowed to perform operations like reading the address book or sending email without the user&#039;s permission.

Seems to me that applying some logical security ideas in the development of Outlook would save everyone a lot of time and effort.  I understand MS wants there to be the possibility of &#039;active content&#039;, but that is an issue web browsers have been dealing with for years.  Why not use some of the same frameworks in Outlook?</description>
		<content:encoded><![CDATA[<p>Still, the problem seems to me to rest solely with outlook.  Why should any &#8216;foreign&#8217; script be allowed to perform operations like reading the address book or sending email without the user&#8217;s permission.</p>
<p>Seems to me that applying some logical security ideas in the development of Outlook would save everyone a lot of time and effort.  I understand MS wants there to be the possibility of &#8216;active content&#8217;, but that is an issue web browsers have been dealing with for years.  Why not use some of the same frameworks in Outlook?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
