<?xml version="1.0"?><!-- RSS generated by Radio UserLand v8.0.6 on Sat, 20 Sep 2003 17:41:47 GMT --><rss version="2.0">	<channel>		<title>john robert boynton: RadioRadio</title>		<link>http://radio.weblogs.com/0102813/categories/radioradio/</link>		<description>licentious radio</description>		<copyright>Copyright 2003 john robert boynton</copyright>		<lastBuildDate>Sat, 20 Sep 2003 17:41:47 GMT</lastBuildDate>		<docs>http://backend.userland.com/rss</docs>		<generator>Radio UserLand v8.0.6</generator>		<managingEditor>jrb@tdl.com</managingEditor>		<webMaster>jrb@tdl.com</webMaster>		<category domain="http://www.weblogs.com/rssUpdates/changes.xml">rssUpdates</category> 		<skipHours>			<hour>2</hour>			<hour>3</hour>			<hour>4</hour>			<hour>5</hour>			<hour>1</hour>			<hour>6</hour>			<hour>0</hour>			<hour>7</hour>			</skipHours>		<cloud domain="radio.xmlstoragesystem.com" port="80" path="/RPC2" registerProcedure="xmlStorageSystem.rssPleaseNotify" protocol="xml-rpc"/>		<ttl>60</ttl>		<item>			<description>Ha ha.licentious radio is the first site in Google search results for &quot;licentious&quot;. We&apos;re proud, mighty proud.We&apos;d like to thank all the *little* people who made this possible. We never expected this honor. We only try to do our best. If we can cause one smile, we feel like we&apos;ve accomplished something. We&apos;ll use any notoriety from this honor to promote world peace and save the animals.</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/08/09.html#a1756</guid>			<pubDate>Sat, 09 Aug 2003 16:31:18 GMT</pubDate>			</item>		<item>			<description>Random Rant on the font tag....Putting a font tag in every freaking table cell was pretty silly.On the other hand, it worked. &quot;Worked&quot; in the sense of letting users pick the default text size, and reliably scaling the text size from there across platforms. The fact that some designers picked the typically unreadable &quot;font size=1&quot; for body text was not the fault of the font tag.CSS has a way to do essentially the same thing, but Microsoft broke it by picking different relative sizes than the rest of the world. That is,  the CSS equivalent of size=2 is one step different on Windows IE than on most other browsers.Then there&apos;s a Windows IE bug for sizing text with em units in CSS -- some users will see .9em as unreadably small.I&apos;m sure Billionaire Bill&apos;s heart breaks when he hears about these bugs that make it vastly more difficult to create websites that look OK on both Windows IE and other browsers.</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/05/03.html#a1585</guid>			<pubDate>Sat, 03 May 2003 17:59:49 GMT</pubDate>			</item>		<item>			<description>A little problem with the tabs at the Google search engine....Problem: mouse cursor changes over the tabs, but only the text is clickable. This is actually *very* bad usability... needlessly tricking people. (This affects Gecko -- Netscape/Mozilla...--  browsers, and at least IE 5 -- windows and Mac.) Solution: Add to the .q styles (the &apos;a&apos; tags in the tabs): &lt;tt&gt;width: 100%; display: block&lt;/tt&gt;With the width at 100% of the table cell, the entire tab is clickable. Gecko browsers need &quot;display:block&quot;, though IE5win doesn&apos;t.When the entire tab is clickable, you don&apos;t need the cursor style in &apos;td&apos; tag for each tab:&lt;tt&gt;style=cursor:pointer;cursor:hand;&lt;/tt&gt;That way you even save a few bytes. (Even if you don&apos;t add the CSS for the &quot;q&quot; class, you should take out the cursor styles.)You could also add &quot;width: 100%; display: block&quot; to the style for tabs on the news page (.d).</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/04/07.html#a1539</guid>			<pubDate>Mon, 07 Apr 2003 19:31:54 GMT</pubDate>			</item>		<item>			<description>Google queries that led people to licentious radio today:&lt;ul&gt;&lt;li&gt;george bush 11 september speech&lt;li&gt;what do you think of bush&apos;s radio address on iraq&lt;li&gt;/usr/lib/ipkg/info/opie-irdaapplet.postinst configure&apos; failed&lt;li&gt;republican voter fraud&lt;li&gt;greenspan interest rate&lt;li&gt;Neil Bush&lt;li&gt;linux for ipaq 3800&lt;li&gt;Israel halliburton&lt;li&gt;ipaq install network card&lt;li&gt;humor radio&lt;li&gt;emil ruder&lt;li&gt;CSS div absolute table cell&lt;li&gt;&quot;ordered list&quot; stylesheet&lt;li&gt;Interest rate - greenspan&lt;li&gt;madplay radio&lt;li&gt;hitler breaking treaties&lt;li&gt;ipaq radio&lt;li&gt;George Bush press conference, transcript&lt;li&gt;ipaq and radio&lt;li&gt;typography golden section&lt;li&gt;12 iraqis surrendered march 2003&lt;li&gt;neil bush&lt;li&gt;interest rate greenspan&lt;li&gt;neil bush&lt;li&gt;&quot;I&apos;m the person who gets to decide,  not you.&quot;&lt;li&gt;&quot;download microsoft fonts&quot;&lt;li&gt;graphics kind of peace&lt;li&gt;Schwarzkopf france deer hunt&quot;&lt;li&gt;&quot;zapping electronics&quot;&lt;li&gt;squeeze breast&lt;li&gt;usability humor&lt;/ul&gt;On a good day, a few people find answers to technical questions, and a few people find entertainment. We&apos;re on the second page of results for &quot;Neil Bush&quot;. You can tell Neil is in stealth mode (after nearly getting Reagan whacked, and stealing A FREAKING BILLION DOLLARS from American taxpayers, and having Corrupt Brother Jeb shovel money down his throat).Every now and then somebody takes the time to say &apos;hi&apos; or asks a question.</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/03/10.html#a1391</guid>			<pubDate>Tue, 11 Mar 2003 04:39:08 GMT</pubDate>			</item>		<item>			<description>If Google ads are so tied to the search query, why did &quot;mozilla html object tag&quot; give me an ad for: &quot;GirlSummer Academic Camps&quot;?</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/03/07.html#a1375</guid>			<pubDate>Fri, 07 Mar 2003 15:38:12 GMT</pubDate>			</item>		<item>			<description>&lt;a href=&quot;http://scriptingnews.userland.com/backissues/2003/02/27#When:6:45:08AM&quot;&gt;Dave Winer&lt;/a&gt; [userland.com]: &quot;Here&apos;s what Google can do for weblogs that would be a service to the weblog community -- classify and group them. Give me an accurate list of all the librarian weblogs, and all the lawyer weblogs, and all the weblogs of people who have implemented an XML-RPC stack. You get the idea. They have been able to do this with news stories, it seems they should also be able to do it with weblogs. This is the biggest unsolved problem I see in this world, and I don&apos;t know how to solve it, it&apos;s not what I do. Postscript: Tom Matrullo wants this too.&quot;My suggestion is use the Open Directory categories -- maybe enhance them -- and let weblog writers self-select. There&apos;s no reason to restrict this to weblogs, of course. It would let you establish a context for your search phrase. Search for &quot;mustang&quot; under horses, or under cars.Google&apos;s trick of categorizing news articles is slightly different from categorizing weblogs and websites: Google has a very small number of categories for news, and most news articles are about one topic. If the software isn&apos;t sure about one article, it can just leave it off the front page. If it ever guesses wrong about an article, the article disappears off the front page in a matter of hours.</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/02/27.html#a1354</guid>			<pubDate>Fri, 28 Feb 2003 02:59:45 GMT</pubDate>			</item>		<item>			<description>The case for &lt;a href=&quot;http://www.google-watch.org/bigbro.html&quot;&gt;Google for Big Brother of the Year&lt;/a&gt; award.We just mention this Google stuff, we&apos;re not necessarily complaining about Google ourselves.</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/02/13.html#a1272</guid>			<pubDate>Thu, 13 Feb 2003 21:43:06 GMT</pubDate>			</item>		<item>			<description>Googlicide: linking to a Google-censored page, thereby black-holing your blog at Google until the link scrolls off the main page?</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/02/12.html#a1252</guid>			<pubDate>Thu, 13 Feb 2003 01:35:37 GMT</pubDate>			</item>		<item>			<description>Weird Google-glitch yesterday. If you searched for various combinations of: &quot;George W. Bush State of the Union address, 2003&quot;, licentious radio&apos;s (not very funny) &lt;a href=&quot;http://radio.weblogs.com/0102813/stories/2003/01/27/georgeWBushStateOfTheUnion.html&quot;&gt;satirical transcript&lt;/a&gt; was the *second* hit. Presumably because the title of the licentious page includes &quot;2003&quot;. The page got forty or fifty hits yesterday, versus approximately none in the previous week. Today, it&apos;s gone from Google, altogether.The most interesting thing is the question of why it suddenly got a high ranking. But we&apos;re pleased and proud that even if *China* doesn&apos;t censor licentious radio, Google *does*. (This isn&apos;t the first case.)There&apos;s also a rather interesting question as to how exactly Google chooses which pages to censor. Surely there&apos;s no one reporting our lame satire to a censor desk, but surely &quot;boob job&quot; isn&apos;t enough to get you whacked, either. Maybe there&apos;s a special &quot;be polite to Mad King George&quot; filter? That&apos;d be some clever code.Bottom line is what Ari said: people should watch what they say.</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/02/11.html#a1229</guid>			<pubDate>Tue, 11 Feb 2003 18:16:11 GMT</pubDate>			</item>		<item>			<description>From the SF Chronicle today: &quot;About 108 venture funds raised $6.9 billion during 2002, compared with 331 funds that raised $40.7 billion in 2001.... Because 26 firms gave $5 billion in uninvested money back to their limited partners, the net amount of new capital was just $1.9 billion last year -- a 95 percent drop from 2001.... In 2000, nearly $107 billion was raised by 653 funds.&quot;</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/02/11.html#a1224</guid>			<pubDate>Tue, 11 Feb 2003 15:09:27 GMT</pubDate>			</item>		<item>			<description>test</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/02/09.html#a1208</guid>			<pubDate>Sun, 09 Feb 2003 21:34:26 GMT</pubDate>			</item>		<item>			<description>&lt;a href=&quot;http://www.technorati.com/cosmos/links.html?rank=links&amp;url=http%3A//www.shirky.com/writings/powerlaw_weblog.html&quot;&gt;Rating links&lt;/a&gt; [technorati.com] to Shirky&apos;s article on weblogs.Top links right now: Scripting News 1490, Boing Boing Blog 1085, Instapundit.com 609. Megnut is #6 with 267. licentious radio is #21 with 16. (That&apos;s the number of &quot;inbound blogs&quot;.) We presume licentious radio&apos;s rank will fall as more websites link to the article. It&apos;s interesting how easy it is to find evidence of Shirky&apos;s point.</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/02/09.html#a1207</guid>			<pubDate>Sun, 09 Feb 2003 18:31:09 GMT</pubDate>			</item>		<item>			<description>&lt;a href=&quot;http://scriptingnews.userland.com/backissues/2003/02/09#clayStartAWeblogNow&quot;&gt;DaveNet Dave&lt;/a&gt; points to &lt;a href=&quot;http://www.shirky.com/writings/powerlaw_weblog.html&quot;&gt;Shirkey on weblogs&lt;/a&gt;. I don&apos;t quite get Dave&apos;s point. Shirky says weblog readership is a &quot;power law&quot; deal, where very few weblogs get huge readership, and almost all weblogs get very little readership, with many weblogs in between. I guess Dave is saying that weblogs are more niche-oriented. But I thought that&apos;s what Shirky was saying, too.</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/02/09.html#a1199</guid>			<pubDate>Sun, 09 Feb 2003 15:07:39 GMT</pubDate>			</item>		<item>			<description>Interesting claim on the Opera/MSN story.... They suggest MSN tweaked a stylesheet to work better with Opera 6. When Opera 7 came out, the tweaked stylesheet broke the layout, because of changes in the browser. I haven&apos;t tested this, but it sounds plausible (&lt;a href=&quot;http://slashdot.org/comments.pl?sid=53229&amp;cid=5263650&quot;&gt;slashdot comment&lt;/a&gt;).First, make your browser follow the standards. Second, when browser-sniffing, be aware that new versions will come out eventually, and the new versions will be specifically *different* than the current version. So limit your targeting to known versions. When Opera 7 comes out, give it some generic stylesheet until you take the time to figure out what you need to do to support it. </description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/02/09.html#a1198</guid>			<pubDate>Sun, 09 Feb 2003 14:41:11 GMT</pubDate>			</item>		<item>			<description>I guess that makes it official, then. I am the &lt;a href=&quot;http://www.google.com/search?hl=en&amp;ie=ISO-8859-1&amp;q=anti-zeldman&amp;btnG=Google+Search&quot;&gt;Anti-zeldman&lt;/a&gt; [google.com]. (ha ha)</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/02/09.html#a1197</guid>			<pubDate>Sun, 09 Feb 2003 14:12:33 GMT</pubDate>			</item>		<item>			<description>&lt;a href=&quot;http://radio.weblogs.com/0102813/stories/2002/06/20/launchdavewinerorgAnnounce.html&quot;&gt;LaunchDaveWiner.org&lt;/a&gt; spokesperson Leonard Nimoy announced partial victory today: &quot;There turned out to be some problems with sending Dave into orbit. The cost was one -- we raised a total of $83.68, somewhat short of the $40 million needed. But we *have* managed to send Dave to Harvard. It&apos;s still pretty far away, and he&apos;ll be there a lot longer, so we believe our four contributors will all be pleased.&quot;</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/01/25.html#a1103</guid>			<pubDate>Sat, 25 Jan 2003 17:27:43 GMT</pubDate>			</item>		<item>			<description>Underlining links was a *seriously* primitive choice for html. Underlining reduces readability, even if it adds emphasis. So your eye is attracted to the spot, but the text is difficult to read.CSS provides more options. Try: border-bottom: 1px; text-decoration: none. That also lets you get away from coloring the link text. You might want to add emphasis to a link by coloring it, but a lot of times there&apos;s no need. You can leave the text color alone, and just color the bottom border.If you add pretty good line-height to make your text more readable, then you can afford a little padding, so there&apos;s some whitespace between the bottom of descenders (&quot;gpqy&quot;) and the border. If you choose a border color that is lighter than the text, you probably have less need of extra padding.If you&apos;re worried that the border by itself doesn&apos;t add enough emphasis, try making it two pixels.I&apos;ve been playing with this for a couple of days. Today I ran across &lt;a href=&quot;http://www.new-series.org/?old_articles&quot;&gt;this site&lt;/a&gt;, with a pleasant gray background, and a darker gray border for links.</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/01/08.html#a1029</guid>			<pubDate>Wed, 08 Jan 2003 20:08:26 GMT</pubDate>			</item>		<item>			<description>One of the worst CSS tricks: set body text-align: center, and then a width for the content div. Anyone whose browser window isn&apos;t as wide as your div won&apos;t be able to see the whole page, won&apos;t even be able to scroll to read the part hidden *to the left* of the viewable area. (In Mozilla, at least.)Don&apos;t *do* this!</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/01/08.html#a1028</guid>			<pubDate>Wed, 08 Jan 2003 19:51:07 GMT</pubDate>			</item>		<item>			<description>One of the interesting questions in the current drive to using &quot;structure&quot; in html, is what we use structure *for*.Tantek Celik now makes &lt;a href=&quot;http://tantek.com/log/2003/01.html#L20030102t0602&quot;&gt;each weblog post a list item&lt;/a&gt;. It&apos;s true that a weblog is an ordered list of posts, as a book is an ordered list of chapters, a chapter is an ordered list of sections, and a section is an ordered list of paragraphs. It&apos;s also true that a paragraph is an ordered list of sentences, which are lists of words, which are lists of letters.Some structure may be useful to non-visual readers and robots -- using heading tags instead of visual-only markup is an example.Some structure is useful for transformations. If you aren&apos;t editing the same sequence of bytes that your readers see, you can do more interesting things. You could create a weblog xml language, so that when you write and edit, you are looking at (or generating) semantically meaningful tags. For example: &amp;lt;xblog&amp;gt; &amp;lt;blogitem date=&quot;&quot; time=&quot;&quot;&amp;gt;text here&amp;lt;/blogitem&amp;gt; &amp;lt;/xblog&amp;gt;. From that, your weblog software would build all the necessary links and anchors, and translate down to html so that any old browser could read it. You could add even more structure, of course.The problem with making up xml languages seems to be that the standard validation technology doesn&apos;t easily support mixing two document types. Eventually, that will be less of a problem.But when you think of using more structure, why? The standard reason is to make maintenance easier by using transformations to generate the final version. If you don&apos;t use automated transformations, using more structure might still make maintenance easier. But is it *really* much of an advantage to use list tags with classes, rather than div tags with classes? Tantek is doing a few tricky things. Rather than using class names in lists, the nesting of the lists implicitly holds the meaning. An &amp;lt;ol&amp;gt; for the month contains &amp;lt;li&amp;gt;s for the days, which contain an &amp;lt;ol&amp;gt; for the day&apos;s items.Then he puts the date and time into the value attribute of the list tags. Since the dates are in an ordered list, browsers should display the date as the number of the list item. The times are in an unordered list, so he has to repeat the time with a heading tag.All of this seems like a useful exploration, but I wonder who benefits. You probably save a few styles in CSS. It seems like it would be easier to create with a wysiwyg html editor, but you would still have to specify a couple of class attributes or copy/paste. If someone extracted a block of the source to use in a different setting, is there any benefit, or would it just be harder to understand? The fundamental issue seems to be that html was designed to indicate sections with heading tags at the start, but DOM (and XML) are desperate to wrap anything meaningful within a tag.Tantek&apos;s stylesheet then uses the nested structure to apply styles:&lt;pre&gt;ol.month li { clear:left; list-style:none }ol.month li { text-align:left;margin-top:2em }ol.month ol li { margin:0;margin-bottom:1em }ol.month ol ul li { margin:0 }ol.month ol ul ul,ol.month ol ul ol { margin:1em 0 1em 2em }ol.month ol ul ul li,ol.month ol ul ol li { margin:0 }ol.month ol ul ul li { list-style:disc }ol.month ol ul ol li { list-style:decimal }&lt;/pre&gt;*That* is the shape of things to come.</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2003/01/02.html#a1011</guid>			<pubDate>Thu, 02 Jan 2003 16:24:24 GMT</pubDate>			</item>		<item>			<description>Sigh. Have you patched Windows today? Bad guys can own your XP computer if you download an mp3, or if IE even *looks* at a hacked website: &quot;if the user browses to a malicious website with Internet Explorer directly, the attack will workregardless of the Internet Explorer security settings.&quot;Say somebody hacks into a popular website running Microsoft&apos;s webserver, sneaks in an iframe tag to another compromised computer -- anywhere on the web. Now before the popular website&apos;s people even notice, thousands or hundreds of thousands of computers are under the bad-guy&apos;s control.Brought to you by &quot;trustworthy computing&quot;. Note this is a bug in a feature that is part of Microsoft&apos;s long-term strategy of adding every conceivable feature in order to defeat the competition, no matter what the impact on security. You would think that Gates could set aside a billion dollars or so to train his people in the need for security. Think &quot;safety first&quot;. But the Microsofties all know how they kill the competition, and they aren&apos;t likely to change their ways because Gates has to mumble in public about security. Better to put the money into PR campaigns that 802.11 is unsafe, for example.</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2002/12/19.html#a988</guid>			<pubDate>Thu, 19 Dec 2002 14:55:36 GMT</pubDate>			</item>		<item>			<description>Follow-up on chronologically-ordered weblogs.... Here&apos;s a example of using client-side javascript and cookies to &lt;a href=&quot;http://radio.weblogs.com/0102813/images/blogsim.html&quot; target=new&gt;hide previously-viewed posts&lt;/a&gt; [new window].Why are blogs in reverse order? Partly because we don&apos;t want the server to remember which items each viewer has already seen. We also don&apos;t want the server to do the work of delivering only unseen items for each user. That would get expensive, compared to Radio, that generates static pages.The script uses client-side memory and processing power, which is scalable. That is, if a million people hit your weblog, the server doesn&apos;t have to do any extra work. The example assumes the server doesn&apos;t help by providing variables like the ids of the first and last items on the page. Slightly cooperative weblog software would reduce the complexity of the Javascript code.</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2002/12/18.html#a985</guid>			<pubDate>Thu, 19 Dec 2002 00:16:38 GMT</pubDate>			</item>		<item>			<description>Re-ordering weblogs is easy. Give it a separate page. Maybe restrict it to a shorter timespan. Use Javascript and DOM: 1) use Javascript to write a cookie with the id of the last-viewed entry.2) use Javascript to set &quot;display: none&quot; for the items that have already been read. This will work in fancy new browsers like IE5+, Mozilla, and NS6+. For old and primitive browsers, be sure to include a link to the (current) standard reverse-order page.3) add a link to display the hidden items.Not having done this yet, I presume the Javascript won&apos;t be entirely straightforward. Ideally, the weblog server software would give you access to variables for the last id, and the ids would have to be numerically ordered. Radio&apos;s ids will work. Of course the server software would have to give you the option. I don&apos;t know if any do, but it certainly wouldn&apos;t be hard.&lt;a href=&quot;http://scriptingnews.userland.com/backissues/2002/12/18#When:2:53:29AM&quot;&gt;Dave Winer&lt;/a&gt; provoked this outburst by linking to &lt;a href=&quot;http://nopundit.blogspot.com/2002_12_15_nopundit_archive.html&quot;&gt;Ken Hirsch&lt;/a&gt;.</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2002/12/18.html#a983</guid>			<pubDate>Wed, 18 Dec 2002 16:43:34 GMT</pubDate>			</item>		<item>			<description>Great virus coming soon to a computer near you: this one exploits one of those Microsoft destroy-the-competition features, emails itself to everyone in your email archive, and then erases your hard disk. Brought to you by trustworthy computing.I gotta say, a few really destructive viruses might just be in order to force Microsoft to change its ways in a hurry, not just cover their incompetence with PR spin.&lt;a href=&quot;http://www.infoworld.com/articles/hn/xml/02/11/27/021127hnwinevar.xml?s=IDGNS&quot;&gt;New worm, Winevar, packs a punch&lt;/a&gt; [infoworld.com].</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2002/11/30.html#a921</guid>			<pubDate>Sat, 30 Nov 2002 17:02:49 GMT</pubDate>			</item>		<item>			<description>I find it rather depressing that licentious radio is #1 on Google for &quot;smiling naked women&quot;. Even worse, there are only &lt;a href=&quot;http://www.google.com/search?hl=en&amp;ie=ISO-8859-1&amp;q=%22smiling+naked+women%22&quot;&gt;six hits&lt;/a&gt; for the search. </description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2002/10/08.html#a827</guid>			<pubDate>Wed, 09 Oct 2002 04:15:18 GMT</pubDate>			</item>		<item>			<description>More fun with licentious Google: we&apos;re #3 at Google for &lt;a href=&quot;http://www.google.com/search?hl=en&amp;ie=ISO-8859-1&amp;q=beef+subsidy&amp;btnG=Google+Search&quot;&gt;beef subsidy&lt;/a&gt; [google.com]. (Points to: &lt;a href=&quot;http://radio.weblogs.com/0102813/stories/2002/02/25/beefSubsidyTerroristsThrea.html&quot;&gt;Beef subsidy terrorists threatened with nukes&lt;/a&gt;.)</description>			<guid>http://radio.weblogs.com/0102813/categories/radioradio/2002/09/16.html#a794</guid>			<pubDate>Mon, 16 Sep 2002 21:37:38 GMT</pubDate>			</item>		</channel>	</rss>