<?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: A Seesmic Issue</title>
	<atom:link href="http://www.loupaglia.com/correlate/2008/03/17/a-seesmic-issue/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.loupaglia.com/correlate/2008/03/17/a-seesmic-issue/</link>
	<description>paglia&#039;s thoughts: &#34;one to negative one&#34; and some noise in between</description>
	<lastBuildDate>Fri, 15 Jan 2010 01:23:08 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Lou Paglia</title>
		<link>http://www.loupaglia.com/correlate/2008/03/17/a-seesmic-issue/comment-page-1/#comment-381</link>
		<dc:creator>Lou Paglia</dc:creator>
		<pubDate>Tue, 18 Mar 2008 10:16:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.loupaglia.com/correlate/2008/03/17/a-seesmic-issue/#comment-381</guid>
		<description>Loic &#187; Thanks. Will do.  Good luck with the rest of development.</description>
		<content:encoded><![CDATA[<div class='microid-5cacc5f30a26befbea1a4ce51a397b43fc6cd773'>Loic &raquo; Thanks. Will do.  Good luck with the rest of development.</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Loic</title>
		<link>http://www.loupaglia.com/correlate/2008/03/17/a-seesmic-issue/comment-page-1/#comment-380</link>
		<dc:creator>Loic</dc:creator>
		<pubDate>Tue, 18 Mar 2008 06:00:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.loupaglia.com/correlate/2008/03/17/a-seesmic-issue/#comment-380</guid>
		<description>Great feedback! We&#039;re actually working hard right now on the email notification server. Thank you for your help, please send us more feedback.</description>
		<content:encoded><![CDATA[<div class='microid-e4bdd0f591e9960aa027a65e2118d2f4ea643b18'>Great feedback! We&#8217;re actually working hard right now on the email notification server. Thank you for your help, please send us more feedback.</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lou Paglia</title>
		<link>http://www.loupaglia.com/correlate/2008/03/17/a-seesmic-issue/comment-page-1/#comment-374</link>
		<dc:creator>Lou Paglia</dc:creator>
		<pubDate>Tue, 18 Mar 2008 02:43:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.loupaglia.com/correlate/2008/03/17/a-seesmic-issue/#comment-374</guid>
		<description>Cathy Brooks &#187; Thanks again for your response.  It is great to &quot;see&quot;, &quot;hear&quot; and &quot;read&quot; your response.  Eagerly awaiting the day you guys decide to come out of alpha.  And I can imagine the scaling issues that you are dealing with if the scaling issues that Twitter has dealt with as of late.  They seems to have made the transition to keep up with their traffic levels and I&#039;m sure you/team will be able to as well.

I look forward to watching your strategy unfold.  For some reason, I&#039;m already envisioning the Seesmic API in full integration within Ning.  Clearly, YouTubes API release may proove some competition in that space if they are truly trying to head into the API of video space and also being fine with other outfits like Ning privatizing on top of it, perhaps integrating with OpenSocial.

Thanks again, and I too look forward to continuing the conversation.</description>
		<content:encoded><![CDATA[<div class='microid-5cacc5f30a26befbea1a4ce51a397b43fc6cd773'>Cathy Brooks &raquo; Thanks again for your response.  It is great to &#8220;see&#8221;, &#8220;hear&#8221; and &#8220;read&#8221; your response.  Eagerly awaiting the day you guys decide to come out of alpha.  And I can imagine the scaling issues that you are dealing with if the scaling issues that Twitter has dealt with as of late.  They seems to have made the transition to keep up with their traffic levels and I&#8217;m sure you/team will be able to as well.</p>
<p>I look forward to watching your strategy unfold.  For some reason, I&#8217;m already envisioning the Seesmic API in full integration within Ning.  Clearly, YouTubes API release may proove some competition in that space if they are truly trying to head into the API of video space and also being fine with other outfits like Ning privatizing on top of it, perhaps integrating with OpenSocial.</p>
<p>Thanks again, and I too look forward to continuing the conversation.</p></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cathy Brooks</title>
		<link>http://www.loupaglia.com/correlate/2008/03/17/a-seesmic-issue/comment-page-1/#comment-373</link>
		<dc:creator>Cathy Brooks</dc:creator>
		<pubDate>Tue, 18 Mar 2008 02:18:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.loupaglia.com/correlate/2008/03/17/a-seesmic-issue/#comment-373</guid>
		<description>Greetings Lou, and thanks for re-enabling comments. (-:

As I mentioned in my video post - you have hit the nail on the head. To clarify, Seesmic is currently still in closed alpha. This means that to &quot;come play&quot; you need an invite code, which you can either get by signing up on the site or by emailing someone at Seesmic (like cathy[at]seesmic[dot]com, for example ). The reason for this is several fold - mostly to make sure we&#039;re handling scaling issues properly and also to ensure that we have built solid technology protections in place for things like copyright, privacy etc...

Once we kick open the doors to the world what you&#039;ll find is that rather than trying to be THE destination site, Seesmic is on track to be A destination site. Our goal - to serve as the engine powering the world&#039;s online video conversations.

So yes, we&#039;ll enable you to share your Seesmic content to many other places and allow others - whether registered on Seesmic or not - to participate in those conversations.

For the more detailed response here&#039;s the post: http://seesmic.com/v/2myOkMBQvJ

Let&#039;s keep this conversation going - feel free to email or post Seesmics with other thoughts and ideas ... and of course to all of your readers, feel free to contact me directly if you wish to come test things out for yourself!</description>
		<content:encoded><![CDATA[<div class='microid-d81d75c24bb84ff460d3c26e0333b99846d74f69'>Greetings Lou, and thanks for re-enabling comments. (-:</p>
<p>As I mentioned in my video post &#8211; you have hit the nail on the head. To clarify, Seesmic is currently still in closed alpha. This means that to &#8220;come play&#8221; you need an invite code, which you can either get by signing up on the site or by emailing someone at Seesmic (like cathy[at]seesmic[dot]com, for example ). The reason for this is several fold &#8211; mostly to make sure we&#8217;re handling scaling issues properly and also to ensure that we have built solid technology protections in place for things like copyright, privacy etc&#8230;</p>
<p>Once we kick open the doors to the world what you&#8217;ll find is that rather than trying to be THE destination site, Seesmic is on track to be A destination site. Our goal &#8211; to serve as the engine powering the world&#8217;s online video conversations.</p>
<p>So yes, we&#8217;ll enable you to share your Seesmic content to many other places and allow others &#8211; whether registered on Seesmic or not &#8211; to participate in those conversations.</p>
<p>For the more detailed response here&#8217;s the post: <a href="http://seesmic.com/v/2myOkMBQvJ" rel="nofollow">http://seesmic.com/v/2myOkMBQvJ</a></p>
<p>Let&#8217;s keep this conversation going &#8211; feel free to email or post Seesmics with other thoughts and ideas &#8230; and of course to all of your readers, feel free to contact me directly if you wish to come test things out for yourself!</p></div>
]]></content:encoded>
	</item>
</channel>
</rss>
