<?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: Liveperson.net: Support to shoot yourself in the foot with</title>
	<atom:link href="http://quasistoic.org/ts/archives/2006/08/14/liveperson-actually-dead-drone/feed/" rel="self" type="application/rss+xml" />
	<link>http://quasistoic.org/ts/archives/2006/08/14/liveperson-actually-dead-drone/</link>
	<description>but still a permanent idiot</description>
	<lastBuildDate>Thu, 09 Feb 2012 05:00:50 -0500</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Barbie</title>
		<link>http://quasistoic.org/ts/archives/2006/08/14/liveperson-actually-dead-drone/comment-page-1/#comment-2964</link>
		<dc:creator>Barbie</dc:creator>
		<pubDate>Wed, 14 Feb 2007 08:28:23 +0000</pubDate>
		<guid isPermaLink="false">http://quasistoic.org/ts/archives/2006/08/14/liveperson-actually-dead-drone/#comment-2964</guid>
		<description>You can find a lot of reviews about StartLogic on the website http://www.hothosting.info/en. Also, StartLogic is trusted by many of its customers. Obviously, there can not be a very perfect host, since these hosts are of many different features. 

The clients should buy a host which meets their needs perfectly. For example, if a person has some experiences with Linux, he or she may choose the host which supports ssh so that it can achieve its perfect performances. Moreover, the e-shop host users can choose a kind production which could provides more after-services.

Go to  http://www.hothosting.info/en and have a look, there must be some suitable methods for you in choosing the right hosts. You will know more about the web hosting!Enjoy!</description>
		<content:encoded><![CDATA[<p>You can find a lot of reviews about StartLogic on the website <a href="http://www.hothosting.info/en" rel="nofollow">http://www.hothosting.info/en</a>. Also, StartLogic is trusted by many of its customers. Obviously, there can not be a very perfect host, since these hosts are of many different features. </p>
<p>The clients should buy a host which meets their needs perfectly. For example, if a person has some experiences with Linux, he or she may choose the host which supports ssh so that it can achieve its perfect performances. Moreover, the e-shop host users can choose a kind production which could provides more after-services.</p>
<p>Go to  <a href="http://www.hothosting.info/en" rel="nofollow">http://www.hothosting.info/en</a> and have a look, there must be some suitable methods for you in choosing the right hosts. You will know more about the web hosting!Enjoy!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny Dawson</title>
		<link>http://quasistoic.org/ts/archives/2006/08/14/liveperson-actually-dead-drone/comment-page-1/#comment-2962</link>
		<dc:creator>Danny Dawson</dc:creator>
		<pubDate>Wed, 06 Dec 2006 22:36:54 +0000</pubDate>
		<guid isPermaLink="false">http://quasistoic.org/ts/archives/2006/08/14/liveperson-actually-dead-drone/#comment-2962</guid>
		<description>The wp-hackers list pointed me to this bug report:
http://trac.wordpress.org/ticket/1786

which appears to have been resolved by using wp_die() instead of die() in the wp-comments-post.php file. I suppose wp_die() must be hookable.

These changes made it into the wordpress trunk on July 5th, but somehow didn&#039;t make it into the 2.0.5 release on October 27th. It looks like they still haven&#039;t made it into the 2.0 branch, and thus probably won&#039;t make it into the 2.0.6 tag, which was apparently due 5 days ago.

Looking further into this, the wp_die() function is slated for the 2.1 release, which does not yet have a date on the official roadmap.</description>
		<content:encoded><![CDATA[<p>The wp-hackers list pointed me to this bug report:<br />
<a href="http://trac.wordpress.org/ticket/1786" rel="nofollow">http://trac.wordpress.org/ticket/1786</a></p>
<p>which appears to have been resolved by using wp_die() instead of die() in the wp-comments-post.php file. I suppose wp_die() must be hookable.</p>
<p>These changes made it into the wordpress trunk on July 5th, but somehow didn&#8217;t make it into the 2.0.5 release on October 27th. It looks like they still haven&#8217;t made it into the 2.0 branch, and thus probably won&#8217;t make it into the 2.0.6 tag, which was apparently due 5 days ago.</p>
<p>Looking further into this, the wp_die() function is slated for the 2.1 release, which does not yet have a date on the official roadmap.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: picardo</title>
		<link>http://quasistoic.org/ts/archives/2006/08/14/liveperson-actually-dead-drone/comment-page-1/#comment-2960</link>
		<dc:creator>picardo</dc:creator>
		<pubDate>Wed, 06 Dec 2006 21:32:12 +0000</pubDate>
		<guid isPermaLink="false">http://quasistoic.org/ts/archives/2006/08/14/liveperson-actually-dead-drone/#comment-2960</guid>
		<description>Hi, I came across your post on Wordpress forum about the error handling fix.

http://wordpress.org/support/topic/54505

You wrote that you would check with the wp hackers to see if there was anything forthcoming from them.

(A quick check showed, this blog also exhibits the same error. You&#039;d be the first to implement the fix no? Does that mean there isn&#039;t anything??)</description>
		<content:encoded><![CDATA[<p>Hi, I came across your post on WordPress forum about the error handling fix.</p>
<p><a href="http://wordpress.org/support/topic/54505" rel="nofollow">http://wordpress.org/support/topic/54505</a></p>
<p>You wrote that you would check with the wp hackers to see if there was anything forthcoming from them.</p>
<p>(A quick check showed, this blog also exhibits the same error. You&#8217;d be the first to implement the fix no? Does that mean there isn&#8217;t anything??)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

