<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Technosailor - Latest Comments in Blog Architecture: Conversation</title><link>http://technosailor.disqus.com/</link><description></description><language>en</language><lastBuildDate>Fri, 14 Jul 2006 16:15:27 -0000</lastBuildDate><item><title>Re: Blog Architecture: Conversation</title><link>http://technosailor.com/2006/07/14/blog-architecture-conversation/#comment-1033356</link><description>I'm real interested to see how this turns out. It's got me thinking about a few other ways to present a blog.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bald Man</dc:creator><pubDate>Fri, 14 Jul 2006 16:15:27 -0000</pubDate></item><item><title>Re: Blog Architecture: Conversation</title><link>http://technosailor.com/2006/07/14/blog-architecture-conversation/#comment-1033355</link><description>Yes, it will be cookie-based so the choice remains persistant. The weakness of this is that if you view on another computer, those preferences won't remain and will have to be set again. I may think about having an option for users to register and then store their settings in the usermeta table. If I go that route, options set in usermeta will override cookie settings.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Aaron</dc:creator><pubDate>Fri, 14 Jul 2006 10:34:08 -0000</pubDate></item><item><title>Re: Blog Architecture: Conversation</title><link>http://technosailor.com/2006/07/14/blog-architecture-conversation/#comment-1033354</link><description>Sounds very interesting, and I can't wait to see how it plays out.&lt;br&gt;&lt;br&gt;I'm most curious about how you're going to handle these different views. Are you going to store a cookie on the users computer that sets their default view?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Nick</dc:creator><pubDate>Fri, 14 Jul 2006 10:31:13 -0000</pubDate></item></channel></rss>