<?xml version="1.0"?>
<rss version="2.0" xmlns:radioWeblogPost="http://backend.userland.com/radioWeblogPostModule">
	<channel>
		<title>Dave&apos;s Handsome Radio Blog!</title>
		<link>http://radio.weblogs.com/0001015/</link>
		<description>A non-smoking weblog since June 14, 2002.</description>
		<docs>http://backend.userland.com/rss</docs>
		<generator>Radio UserLand v8.0.5</generator>
		<item>
			<description>http://frontier.userland.com/stories/storyReader$9255 </description>
			<pubDate>Fri, 28 Dec 2001 23:47:43 GMT</pubDate>
			<radioWeblogPost:id>701</radioWeblogPost:id>
			</item>
		<item>
			<description>A List Apart: &lt;a href=&quot;http://www.alistapart.com/stories/macbrowsers/&quot;&gt;Mac Browser Roundup&lt;/a&gt;.</description>
			<pubDate>Wed, 26 Dec 2001 14:51:02 GMT</pubDate>
			<radioWeblogPost:id>700</radioWeblogPost:id>
			</item>
		<item>
			<description>&lt;a href=&quot;http://sorry.blogger.com/&quot;&gt;Ouch&lt;/a&gt;. &quot;NOTICE: Blogger has had a security breach. It appears no permanent damage has been done, but as a precaution, we advise you change your FTP password if you had it stored on Blogger. We should be back up and running later today. Sorry for the inconvenience. Crackers have not respect for vacation time, it seems.&quot;</description>
			<pubDate>Wed, 26 Dec 2001 14:49:38 GMT</pubDate>
			<radioWeblogPost:id>699</radioWeblogPost:id>
			</item>
		<item>
			<description>Lesson in keeping your mind focused on the problem. This morning I noted some serious breakage. I reported that I posted an item to my weblog, expected it to appear on the public site, but it did not appear. I checked if there was an archive page for today but it was not there. The weblog functionality appeared to be totally broken. I was led to this problem because a file I created manually had not upstreamed. But then I noticed that after restarting Radio it &lt;i&gt;had &lt;/i&gt;upstreamed. I went back and read my bug report carefully and spotted the problem. I had clicked on Post but had never Published. When I did so the changes upstreamed. This time it was just confusion on a user&apos;s part, not breakage in the software. A reminder to show extra compassion for confused users. </description>
			<pubDate>Wed, 26 Dec 2001 14:30:38 GMT</pubDate>
			<radioWeblogPost:id>698</radioWeblogPost:id>
			</item>
		<item>
			<description>testing 1-2-3 -- 1. 2.</description>
			<pubDate>Wed, 26 Dec 2001 14:01:17 GMT</pubDate>
			<radioWeblogPost:id>697</radioWeblogPost:id>
			</item>
		<item>
			<description>Hey I just searched for &lt;a href=&quot;http://www.google.com/search?q=weblogs&quot;&gt;weblogs&lt;/a&gt; on Google, and weblogs.com is #1. And it&apos;s also on the first page for &lt;a href=&quot;http://www.google.com/search?q=weblog&quot;&gt;weblog&lt;/a&gt;. </description>
			<pubDate>Sun, 23 Dec 2001 15:07:05 GMT</pubDate>
			<radioWeblogPost:id>696</radioWeblogPost:id>
			</item>
		<item>
			<description>General notes on Prefs panels.. 

The first time you refer to the product use its full name: Radio UserLand. You may refer to it as Radio after that.

Avoid judgmental statements. &quot;Radio will normally publish your weblog..&quot; -- No. There&apos;s nothing abnormal about switching a pref. Hunt for a better word. Normal is judgmental. Tech writing must be neutral. Further it only feels normal in Dec 2001. For all we know it may be normal next year for people to have five buttons on their home page. We can&apos;t predict the future.

Whenever possible I try to put new prefs panels at the end of their sections, so as not to break links in the mail list archives. THis was one of those cases when it should have been at the end. It&apos;s an advanced pref, controlling the UI, not for newbies. It wouldn&apos;t hurt anything if it were the last item in the list. 

Use an active voice -- get on the user&apos;s side asap. Explain the feature from the user&apos;s pov, not the developer&apos;s. There&apos;s a real tendency for developers to explain why it works the way it works, as opposed to saying &quot;you should do this if.&quot; Adopting this attitude makes for better designed software too, in addition to users who feel like we&apos;re on their side.

</description>
			<pubDate>Sun, 23 Dec 2001 13:25:52 GMT</pubDate>
			<radioWeblogPost:id>695</radioWeblogPost:id>
			</item>
		<item>
			<description>&lt;a href=&quot;http://inessential.com/2001/12/22.html&quot;&gt;Brent Simmons&lt;/a&gt;: &quot;I&apos;m 200, You&apos;re 200.&quot; &quot;;-&gt;&quot;</description>
			<pubDate>Sat, 22 Dec 2001 19:39:04 GMT</pubDate>
			<category>Michegas</category>
			<radioWeblogPost:id>694</radioWeblogPost:id>
			</item>
		<item>
			<description>&lt;a href=&quot;http://radio.weblogs.com/0001194/2001/12/20.html#a1&quot;&gt;Meryl Evans&lt;/a&gt;: &quot;Oh the weather outside is frightful. But the monitor is so delightful. And since we&apos;ve no place to jog. Let Us Blog! Let Us Blog! Let Us Blog!&quot;</description>
			<pubDate>Fri, 21 Dec 2001 13:32:12 GMT</pubDate>
			<category>Michegas</category>
			<radioWeblogPost:id>693</radioWeblogPost:id>
			</item>
		<item>
			<description>&lt;a href=&quot;http://www.osnews.com/story.php?news_id=421&amp;page=1&quot;&gt;Scot Hacker&lt;/a&gt; reviews Mac OS X.</description>
			<pubDate>Thu, 20 Dec 2001 14:40:55 GMT</pubDate>
			<category>Macintosh</category>
			<radioWeblogPost:id>692</radioWeblogPost:id>
			</item>
		<item>
			<description>There&apos;s so much good news these days. Here&apos;s an &lt;a href=&quot;http://www.perl.com/pub/a/2001/12/19/xmlrpc.html&quot;&gt;article&lt;/a&gt; on Perl.Com that explains how to program Microsoft&apos;s Active Directory through XML-RPC, and avoid the locked trunks and have fun and support interop. Wow. Things are really sorting themselves out nicely. Thanks!</description>
			<pubDate>Thu, 20 Dec 2001 14:39:23 GMT</pubDate>
			<category>XML-RPC</category>
			<radioWeblogPost:id>691</radioWeblogPost:id>
			</item>
		<item>
			<description>Stop the presses! Thanks to &lt;a href=&quot;http://www.pythonware.com/daily/&quot;&gt;Daily Python-URL&lt;/a&gt; for digging up this &lt;a href=&quot;http://www-106.ibm.com/developerworks/xml/library/x-matters15.html?open&amp;l=810,t=grx,p=rpc&quot;&gt;article&lt;/a&gt; about XML-RPC on IBM DeveloperWorks. What a great story. He starts off saying in every way imaginable what a piece of &lt;a href=&quot;http://www.dictionary.com/cgi-bin/dict.pl?term=shit&quot;&gt;expletive&lt;/a&gt; it is. Then proceeds to say that this is the highest praise possible. Right on. It&apos;s true. We make shitty software. &lt;i&gt;With bugs.&lt;/i&gt;</description>
			<pubDate>Wed, 19 Dec 2001 18:30:59 GMT</pubDate>
			<category>XML-RPC</category>
			<radioWeblogPost:id>690</radioWeblogPost:id>
			</item>
		<item>
			<description>I reactivated the Macintosh &lt;a href=&quot;http://radio.weblogs.com/0001015/categories/macintosh/rss.xml&quot;&gt;RSS feed&lt;/a&gt;. It&apos;s viewable in HTML &lt;a href=&quot;http://www.thetwowayweb.com/macintoshNews&quot;&gt;on the 2WW site&lt;/a&gt;.</description>
			<pubDate>Wed, 19 Dec 2001 13:48:12 GMT</pubDate>
			<radioWeblogPost:id>689</radioWeblogPost:id>
			</item>
		<item>
			<description>&lt;a href=&quot;http://scriptingnews.userland.com/stories/storyReader$1464&quot;&gt;How I edited the awards outline&lt;/a&gt;. &quot;First, I opened up the outliner and created a file called awards.opml.&quot;</description>
			<pubDate>Wed, 19 Dec 2001 13:44:46 GMT</pubDate>
			<category>Outliners</category>
			<category>Radio 7.1</category>
			<category>Two-Way-Web</category>
			<radioWeblogPost:id>688</radioWeblogPost:id>
			</item>
		<item>
			<description>&lt;a href=&quot;http://www.opera.com/mac/&quot;&gt;Opera for Macintosh&lt;/a&gt;: &quot;The legendary speed of the Opera Web browser is now available on the Macintosh in two flavors: PPC and Carbon. Opera for Mac is not only fast, but flexible and easy to use, with a bright clean interface implemented according to the Apple Design Guidelines.&quot;</description>
			<pubDate>Wed, 19 Dec 2001 13:38:57 GMT</pubDate>
			<category>Macintosh</category>
			<radioWeblogPost:id>687</radioWeblogPost:id>
			</item>
		<item>
			<description>Contemplating a couple of changes. John says that after he&apos;s finished editing a post, the browser should come back to an empty form. The reasoning is that it&apos;s hard to figure out how to get an empty editing box after editing. I&apos;m going to do a little experiment to see how I feel about this. OK, I&apos;m editing this post now.</description>
			<pubDate>Tue, 18 Dec 2001 17:33:05 GMT</pubDate>
			<radioWeblogPost:id>686</radioWeblogPost:id>
			</item>
		<item>
			<description>The new feature is now complete. I&apos;m testing it right now. If all goes well this will appear in a folder on my local area network in addition to the community server. &lt;i&gt;Praise Murphy!&lt;/i&gt;</description>
			<pubDate>Mon, 17 Dec 2001 23:14:08 GMT</pubDate>
			<radioWeblogPost:id>685</radioWeblogPost:id>
			</item>
		<item>
			<description>Adding a new type of callback, one that&apos;s called when the text of a page is rendered as it is upstreamed. If this works it will allow you to capture the rendered text as it flows upstream, so it can be archived locally, or whatever else you like.</description>
			<pubDate>Mon, 17 Dec 2001 22:32:00 GMT</pubDate>
			<radioWeblogPost:id>684</radioWeblogPost:id>
			</item>
		<item>
			<description>&lt;a href=&quot;http://www.redhat.com/support/wpapers/redhat/RHNetwork/RHN-technical/&quot;&gt;Red Hat&lt;/a&gt; is using XML-RPC in a strategic way. That&apos;s cool. </description>
			<pubDate>Mon, 17 Dec 2001 18:08:47 GMT</pubDate>
			<category>XML-RPC</category>
			<radioWeblogPost:id>683</radioWeblogPost:id>
			</item>
		<item>
			<description>This is a test to see if Last Updated appears at the top of DHRB.</description>
			<pubDate>Mon, 17 Dec 2001 15:42:54 GMT</pubDate>
			<radioWeblogPost:id>682</radioWeblogPost:id>
			</item>
		<item>
			<description>New Radio 7.1 feature this morning. &quot;As you post items to your weblog, Radio automatically links, through the calendar, to the other days of the month. This works great for the past, but Radio has no way of linking to daily archives that are in the future. It&apos;s a tricky little corner, but the problem is neatly solved by building the pages for the month once a night, that way, for example, the calendar on the page for the third can correctly link to the fourteenth.&quot;</description>
			<pubDate>Sun, 16 Dec 2001 14:21:18 GMT</pubDate>
			<category>Radio 7.1</category>
			<radioWeblogPost:id>681</radioWeblogPost:id>
			</item>
		<item>
			<description>&lt;a href=&quot;http://groups.yahoo.com/group/xml-rpc/message/4027&quot;&gt;Cliff Baeseman&lt;/a&gt;: &quot;Well the weather here in Central Wisconsin has been sucking for the last few days. So what else could I do but churn up about 4000 lines of code to create a new VB XML-RPC client that well frankly does not suck.&quot;</description>
			<pubDate>Sun, 16 Dec 2001 11:37:02 GMT</pubDate>
			<category>XML-RPC</category>
			<radioWeblogPost:id>680</radioWeblogPost:id>
			</item>
		<item>
			<description>New tutorial: &lt;a href=&quot;http://radio.userland.com/goingCrazyWithMacros&quot;&gt;Going crazy with macros&lt;/a&gt;.</description>
			<pubDate>Sat, 15 Dec 2001 17:08:56 GMT</pubDate>
			<category>Radio 7.1</category>
			<radioWeblogPost:id>679</radioWeblogPost:id>
			</item>
		<item>
			<description>Maarten Koopmans: &lt;a href=&quot;http://www.escribe.com/internet/rebol/m17669.html&quot;&gt;Rugby 4.4exp with XML-RPC&lt;/a&gt;.</description>
			<pubDate>Sat, 15 Dec 2001 14:29:21 GMT</pubDate>
			<category>XML-RPC</category>
			<radioWeblogPost:id>678</radioWeblogPost:id>
			</item>
		<item>
			<description>&lt;a href=&quot;http://scriptingnews.userland.com/backissues/2001/12/14#radio71ToShipInJanuary&quot;&gt;Scripting News&lt;/a&gt;: Radio 7.1 to ship in early January 2002. Pricing under $100. Available for all flavors of Windows and Macintosh OS. </description>
			<pubDate>Sat, 15 Dec 2001 14:20:55 GMT</pubDate>
			<category>Radio 7.1</category>
			<radioWeblogPost:id>677</radioWeblogPost:id>
			</item>
		<item>
			<description>I didn&apos;t feel like writing docs this evening, so I added a feature to Radio 7.1, it&apos;s been on the list for a long time. It allows you to have the contents of your weblog archived in XML in a folder you designate. Every hour it synchs up the folder with the contents of your blog. Another form of backup, and a way to use Radio to author content that flows out through more and more channels.</description>
			<pubDate>Sat, 15 Dec 2001 01:29:22 GMT</pubDate>
			<radioWeblogPost:id>675</radioWeblogPost:id>
			</item>
		<item>
			<description>This is an emergency test post. Hurry up!</description>
			<pubDate>Sat, 15 Dec 2001 00:59:30 GMT</pubDate>
			<radioWeblogPost:id>674</radioWeblogPost:id>
			</item>
		<item>
			<description>According to Jake, you should now see a Last Updated string at the top of my blog home page.</description>
			<pubDate>Fri, 14 Dec 2001 22:55:20 GMT</pubDate>
			<radioWeblogPost:id>673</radioWeblogPost:id>
			</item>
		<item>
			<description>Interesting. When I simulated the blog post in the debugger, all three files were touched and all three upstreamed. This suggests it&apos;s a timing or synchronization issue. Something is being touched, but the upstreamer is not tuning in.</description>
			<pubDate>Thu, 13 Dec 2001 01:51:10 GMT</pubDate>
			<radioWeblogPost:id>672</radioWeblogPost:id>
			</item>
		<item>
			<description>Jake, Lawrence: Progress on the missing archive page on the laptop -- it&apos;s not being touched. It doesn&apos;t show up in the upstream scan. It appears to not be an upstreaming problem. Looking into it now.</description>
			<pubDate>Thu, 13 Dec 2001 01:45:36 GMT</pubDate>
			<radioWeblogPost:id>671</radioWeblogPost:id>
			</item>
		<item>
			<description>Radio 7.1&apos;s CMS is new in a lot of ways. It&apos;s a CMS where the content lives in the file system. Yes, it all flows through the object database on its way onto the public Internet, but that&apos;s invisible to the user. (Not to developers, of course.) People who were around in the early CMS days, Frontier 4.2.3, will recognize the new CMS as the continuation of the &lt;a href=&quot;http://frontier.userland.com/stories/storyReader$1097&quot;&gt;BBSite suite&lt;/a&gt;, which gave BBEdit users a modest CMS in the file system. The difference is a few years. In those years our understanding of content management increased, and (don&apos;t overlook this) Moore&apos;s Law has been raging, and things that were formerly unthinkable are now &lt;i&gt;fast.&lt;/i&gt;&lt;p&gt;
One of the big benefits of doing it all in the file system is that users have total choice of tools. Everything from Notepad to Dreamweaver, you name it, as long as it can produce a text file, an HTML file or an OPML file, we can deal with it. It&apos;s been interesting to watch the debate over file extensions rage in Mac-land. We&apos;ve drunk the Kool Aid. The extensions route the files through the rendering process. Lots of cross-platform cross-tools connections, achieved entirely through architecture, not brute force. It&apos;s a clean CMS that people who program in PHP and ASP will instantly grok.</description>
			<pubDate>Thu, 13 Dec 2001 00:53:22 GMT</pubDate>
			<category>Mind Bombs</category>
			<radioWeblogPost:id>670</radioWeblogPost:id>
			</item>
		<item>
			<description>I need something lite to do -- so I want to find out why Weblogs.Com pings are not showing up on the Events page. Maybe it&apos;s quite simple. There doesn&apos;t appear to be any code that does it. Still searching. I checked every call to radio.log.add in builtins.radio, and there&apos;s nothing there. OK, it&apos;s easy to fix the bug. I&apos;ll write the code.</description>
			<pubDate>Wed, 12 Dec 2001 23:39:49 GMT</pubDate>
			<radioWeblogPost:id>669</radioWeblogPost:id>
			</item>
		<item>
			<description>Today I &lt;a href=&quot;http://radio.userland.com/upstreamingDriverArchitecture&quot;&gt;documented&lt;/a&gt; the driver architecture for upstreaming in Radio UserLand 7.1. Ken Dow got his driver working today too, so the doc had a developer review. I think this doc is done.</description>
			<pubDate>Wed, 12 Dec 2001 23:11:26 GMT</pubDate>
			<radioWeblogPost:id>668</radioWeblogPost:id>
			</item>
		<item>
			<description>Back to work on the World Wide Web, circa 2001.</description>
			<pubDate>Wed, 12 Dec 2001 17:33:53 GMT</pubDate>
			<category>The Web</category>
			<radioWeblogPost:id>667</radioWeblogPost:id>
			</item>
		<item>
			<description>Error deleting files on linux3.userland.com: &quot;We haven&apos;t written tcp.ftp.delete yet.&quot;</description>
			<pubDate>Tue, 11 Dec 2001 23:59:44 GMT</pubDate>
			<radioWeblogPost:id>665</radioWeblogPost:id>
			</item>
		<item>
			<description>Steven Vore: &quot;Should we assume that &apos;Dave&apos;s Handsome Radio Blog&apos; is being created with Radio 7.1?  It&apos;s a great advertisement, in itself, for the whole KM/developer group notes/blogging throughout the day deal. I&apos;m using Radio 7.0 to create outlines of a (huge) collection of web apps I&apos;ve inherited, partially in an attempt to keep my sanity while I try to wrap my arms around all this &apos;shtuff&apos; I&apos;ve been given and partially in hopes that the next person to join the team won&apos;t have the same troubles. DHRB has pushed my &apos;hey, what if I did that&apos; button and I&apos;m seeing the whole project-documentation picture change before my eyes. Mind bomb.&quot; 

DW: &quot;Yes, this is a Radio 7.1 blog.&quot;
</description>
			<pubDate>Tue, 11 Dec 2001 19:22:20 GMT</pubDate>
			<category>Michegas</category>
			<radioWeblogPost:id>664</radioWeblogPost:id>
			</item>
		<item>
			<description>Puzzle. Watch system.temp.radio.stats.agentsTicks while the thread is running. The number for upstreamChangedFiles sometimes updates &lt;b&gt;three times&lt;/b&gt; in each pass. I&apos;ve stepped through radio.thread.script in the debugger to try to understand how this can happen, but it makes no sense to me. It often does it three times. This pisses me off because it triples the cost since it clearly is scanning three times! No, I&apos;ve gotta figure out why it&apos;s doing this.</description>
			<pubDate>Tue, 11 Dec 2001 15:36:55 GMT</pubDate>
			<radioWeblogPost:id>663</radioWeblogPost:id>
			</item>
		<item>
			<description>radio.thread.script can be smarter about going to sleep. If it sees that there&apos;s work queued up for it to do, it can just loop around to the top and do another pass. An example of this is the writing of directory.opml. The need to do this is detected by the upstreamer, and it adds an item to system.temp.radio.recentlyChangedFolders, which will be picked up by radio.thread.agents.saveChangedDirectories. There may be other ways for the thread to see that it has more work to do and not go to sleep at all. How I&apos;ll do this. A new global, system.temp.radio.misc.flThreadSleeps, set on each pass in radio.thread.script, it can be turned off by any code that runs in an agent. This keeps the dirty details out of radio.thread.script.</description>
			<pubDate>Tue, 11 Dec 2001 14:33:04 GMT</pubDate>
			<radioWeblogPost:id>662</radioWeblogPost:id>
			</item>
		<item>
			<description>After it writes out the files, immediately kick the thread in the butt. Wake up! Go to work. No bitches with one hand on the hip and a pinky in the corner of the mouth. You have work to do dear thread. No lollygagging allowed. 1.</description>
			<pubDate>Tue, 11 Dec 2001 14:29:56 GMT</pubDate>
			<radioWeblogPost:id>661</radioWeblogPost:id>
			</item>
		<item>
			<description>Next change. Trick the upstreamer into doing &quot;index&quot; first. The goal is to make it more likely that when you click on Home on the DWHP that it will already be updated. If index is moved to the front of the list, that becomes more likely. Why should it wait for the other two files? It shouldn&apos;t. &lt;i&gt;Testing. 1. 2. 3. 4. 5. 6.&lt;/i&gt;</description>
			<pubDate>Tue, 11 Dec 2001 13:52:57 GMT</pubDate>
			<radioWeblogPost:id>660</radioWeblogPost:id>
			</item>
		<item>
			<description>OK, back to upstreaming school. The foundation is laid. All upstreaming goes through a single bottleneck. Now to get clever about waking the bottleneck up.</description>
			<pubDate>Tue, 11 Dec 2001 13:27:10 GMT</pubDate>
			<radioWeblogPost:id>659</radioWeblogPost:id>
			</item>
		<item>
			<description>&lt;a href=&quot;http://news.cnet.com/news/0-1014-201-8104108-0.html?tag=pt.rss..feed.ne_8104108&quot;&gt;Turning on the World Wide Web&lt;/a&gt;. Ten years ago, Paul Kunz wrote and posted the first American Web page at the Stanford Linear Accelerator Center. The subsequent chain of events turned the Web into a staple of everyday life. </description>
			<pubDate>Mon, 10 Dec 2001 19:30:41 GMT</pubDate>
			<source url="http://export.cnet.com/export/feeds/news/rss/1,11176,,00.xml">CNET News.com</source>
			<radioWeblogPost:sourceTime>Mon, 10 Dec 2001 13:59:27 GMT</radioWeblogPost:sourceTime>
			<category>The Web</category>
			<radioWeblogPost:id>658</radioWeblogPost:id>
			</item>
		<item>
			<description>&lt;ol&gt;&lt;li&gt;Earlier in the day yesterday I fixed a simple problem, at 7:43:57 AM. Checked it in.

&lt;li&gt;Went to work on RSS and the cloud.

&lt;li&gt;Took a break.

&lt;li&gt;In the evening I rolled up my sleeves to do the long-postponed work of stream-izing the upstreamer, so that it could upload five files in one shot instead of doing five separate upstreams. To begin the work I used WebEdit to check it out, thinking I was protected. I was not.

&lt;li&gt;I finished the work around 10PM or so, went offline.

&lt;li&gt;At 12:15AM, my copy of Radio updated. It got the version of radio.upstream.uploadChangedFiles that I had checked in earlier in the day on Sunday.
&lt;/ol&gt;


</description>
			<pubDate>Mon, 10 Dec 2001 17:20:38 GMT</pubDate>
			<category>Michegas</category>
			<radioWeblogPost:id>657</radioWeblogPost:id>
			</item>
		<item>
			<description>It&apos;s &lt;i&gt;much&lt;/i&gt; worse than it appears! &quot;;-&gt;&quot; 1. 2. 3. 4. 5.</description>
			<pubDate>Mon, 10 Dec 2001 13:31:46 GMT</pubDate>
			<category>Michegas</category>
			<radioWeblogPost:id>656</radioWeblogPost:id>
			</item>
		<item>
			<description>Well my overhaul worked. Tomorrow first thing I clean it up and release it. It&apos;s a lot faster and cleaner, and yet still very flexible. It works here. My mind is fried now. Started programming at 5AM. Only stopped for lunch and a walk. How many hours is that? No matter. This is how you ship. Always has been, always will. 

&quot;curly&quot;

</description>
			<pubDate>Mon, 10 Dec 2001 01:43:09 GMT</pubDate>
			<category>Michegas</category>
			<radioWeblogPost:id>655</radioWeblogPost:id>
			</item>
		<item>
			<description>Doing another overhaul of upstreaming. It keeps getting deeper, but simpler. A good sign. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10.</description>
			<pubDate>Sun, 09 Dec 2001 22:20:38 GMT</pubDate>
			<category>Michegas</category>
			<radioWeblogPost:id>654</radioWeblogPost:id>
			</item>
		<item>
			<description>I just fixed a bug. We have two places where RSS is generated, for the home page and for each of the categories. It was generating &amp;lt;cloud&gt; elements for the categories, not for the home page. Now it generates them for both. That&apos;s what I&apos;m testing with this post. </description>
			<pubDate>Sun, 09 Dec 2001 16:45:59 GMT</pubDate>
			<category>Michegas</category>
			<radioWeblogPost:id>653</radioWeblogPost:id>
			</item>
		<item>
			<description>I&apos;m always trawling for Michegas, but today I&apos;m looking more aggressively than usual. Scoble says he has the #1 link on Google for Carly Fiorina. Not according to &lt;a href=&quot;http://www.google.com/search?q=carly+fiorina&quot;&gt;the Google I use&lt;/a&gt;. Maybe he&apos;s using some other Google? Google. Google. Google. Google. Google. Say it fast. &quot;;-&gt;&quot;</description>
			<pubDate>Sun, 09 Dec 2001 16:06:26 GMT</pubDate>
			<category>Michegas</category>
			<radioWeblogPost:id>652</radioWeblogPost:id>
			</item>
		<item>
			<description>We&apos;re now up to four subscribers to the Michegas channel, but unfortunately two of them are behind firewalls and will not get updates. There&apos;s a pref setting for this in Radio, but I guess some people aren&apos;t setting it, or don&apos;t know if they&apos;re behind a firewall. No matter, the community server will try once and give up. 25 hours from now the user will get another chance. This is how you make systems like this scale, Murphy-willing.</description>
			<pubDate>Sun, 09 Dec 2001 15:37:40 GMT</pubDate>
			<category>Michegas</category>
			<radioWeblogPost:id>651</radioWeblogPost:id>
			</item>
		<item>
			<description>Running an experiment today. The Michegas channel just got its second subscriber. Hummin and rollin.</description>
			<pubDate>Sun, 09 Dec 2001 15:28:53 GMT</pubDate>
			<category>Michegas</category>
			<radioWeblogPost:id>650</radioWeblogPost:id>
			</item>
		<item>
			<description>I am breathing my own fumes again! I just subscribed to &lt;a href=&quot;http://radio.weblogs.com/0001015/categories/michegas/rss.xml&quot;&gt;this RSS feed&lt;/a&gt;. Of course this item is itself in this feed. Heh. Hope someone&apos;s copy of Radio doesn&apos;t lose its mind. Now the question is, will I receive notification that it changed? Rube Goldberg would love this shit.</description>
			<pubDate>Sun, 09 Dec 2001 14:45:01 GMT</pubDate>
			<category>Michegas</category>
			<category>XML</category>
			<radioWeblogPost:id>649</radioWeblogPost:id>
			</item>
		<item>
			<description>Adam Curry&apos;s &lt;a href=&quot;http://www.curry.com/2001/12/09#bootstrappingOutlookhotmail&quot;&gt;mind&lt;/a&gt; is going amok about email.</description>
			<pubDate>Sun, 09 Dec 2001 14:37:01 GMT</pubDate>
			<category>Two-Way-Web</category>
			<radioWeblogPost:id>648</radioWeblogPost:id>
			</item>
		<item>
			<description>I&apos;ve started my 2001 awards list. It&apos;s coming together nicely. I expect to spend a few more days and then announce the nominees. Now there are nine categories. I&apos;m sure there will be some arguments about who&apos;s in which category. Oh la. I&apos;m having fun with it. Questions. When should we open voting? How long should the voting stay open? And if you didn&apos;t get nominated in 2001, there&apos;s always 2002.</description>
			<pubDate>Sun, 09 Dec 2001 11:15:05 GMT</pubDate>
			<category>Michegas</category>
			<radioWeblogPost:id>647</radioWeblogPost:id>
			</item>
		<item>
			<description>The text on the setupRadio page refers to things I don&apos;t know about. What is radio.weblogs.com? It doesn&apos;t explain the community server I am being asked to join. If we did a little selling here, we wouldn&apos;t get the question &quot;Do I have to join this?&quot; -- instead they would see it as a necessary part of the $xx they just spent (or are about to).</description>
			<pubDate>Sat, 08 Dec 2001 12:57:38 GMT</pubDate>
			<radioWeblogPost:id>646</radioWeblogPost:id>
			</item>
		<item>
			<description>Test post. 1.2.3.4.5.</description>
			<pubDate>Fri, 07 Dec 2001 16:40:07 GMT</pubDate>
			<radioWeblogPost:id>645</radioWeblogPost:id>
			</item>
		<item>
			<description>Now I spotted another problem. The renderer had so much work to do that it took longer than 10 seconds, and the upstreamer started upstreaming files, that were then accumulated in recentlyWrittenWwwFiles. It&apos;s not clear that all of them upstreamed and recentlyWrittenWwwFiles is not empty now. (I&apos;m running with recentlyWrittenWwwFiles open all the time so I can watch it.) I suspect that we need a semaphore to keep the main upstreamer from doing anything while a publish is pending.</description>
			<pubDate>Fri, 07 Dec 2001 16:08:39 GMT</pubDate>
			<radioWeblogPost:id>644</radioWeblogPost:id>
			</item>
		<item>
			<description>Hello.</description>
			<pubDate>Fri, 07 Dec 2001 13:56:35 GMT</pubDate>
			<radioWeblogPost:id>643</radioWeblogPost:id>
			</item>
		<item>
			<description>This is another test.</description>
			<pubDate>Fri, 07 Dec 2001 13:54:54 GMT</pubDate>
			<radioWeblogPost:id>642</radioWeblogPost:id>
			</item>
		<item>
			<description>Another test post.</description>
			<pubDate>Fri, 07 Dec 2001 13:53:21 GMT</pubDate>
			<radioWeblogPost:id>641</radioWeblogPost:id>
			</item>
		<item>
			<description>Jrobb reports a problem. When you post a new item, he wants an empty text box. If this were happening it would mean serious breakage. I don&apos;t think this is actually what he&apos;s seeing. This test will verify. 1.</description>
			<pubDate>Fri, 07 Dec 2001 13:51:04 GMT</pubDate>
			<radioWeblogPost:id>640</radioWeblogPost:id>
			</item>
		<item>
			<description>This is a test.</description>
			<pubDate>Fri, 07 Dec 2001 00:33:02 GMT</pubDate>
			<radioWeblogPost:id>639</radioWeblogPost:id>
			</item>
		<item>
			<description>I&apos;d bet $10 that I fixed the problem reported by Andy Fragen. Now Murphy-willing, once again, after you hit Post to Weblog, if you click on Events, you&apos;ll see the Upstream there. In other words the updates will be live before you can look to see if they got there. Keep your fingers crossed.</description>
			<pubDate>Fri, 07 Dec 2001 00:30:37 GMT</pubDate>
			<radioWeblogPost:id>638</radioWeblogPost:id>
			</item>
		<item>
			<description>3. I want to get Jeff Cheney posting again. He hit the 5MB limit. It&apos;s good that the limit works! Now I need a mechanism to give one user more space because he&apos;s a friend, this will make it possible to give people more space for more money.</description>
			<pubDate>Fri, 07 Dec 2001 00:22:56 GMT</pubDate>
			<radioWeblogPost:id>637</radioWeblogPost:id>
			</item>
		<item>
			<description>1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 </description>
			<pubDate>Fri, 07 Dec 2001 00:02:49 GMT</pubDate>
			<radioWeblogPost:id>636</radioWeblogPost:id>
			</item>
		<item>
			<description>I found a major error in radio.upstream.uploadRecentlyTouchedFiles. The callback scripts would always error, they were expecting a list of file paths, but we were passing a list containing a list of filepaths. The error is in this line: try {nomad^ ({f})}. Note the extra set of curly braces. I believe that when I fix this, weblogs.com notification will work again. If you see Dave&apos;s Handsome Radio Blog on www.weblogs.com, you&apos;ll know it worked. Keep your fingers crossed. &quot;;-&gt;&quot;</description>
			<pubDate>Thu, 06 Dec 2001 23:56:05 GMT</pubDate>
			<radioWeblogPost:id>635</radioWeblogPost:id>
			</item>
		<item>
			<description>Something appears to be broken. How much time before it appears in the cloud? 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15.</description>
			<pubDate>Thu, 06 Dec 2001 22:12:02 GMT</pubDate>
			<radioWeblogPost:id>634</radioWeblogPost:id>
			</item>
		<item>
			<description>I&apos;m testing the upstreaming code to see if it&apos;s broken or not.</description>
			<pubDate>Thu, 06 Dec 2001 22:10:57 GMT</pubDate>
			<radioWeblogPost:id>633</radioWeblogPost:id>
			</item>
		<item>
			<description>This is a test post to see if new upstreaming code is completely broken. 1.</description>
			<pubDate>Thu, 06 Dec 2001 17:56:41 GMT</pubDate>
			<radioWeblogPost:id>632</radioWeblogPost:id>
			</item>
		<item>
			<description>test post.</description>
			<pubDate>Tue, 04 Dec 2001 00:56:49 GMT</pubDate>
			<radioWeblogPost:id>631</radioWeblogPost:id>
			</item>
		<item>
			<description>A test post to see if directory.opml is upstreamed when I update my blog. (Note to Jake -- no.)</description>
			<pubDate>Sun, 02 Dec 2001 12:50:48 GMT</pubDate>
			<radioWeblogPost:id>630</radioWeblogPost:id>
			</item>
		<item>
			<description>this is a test post. 1.</description>
			<pubDate>Sat, 01 Dec 2001 19:08:18 GMT</pubDate>
			<radioWeblogPost:id>629</radioWeblogPost:id>
			</item>
		</channel>
	</rss>
