<?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"
	>
<channel>
	<title>Comments on: Here&#8217;s a few - chew on this for awhile&#8230;&#8230;</title>
	<atom:link href="http://blog.broadbandmechanics.com/2007/02/heres-a-few-chew-on-this-for-awhile/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.broadbandmechanics.com/2007/02/heres-a-few-chew-on-this-for-awhile</link>
	<description>Digital Lifestyle Aggregation - helping to establish open source infrastructure</description>
	<pubDate>Mon, 06 Oct 2008 21:36:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Jason DeFillippo</title>
		<link>http://blog.broadbandmechanics.com/2007/02/heres-a-few-chew-on-this-for-awhile#comment-238958</link>
		<dc:creator>Jason DeFillippo</dc:creator>
		<pubDate>Thu, 22 Feb 2007 08:49:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.broadbandmechanics.com/2007/02/heres-a-few-chew-on-this-for-awhile#comment-238958</guid>
		<description>So I'd also like to point out that there should be distinctions between IMG tag widgets and JS widgets and REST widgets. There are also distinctions between logic levels of widgets. 

I did remember another site that I think was a predecessor to blogrolling and that was Haloscan. They had the comment market locked when I started and they were a JS widget with advanced logic. It just had such horrific downtime that it was hated a lot by the bloggers. Also Haloscan didnt' have a public face. I was a one man operation so all my users had my phone number and email address. I had the Sifry method down before Sifry if I'm not mistaken ;-)

JS widget providers need to take special care to write extremely delicate logic to fail fast if their DB or scripting lang doesn't respond in say 1500ms. Anyway, I can expound on this for hours...

Cheers.</description>
		<content:encoded><![CDATA[<p>So I&#8217;d also like to point out that there should be distinctions between IMG tag widgets and JS widgets and REST widgets. There are also distinctions between logic levels of widgets. </p>
<p>I did remember another site that I think was a predecessor to blogrolling and that was Haloscan. They had the comment market locked when I started and they were a JS widget with advanced logic. It just had such horrific downtime that it was hated a lot by the bloggers. Also Haloscan didnt&#8217; have a public face. I was a one man operation so all my users had my phone number and email address. I had the Sifry method down before Sifry if I&#8217;m not mistaken <img src='http://blog.broadbandmechanics.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>JS widget providers need to take special care to write extremely delicate logic to fail fast if their DB or scripting lang doesn&#8217;t respond in say 1500ms. Anyway, I can expound on this for hours&#8230;</p>
<p>Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason D-</title>
		<link>http://blog.broadbandmechanics.com/2007/02/heres-a-few-chew-on-this-for-awhile#comment-238957</link>
		<dc:creator>Jason D-</dc:creator>
		<pubDate>Wed, 21 Feb 2007 23:07:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.broadbandmechanics.com/2007/02/heres-a-few-chew-on-this-for-awhile#comment-238957</guid>
		<description>Just for the record, I didn't blow you off. It was an ambitious design for one guy to handle with no resources and at the time no job. Money trumped over vision in this case. It wasn't a purposeful thing. I admired the vision but it was too far out of my personal area of "can-do".

And I think if you want to call Blogrolling the first widget it should be with the caveat that it was the first intelligent widget for blogs. The data displayed was built purely out of your own preferences and guidelines for what you wanted to get info on as well as external influences like updates to weblogs.com, pings internally or blogger.com updates. All that was put into a highly customizable widget that you could get either via Javascript or a REST interface. I think the full feature set was something new and widely copied since but if you wanna go pure widget external counters like website story were the first.

Cheers.</description>
		<content:encoded><![CDATA[<p>Just for the record, I didn&#8217;t blow you off. It was an ambitious design for one guy to handle with no resources and at the time no job. Money trumped over vision in this case. It wasn&#8217;t a purposeful thing. I admired the vision but it was too far out of my personal area of &#8220;can-do&#8221;.</p>
<p>And I think if you want to call Blogrolling the first widget it should be with the caveat that it was the first intelligent widget for blogs. The data displayed was built purely out of your own preferences and guidelines for what you wanted to get info on as well as external influences like updates to weblogs.com, pings internally or blogger.com updates. All that was put into a highly customizable widget that you could get either via Javascript or a REST interface. I think the full feature set was something new and widely copied since but if you wanna go pure widget external counters like website story were the first.</p>
<p>Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Winer</title>
		<link>http://blog.broadbandmechanics.com/2007/02/heres-a-few-chew-on-this-for-awhile#comment-238928</link>
		<dc:creator>Dave Winer</dc:creator>
		<pubDate>Tue, 20 Feb 2007 17:58:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.broadbandmechanics.com/2007/02/heres-a-few-chew-on-this-for-awhile#comment-238928</guid>
		<description>We had a weblogs.com widget in 1999 or 2000. 

Slowed the browser down something awful.</description>
		<content:encoded><![CDATA[<p>We had a weblogs.com widget in 1999 or 2000. </p>
<p>Slowed the browser down something awful.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
