<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Joost Is Error-Prone</title>
	<atom:link href="http://newteevee.com/2007/05/03/joost-is-error-prone/feed/" rel="self" type="application/rss+xml" />
	<link>http://newteevee.com/2007/05/03/joost-is-error-prone/</link>
	<description>NewTeeVee</description>
	<lastBuildDate>Sat, 21 Nov 2009 16:38:56 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Joost Sues Volpi for Taking Tech to Make a Web Version of Skype</title>
		<link>http://newteevee.com/2007/05/03/joost-is-error-prone/#comment-268593</link>
		<dc:creator>Joost Sues Volpi for Taking Tech to Make a Web Version of Skype</dc:creator>
		<pubDate>Fri, 18 Sep 2009 16:14:11 +0000</pubDate>
		<guid isPermaLink="false">http://newteevee.wordpress.com/2007/05/03/joost-is-error-prone/#comment-268593</guid>
		<description>&lt;p&gt;[...] to Volpi&#8217;s credit, the original software version of Joost was extremely buggy. Though he may not have gained any market share with it, or been able to take advantage of the [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] to Volpi&#8217;s credit, the original software version of Joost was extremely buggy. Though he may not have gained any market share with it, or been able to take advantage of the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heike</title>
		<link>http://newteevee.com/2007/05/03/joost-is-error-prone/#comment-240247</link>
		<dc:creator>Heike</dc:creator>
		<pubDate>Sat, 28 Jun 2008 03:13:27 +0000</pubDate>
		<guid isPermaLink="false">http://newteevee.wordpress.com/2007/05/03/joost-is-error-prone/#comment-240247</guid>
		<description>&lt;p&gt;just call the service center as many times as you can&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>just call the service center as many times as you can</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joost Site Experiencing &#8216;Unprecedented&#8217; Downtime &#171; NewTeeVee</title>
		<link>http://newteevee.com/2007/05/03/joost-is-error-prone/#comment-232311</link>
		<dc:creator>Joost Site Experiencing &#8216;Unprecedented&#8217; Downtime &#171; NewTeeVee</dc:creator>
		<pubDate>Fri, 22 Feb 2008 16:52:48 +0000</pubDate>
		<guid isPermaLink="false">http://newteevee.wordpress.com/2007/05/03/joost-is-error-prone/#comment-232311</guid>
		<description>&lt;p&gt;[...] 8, the site has been down on a daily basis, for a total of more than five hours. We&#8217;ve had technical difficulties with Joost in the past, and the company recently fired its CTO, but what seems to be [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] 8, the site has been down on a daily basis, for a total of more than five hours. We&#8217;ve had technical difficulties with Joost in the past, and the company recently fired its CTO, but what seems to be [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CareBear</title>
		<link>http://newteevee.com/2007/05/03/joost-is-error-prone/#comment-190531</link>
		<dc:creator>CareBear</dc:creator>
		<pubDate>Sun, 09 Dec 2007 16:25:25 +0000</pubDate>
		<guid isPermaLink="false">http://newteevee.wordpress.com/2007/05/03/joost-is-error-prone/#comment-190531</guid>
		<description>&lt;p&gt;the manufacturer should fix the bugz on Joost&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>the manufacturer should fix the bugz on Joost</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Getting Hitched: Traditional CDN and P2P architectures &#171;</title>
		<link>http://newteevee.com/2007/05/03/joost-is-error-prone/#comment-3511</link>
		<dc:creator>Getting Hitched: Traditional CDN and P2P architectures &#171;</dc:creator>
		<pubDate>Fri, 25 May 2007 16:51:55 +0000</pubDate>
		<guid isPermaLink="false">http://newteevee.wordpress.com/2007/05/03/joost-is-error-prone/#comment-3511</guid>
		<description>&lt;p&gt;[...] improve performance in a asymmetric world is to deploy network-based server resources, aka a CDN! Joost is a big victim of this [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] improve performance in a asymmetric world is to deploy network-based server resources, aka a CDN! Joost is a big victim of this [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NewTeeVee &#187; Get your Joost Invites Now&#8230; Almost Unlimited</title>
		<link>http://newteevee.com/2007/05/03/joost-is-error-prone/#comment-3508</link>
		<dc:creator>NewTeeVee &#187; Get your Joost Invites Now&#8230; Almost Unlimited</dc:creator>
		<pubDate>Mon, 07 May 2007 20:13:41 +0000</pubDate>
		<guid isPermaLink="false">http://newteevee.wordpress.com/2007/05/03/joost-is-error-prone/#comment-3508</guid>
		<description>&lt;p&gt;[...] company says its server situation has improved since last week. It&#8217;s still a bit buggy on our end, but [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] company says its server situation has improved since last week. It&#8217;s still a bit buggy on our end, but [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joost Beta Faces Problems &#171; inbabble.com</title>
		<link>http://newteevee.com/2007/05/03/joost-is-error-prone/#comment-3510</link>
		<dc:creator>Joost Beta Faces Problems &#171; inbabble.com</dc:creator>
		<pubDate>Mon, 07 May 2007 16:48:59 +0000</pubDate>
		<guid isPermaLink="false">http://newteevee.wordpress.com/2007/05/03/joost-is-error-prone/#comment-3510</guid>
		<description>&lt;p&gt;[...] include &#8220;Unable to connect to network” or “An unknown error occurred, sorry” and the Joost [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] include &#8220;Unable to connect to network” or “An unknown error occurred, sorry” and the Joost [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Akshun J</title>
		<link>http://newteevee.com/2007/05/03/joost-is-error-prone/#comment-3507</link>
		<dc:creator>Akshun J</dc:creator>
		<pubDate>Mon, 07 May 2007 10:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://newteevee.wordpress.com/2007/05/03/joost-is-error-prone/#comment-3507</guid>
		<description>&lt;p&gt;Joost growing pains...  Wonder if there will be a linux client after all this?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Joost growing pains&#8230;  Wonder if there will be a linux client after all this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wayne</title>
		<link>http://newteevee.com/2007/05/03/joost-is-error-prone/#comment-3505</link>
		<dc:creator>Wayne</dc:creator>
		<pubDate>Sun, 06 May 2007 16:56:56 +0000</pubDate>
		<guid isPermaLink="false">http://newteevee.wordpress.com/2007/05/03/joost-is-error-prone/#comment-3505</guid>
		<description>&lt;p&gt;Do these problems show up on all platforms or just OS X?  Most of the posts I have seen seem to point toward a Mac client issue, although I haven&#039;t read the thread linked in this article.&lt;/p&gt;

&lt;p&gt;On a separate note a couple people said they had extra invites, if you still have any left can I get one?&lt;/p&gt;

&lt;p&gt;Thanks,&lt;/p&gt;

&lt;p&gt;Wayne&lt;/p&gt;

&lt;p&gt;Wayne@knownGood.com&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Do these problems show up on all platforms or just OS X?  Most of the posts I have seen seem to point toward a Mac client issue, although I haven&#8217;t read the thread linked in this article.</p>
<p>On a separate note a couple people said they had extra invites, if you still have any left can I get one?</p>
<p>Thanks,</p>
<p>Wayne</p>
<p><a href="mailto:Wayne@knownGood.com">Wayne@knownGood.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray</title>
		<link>http://newteevee.com/2007/05/03/joost-is-error-prone/#comment-3509</link>
		<dc:creator>Ray</dc:creator>
		<pubDate>Sun, 06 May 2007 01:18:32 +0000</pubDate>
		<guid isPermaLink="false">http://newteevee.wordpress.com/2007/05/03/joost-is-error-prone/#comment-3509</guid>
		<description>&lt;p&gt;Matt I have several invites...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Matt I have several invites&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: routeip</title>
		<link>http://newteevee.com/2007/05/03/joost-is-error-prone/#comment-3506</link>
		<dc:creator>routeip</dc:creator>
		<pubDate>Sat, 05 May 2007 17:01:10 +0000</pubDate>
		<guid isPermaLink="false">http://newteevee.wordpress.com/2007/05/03/joost-is-error-prone/#comment-3506</guid>
		<description>&lt;p&gt;Does anyone have an extra Joost invite they wouldn&#039;t mind giving away.  I need one.  Thanks,&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Does anyone have an extra Joost invite they wouldn&#8217;t mind giving away.  I need one.  Thanks,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Hendry</title>
		<link>http://newteevee.com/2007/05/03/joost-is-error-prone/#comment-3502</link>
		<dc:creator>Matt Hendry</dc:creator>
		<pubDate>Fri, 04 May 2007 15:25:41 +0000</pubDate>
		<guid isPermaLink="false">http://newteevee.wordpress.com/2007/05/03/joost-is-error-prone/#comment-3502</guid>
		<description>&lt;p&gt;Remember Joost is still in limited invite only BETA for a reason and there are bound to be errors in a servive that is its still being activly developed and bugs are found on a daily basis as the Joost developers optimise the code in the client and backend services  and try roll out new features.&lt;/p&gt;

&lt;p&gt;Because Joost  is Hybrid p2p they may have scaling issues and they still use standard HTTP for the long tail servers that might be getting slammed to top up bandwidth needed to serve the streams with the influx of new users now the BETA been expanded .&lt;/p&gt;

&lt;p&gt;Please understand this is part of the whole BETA process and the best way for users to help the developers out is to make sure you submit bug reports and feature requests [&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Remember Joost is still in limited invite only BETA for a reason and there are bound to be errors in a servive that is its still being activly developed and bugs are found on a daily basis as the Joost developers optimise the code in the client and backend services  and try roll out new features.</p>
<p>Because Joost  is Hybrid p2p they may have scaling issues and they still use standard HTTP for the long tail servers that might be getting slammed to top up bandwidth needed to serve the streams with the influx of new users now the BETA been expanded .</p>
<p>Please understand this is part of the whole BETA process and the best way for users to help the developers out is to make sure you submit bug reports and feature requests [</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daisy Whitney</title>
		<link>http://newteevee.com/2007/05/03/joost-is-error-prone/#comment-3503</link>
		<dc:creator>Daisy Whitney</dc:creator>
		<pubDate>Fri, 04 May 2007 15:02:09 +0000</pubDate>
		<guid isPermaLink="false">http://newteevee.wordpress.com/2007/05/03/joost-is-error-prone/#comment-3503</guid>
		<description>&lt;p&gt;I&#039;ve had loads of trouble with the service too, needing to uninstall and reinstall several times. True, it&#039;s a beta service, but Joost hasn&#039;t exactly been quiet about it. Joost has lined up 32 advertisers and has signed deals with major content providers and continues to issue press releases about each deal. So it seems natural the service would come under greater scrutiny when it doesn&#039;t work, and frankly, it doesn&#039;t work well.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve had loads of trouble with the service too, needing to uninstall and reinstall several times. True, it&#8217;s a beta service, but Joost hasn&#8217;t exactly been quiet about it. Joost has lined up 32 advertisers and has signed deals with major content providers and continues to issue press releases about each deal. So it seems natural the service would come under greater scrutiny when it doesn&#8217;t work, and frankly, it doesn&#8217;t work well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: E.T.Cook</title>
		<link>http://newteevee.com/2007/05/03/joost-is-error-prone/#comment-3490</link>
		<dc:creator>E.T.Cook</dc:creator>
		<pubDate>Fri, 04 May 2007 14:56:51 +0000</pubDate>
		<guid isPermaLink="false">http://newteevee.wordpress.com/2007/05/03/joost-is-error-prone/#comment-3490</guid>
		<description>&lt;p&gt;I have quite a few joost invites, hit me up Liz, and I can get them your way.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I have quite a few joost invites, hit me up Liz, and I can get them your way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joost, She Is Dying</title>
		<link>http://newteevee.com/2007/05/03/joost-is-error-prone/#comment-3491</link>
		<dc:creator>Joost, She Is Dying</dc:creator>
		<pubDate>Fri, 04 May 2007 14:18:05 +0000</pubDate>
		<guid isPermaLink="false">http://newteevee.wordpress.com/2007/05/03/joost-is-error-prone/#comment-3491</guid>
		<description>&lt;p&gt;[...] Joost is Error Prone [NewTeeVee]  tr { border: 0px } td { cellborder: 10px} table { border: 1px solid black } [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Joost is Error Prone [NewTeeVee]  tr { border: 0px } td { cellborder: 10px} table { border: 1px solid black } [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SELaplana</title>
		<link>http://newteevee.com/2007/05/03/joost-is-error-prone/#comment-3495</link>
		<dc:creator>SELaplana</dc:creator>
		<pubDate>Fri, 04 May 2007 05:56:33 +0000</pubDate>
		<guid isPermaLink="false">http://newteevee.wordpress.com/2007/05/03/joost-is-error-prone/#comment-3495</guid>
		<description>&lt;p&gt;i experienced the same. When I email the support team, only the engine replied me.....&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>i experienced the same. When I email the support team, only the engine replied me&#8230;..</p>
]]></content:encoded>
	</item>
</channel>
</rss>
