<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Ildhavet - Latest Comments in To Disqus or not to Disqus</title><link>http://kaplak.disqus.com/</link><description>Morten Blaabjerg's Personlige Blog</description><atom:link href="https://kaplak.disqus.com/to_disqus_or_not_to_disqus_46/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 12 Jun 2008 03:18:05 -0000</lastBuildDate><item><title>Re: To Disqus or not to Disqus</title><link>http://blog.kaplak.com/2008/06/10/to-disqus-or-not-to-disqus/#comment-2716834</link><description>&lt;p&gt;Yes, it's a priority.&lt;br&gt;&lt;br&gt;&lt;br&gt;You can either add the parameter or just not preview the post while  &lt;br&gt;&lt;br&gt;making drafts.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">obscurelyfamous</dc:creator><pubDate>Thu, 12 Jun 2008 03:18:05 -0000</pubDate></item><item><title>Re: To Disqus or not to Disqus</title><link>http://blog.kaplak.com/2008/06/10/to-disqus-or-not-to-disqus/#comment-2716833</link><description>&lt;p&gt;Any timeline on the next version? Will I have to add the parameter to every post in order to avoid it showing up - or simply live with going in to the community page and removing pages there manually?&lt;br&gt;&lt;br&gt;&lt;br&gt;It gets me a bit uncomfortable, that readers may get incomplete posts or posts subject to later changes (I often write blogposts days, sometimes weeks or months in advance)&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Morten Blaabjerg</dc:creator><pubDate>Thu, 12 Jun 2008 00:47:17 -0000</pubDate></item><item><title>Re: To Disqus or not to Disqus</title><link>http://blog.kaplak.com/2008/06/10/to-disqus-or-not-to-disqus/#comment-2716832</link><description>&lt;p&gt;A page view sends a request out to Disqus to tell us that we need to create a thread for a particular page.&lt;br&gt;&lt;br&gt;&lt;br&gt;Unfortunately, previewing a post in WordPress is the same as viewing a published post. Disqus doesn't discriminate against those types.&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;In the next version, we will attempt to determine whether the post has a published status and set the parameter automatically.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">obscurelyfamous</dc:creator><pubDate>Thu, 12 Jun 2008 00:27:11 -0000</pubDate></item><item><title>Re: To Disqus or not to Disqus</title><link>http://blog.kaplak.com/2008/06/10/to-disqus-or-not-to-disqus/#comment-2716831</link><description>&lt;p&gt;Couldn't find out how to contact Disqus support, so sent a tweet to Daniel Ha, co-founder of Disqus, and got this one back : &lt;a href="http://twitter.com/danielha/statuses/832431033" rel="nofollow noopener" target="_blank" title="http://twitter.com/danielha/statuses/832431033"&gt;http://twitter.com/danielha/statuses/832431033&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Daniel also supplied a Javascript parameter by email, which could help avoid this. I still don't understand however, why or how previewed posts in WP could, should or ought to even appear in Kaplak's page on Disqus.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Morten Blaabjerg</dc:creator><pubDate>Wed, 11 Jun 2008 23:05:28 -0000</pubDate></item><item><title>Re: To Disqus or not to Disqus</title><link>http://blog.kaplak.com/2008/06/10/to-disqus-or-not-to-disqus/#comment-2716830</link><description>&lt;p&gt;Alright, this is mega-uncool. Just found out that Disqus seems to index un-published posts in WordPress too. This is a major boo, and if not fixed ASAP will definitely get me off the service.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Morten Blaabjerg</dc:creator><pubDate>Wed, 11 Jun 2008 22:23:11 -0000</pubDate></item></channel></rss>