<?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: Flurry of activity on the Deki front</title>
	<atom:link href="http://www.bitstampede.com/2009/01/19/flurry-of-activity-on-the-deki-front/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bitstampede.com/2009/01/19/flurry-of-activity-on-the-deki-front/</link>
	<description>Bits on the rampage: Eric Shepherd's blog.</description>
	<lastBuildDate>Tue, 27 Jul 2010 00:37:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: reed</title>
		<link>http://www.bitstampede.com/2009/01/19/flurry-of-activity-on-the-deki-front/comment-page-1/#comment-82931</link>
		<dc:creator>reed</dc:creator>
		<pubDate>Wed, 21 Jan 2009 15:53:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2009/01/19/flurry-of-activity-on-the-deki-front/#comment-82931</guid>
		<description>&lt;cite&gt;The reason we explicitly chose to go with HTTPS for all pages is because Deki doesn’t support it just for auth. The site should be more responsive if we can use it for auth only. This assumes that MindTouch’s solution is secure and doesn’t include private data in the cookies and so forth. We’ll see what they do.&lt;/cite&gt;

So, I think the best solution would be to use http for logged-out users and require SSL for logged-in users. That seems reasonable and keeps response time for most people down.</description>
		<content:encoded><![CDATA[<p><cite>The reason we explicitly chose to go with HTTPS for all pages is because Deki doesn’t support it just for auth. The site should be more responsive if we can use it for auth only. This assumes that MindTouch’s solution is secure and doesn’t include private data in the cookies and so forth. We’ll see what they do.</cite></p>
<p>So, I think the best solution would be to use http for logged-out users and require SSL for logged-in users. That seems reasonable and keeps response time for most people down.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sheppy</title>
		<link>http://www.bitstampede.com/2009/01/19/flurry-of-activity-on-the-deki-front/comment-page-1/#comment-82930</link>
		<dc:creator>sheppy</dc:creator>
		<pubDate>Tue, 20 Jan 2009 01:20:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2009/01/19/flurry-of-activity-on-the-deki-front/#comment-82930</guid>
		<description>Woo -- Deki now has a Wiki.inclusions feature that returns a list of the pages in the inclusion chain, so you can see who included you.  This will be enormously useful!</description>
		<content:encoded><![CDATA[<p>Woo &#8212; Deki now has a Wiki.inclusions feature that returns a list of the pages in the inclusion chain, so you can see who included you.  This will be enormously useful!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sheppy</title>
		<link>http://www.bitstampede.com/2009/01/19/flurry-of-activity-on-the-deki-front/comment-page-1/#comment-82929</link>
		<dc:creator>sheppy</dc:creator>
		<pubDate>Tue, 20 Jan 2009 01:19:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2009/01/19/flurry-of-activity-on-the-deki-front/#comment-82929</guid>
		<description>Steve -- yes, that&#039;s why I used words like &quot;targeted.&quot;  We&#039;ll see what happens; still, it&#039;s exciting to see this stuff being looked at!</description>
		<content:encoded><![CDATA[<p>Steve &#8212; yes, that&#8217;s why I used words like &#8220;targeted.&#8221;  We&#8217;ll see what happens; still, it&#8217;s exciting to see this stuff being looked at!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sheppy</title>
		<link>http://www.bitstampede.com/2009/01/19/flurry-of-activity-on-the-deki-front/comment-page-1/#comment-82928</link>
		<dc:creator>sheppy</dc:creator>
		<pubDate>Tue, 20 Jan 2009 01:17:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2009/01/19/flurry-of-activity-on-the-deki-front/#comment-82928</guid>
		<description>The reason we explicitly chose to go with HTTPS for all pages is because Deki doesn&#039;t support it just for auth.  The site should be more responsive if we can use it for auth only.  This assumes that MindTouch&#039;s solution is secure and doesn&#039;t include private data in the cookies and so forth.  We&#039;ll see what they do.</description>
		<content:encoded><![CDATA[<p>The reason we explicitly chose to go with HTTPS for all pages is because Deki doesn&#8217;t support it just for auth.  The site should be more responsive if we can use it for auth only.  This assumes that MindTouch&#8217;s solution is secure and doesn&#8217;t include private data in the cookies and so forth.  We&#8217;ll see what they do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: reed</title>
		<link>http://www.bitstampede.com/2009/01/19/flurry-of-activity-on-the-deki-front/comment-page-1/#comment-82927</link>
		<dc:creator>reed</dc:creator>
		<pubDate>Tue, 20 Jan 2009 00:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2009/01/19/flurry-of-activity-on-the-deki-front/#comment-82927</guid>
		<description>&lt;cite&gt;The ability to use HTTPS for authentication, then use HTTP for everything else is also on the Lyons list.&lt;/cite&gt;
Bug 397125 mentions that we explicitly chose to go with HTTPS for all pages. Will the above change prevent that in some way?</description>
		<content:encoded><![CDATA[<p><cite>The ability to use HTTPS for authentication, then use HTTP for everything else is also on the Lyons list.</cite><br />
Bug 397125 mentions that we explicitly chose to go with HTTPS for all pages. Will the above change prevent that in some way?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Bjorg</title>
		<link>http://www.bitstampede.com/2009/01/19/flurry-of-activity-on-the-deki-front/comment-page-1/#comment-82926</link>
		<dc:creator>Steve Bjorg</dc:creator>
		<pubDate>Mon, 19 Jan 2009 22:14:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2009/01/19/flurry-of-activity-on-the-deki-front/#comment-82926</guid>
		<description>To clarify, while these bugs were assigned to devs for the &quot;Lyons&quot; release, they may still get punted for various reasons.  However, they are being investigated and everything we can fix, will be fixed.  Whatever doesn&#039;t make it, will be retargeted for Lyons+, which will following 2-3 months after Lyons ships.</description>
		<content:encoded><![CDATA[<p>To clarify, while these bugs were assigned to devs for the &#8220;Lyons&#8221; release, they may still get punted for various reasons.  However, they are being investigated and everything we can fix, will be fixed.  Whatever doesn&#8217;t make it, will be retargeted for Lyons+, which will following 2-3 months after Lyons ships.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
