<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Scripting News - Latest Comments in I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://scripting.disqus.com/</link><description></description><atom:link href="https://scripting.disqus.com/i_need_a_domain_name_server_with_a_rest_interface_scripting_news/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 18 Sep 2009 17:16:12 -0000</lastBuildDate><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16896917</link><description>&lt;p&gt;Using TXT is wrong for this. You should use NAPTR records.&lt;br&gt;You can rig it with TXT, but it doesn't make sense as NAPTR is specifically engineered for this.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Henri Asseily</dc:creator><pubDate>Fri, 18 Sep 2009 17:16:12 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16894900</link><description>&lt;p&gt;&lt;br&gt;This is working pretty well, send me an e-mail if you'd like to try it out. brian@megapump.com&lt;/p&gt;&lt;p&gt;The source code is published on github:&lt;br&gt;      &lt;a href="http://github.com/voitto/rsscloud_dns_server" rel="nofollow noopener" target="_blank" title="http://github.com/voitto/rsscloud_dns_server"&gt;http://github.com/voitto/rs...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;####################&lt;br&gt;## creating a zone record&lt;br&gt;####################&lt;/p&gt;&lt;p&gt;POST vars&lt;br&gt;---------------&lt;br&gt;name = "george"&lt;br&gt;record = "TXT"&lt;br&gt;feedname = "&lt;a href="http://george.loose.ly" rel="nofollow noopener" target="_blank" title="george.loose.ly"&gt;george.loose.ly&lt;/a&gt;"&lt;br&gt;key = md5( subdomain.record.value.pass ) where period concatenates values of these post vars and "pass" contains password value&lt;/p&gt;&lt;p&gt;API endpoint&lt;br&gt;------------------------------&lt;br&gt;&lt;a href="http://cloud.twitteronia.com/api/" rel="nofollow noopener" target="_blank" title="http://cloud.twitteronia.com/api/"&gt;http://cloud.twitteronia.co...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;New zone record&lt;br&gt;------------------------------&lt;br&gt;| 14 |    9 | george | TXT  |                                    |   0 | 86400 | &lt;a href="http://george.loose.ly" rel="nofollow noopener" target="_blank" title="george.loose.ly"&gt;george.loose.ly&lt;/a&gt; |&lt;/p&gt;&lt;p&gt;####################&lt;br&gt;## updating the feedname&lt;br&gt;####################&lt;/p&gt;&lt;p&gt;POST vars&lt;br&gt;---------------&lt;br&gt;name = "george"&lt;br&gt;record = "TXT"&lt;br&gt;feedname = "&lt;a href="http://george.twitteronia.com" rel="nofollow noopener" target="_blank" title="george.twitteronia.com"&gt;george.twitteronia.com&lt;/a&gt;"&lt;br&gt;key = md5( subdomain.record.value.pass ) where period concatenates values of these post vars and "pass" contains password value&lt;/p&gt;&lt;p&gt;API endpoint&lt;br&gt;------------------------------&lt;br&gt;&lt;a href="http://cloud.twitteronia.com/api/" rel="nofollow noopener" target="_blank" title="http://cloud.twitteronia.com/api/"&gt;http://cloud.twitteronia.co...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Updated zone record&lt;br&gt;------------------------------&lt;br&gt;| 14 |    9 | george | TXT  |                                    |   0 | 86400 | &lt;a href="http://george.twitteronia.com" rel="nofollow noopener" target="_blank" title="george.twitteronia.com"&gt;george.twitteronia.com&lt;/a&gt; |&lt;/p&gt;&lt;p&gt;######################&lt;br&gt;## updating the record data&lt;br&gt;######################&lt;/p&gt;&lt;p&gt;POST vars&lt;br&gt;---------------&lt;br&gt;name = "george"&lt;br&gt;record = "TXT"&lt;br&gt;feedname = "&lt;a href="http://george.twitteronia.com" rel="nofollow noopener" target="_blank" title="george.twitteronia.com"&gt;george.twitteronia.com&lt;/a&gt;"&lt;br&gt;feedurl = "&lt;a href="http://george.blogspot.com/posts.rss" rel="nofollow noopener" target="_blank" title="http://george.blogspot.com/posts.rss"&gt;http://george.blogspot.com/...&lt;/a&gt;"&lt;br&gt;key = md5( subdomain.record.value.pass ) where period concatenates values of these post vars and "pass" contains password value&lt;/p&gt;&lt;p&gt;API endpoint&lt;br&gt;------------------------------&lt;br&gt;&lt;a href="http://cloud.twitteronia.com/api/" rel="nofollow noopener" target="_blank" title="http://cloud.twitteronia.com/api/"&gt;http://cloud.twitteronia.co...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Updated zone record&lt;br&gt;------------------------------&lt;br&gt;| 14 |    9 | george | TXT  | &lt;a href="http://george.blogspot.com/posts.rss" rel="nofollow noopener" target="_blank" title="http://george.blogspot.com/posts.rss"&gt;http://george.blogspot.com/...&lt;/a&gt; |   0 | 86400 | &lt;a href="http://george.twitteronia.com" rel="nofollow noopener" target="_blank" title="george.twitteronia.com"&gt;george.twitteronia.com&lt;/a&gt; |&lt;/p&gt;&lt;p&gt;#############################&lt;br&gt;## REST feed lookup from feedname&lt;br&gt;#############################&lt;/p&gt;&lt;p&gt;(you can try this one yourself without authentication)&lt;/p&gt;&lt;p&gt;POST vars&lt;br&gt;---------------&lt;br&gt;name = "george"&lt;br&gt;record = "TXT"&lt;br&gt;feedname = "&lt;a href="http://george.loose.ly" rel="nofollow noopener" target="_blank" title="george.loose.ly"&gt;george.loose.ly&lt;/a&gt;"&lt;/p&gt;&lt;p&gt;API endpoint&lt;br&gt;------------------------------&lt;br&gt;&lt;a href="http://cloud.twitteronia.com/api/" rel="nofollow noopener" target="_blank" title="http://cloud.twitteronia.com/api/"&gt;http://cloud.twitteronia.co...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;(server performs a DNS lookup for TXT record at &lt;a href="http://george.loose.ly" rel="nofollow noopener" target="_blank" title="george.loose.ly"&gt;george.loose.ly&lt;/a&gt;)&lt;/p&gt;&lt;p&gt;Output&lt;br&gt;------------------------------&lt;br&gt;&lt;a href="http://george.blogspot.com/posts.rss" rel="nofollow noopener" target="_blank" title="http://george.blogspot.com/posts.rss"&gt;http://george.blogspot.com/...&lt;/a&gt;&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">brianjesse</dc:creator><pubDate>Fri, 18 Sep 2009 16:48:24 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16883871</link><description>&lt;p&gt;I have no idea what that other "serious implementation" is, but if we even haven't discussed the choice of record type to use, I can guarantee you that we're not going to get far in interoperability.&lt;br&gt;Here's my quick little thing:&lt;br&gt;http://67.23.22.13/dns/&lt;/p&gt;&lt;p&gt;It inserts into a .tel domain a NAPTR record of this type:&lt;br&gt;"E2U+x-feed:http"                "!^.*$!&lt;a href="http://rikkles.blogspot.com/feeds/posts/default!" rel="nofollow noopener" target="_blank" title="http://rikkles.blogspot.com/feeds/posts/default!"&gt;http://rikkles.blogspot.com...&lt;/a&gt;"&lt;/p&gt;&lt;p&gt;It says that it's a feed ("x-feed") using the http protocol, and the replacement string is (as is the case for all NAPTR records) a fully functioning regular expression.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Henri Asseily</dc:creator><pubDate>Fri, 18 Sep 2009 13:52:25 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16880307</link><description>&lt;p&gt;Dave,&lt;/p&gt;&lt;p&gt;Rackspace would like to offer you some comped slices on Slicehost for your dev work.  That will give you a RESTful interface to both compute and DNS, including TXT record manipulation.  If you are interested, please e-mail me at erik.carlin at &lt;a href="http://rackspace.com" rel="nofollow noopener" target="_blank" title="rackspace.com"&gt;rackspace.com&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;Regards,&lt;br&gt;Erik&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Erik Carlin</dc:creator><pubDate>Fri, 18 Sep 2009 12:44:00 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16874930</link><description></description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Guest</dc:creator><pubDate>Fri, 18 Sep 2009 11:05:36 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16874900</link><description></description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Guest</dc:creator><pubDate>Fri, 18 Sep 2009 11:04:58 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16871895</link><description>&lt;p&gt;A heads-up that there's another serious implementation that's reaching closure. I hope you guys share ideas and perhaps we could even have an interoperating REST interface for DNS administration. I would totally support that (with code of my own, on the client side).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Fri, 18 Sep 2009 09:55:29 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16871757</link><description>&lt;p&gt;Yep I'll publish the source code that took all of 3 hours to write very soon.&lt;br&gt;By the way, there's a major issue with "let's make a simple API for the DNS" in that the DNS ain't that simple. So in order to make a simple API, you have to do the hard work of getting rid of what you don't want.&lt;br&gt;Luckily when you're using .tel domains you already have a couple of APIs you can use, and making simple wrappers for those is quite easy.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Henri Asseily</dc:creator><pubDate>Fri, 18 Sep 2009 09:51:53 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16853318</link><description>&lt;p&gt;what do you suggest regarding the spoofing vulnerabilty?  &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">sull</dc:creator><pubDate>Thu, 17 Sep 2009 22:04:05 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16853002</link><description>&lt;p&gt;For the sake of completeness, here are some problems for using DNS as a generalized service registry.  They may or may not affect the 140 char loosely coupled network ("&lt;a href="http://Loose.ly" rel="nofollow noopener" target="_blank" title="Loose.ly"&gt;Loose.ly&lt;/a&gt;").&lt;/p&gt;&lt;p&gt;1. The DNS cache can be slow to propagate, meaning there's an indeterminate lag between modifying a service endpoint (e.g. a feed address) and being able to use it fully.  The best case for DNS NAPTR records is probably a 1-5 minutes lag, but it's ultimately up to each ISP's nameserver to decide how they want to setup their cache.  The shorter the TTL, the less caching you get.&lt;/p&gt;&lt;p&gt;2. Javascript in the browser cannot make the socket connection to do a DNS lookup.  Javascript widgets will need to contact some server running an HTTP service that bridges to a DNS lookup.  And of course, an HTTP service is what most developers today will want to contact in the first place, Andy's fair points above notwithstanding.&lt;/p&gt;&lt;p&gt;3. Lastly, a general point which probably does not affect &lt;a href="http://Loose.ly" rel="nofollow noopener" target="_blank" title="Loose.ly"&gt;Loose.ly&lt;/a&gt;'s casual use case:  DNS is vulnerable to easy spoofing attacks and so cannot be used for looking up some other types of service endpoints, such as OpenID's single-sign-on delegation, or OAuth's authentication endpoints, or a person's public keys for digital signatures.&lt;/p&gt;&lt;p&gt;Just wanted to get that on the record.  None of this is to say it can't work.  Obviously DNS sure is clean and simple :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mason Lee</dc:creator><pubDate>Thu, 17 Sep 2009 21:55:12 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16835835</link><description>&lt;p&gt;right, i mentioned this in my comment as well.  &lt;br&gt;i have not tried dreamhost's API but the DNS hooks are there. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">sull</dc:creator><pubDate>Thu, 17 Sep 2009 17:08:00 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16835771</link><description>&lt;p&gt;i assume you plan to release to the telnic dev community?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">sull</dc:creator><pubDate>Thu, 17 Sep 2009 17:07:06 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16810615</link><description>&lt;p&gt;&lt;br&gt;I made a REST API like this, you can find the documentation at &lt;a href="http://cloud.twitteronia.com" rel="nofollow noopener" target="_blank" title="http://cloud.twitteronia.com"&gt;http://cloud.twitteronia.com&lt;/a&gt; - would love to have feedback here on whether it works. Thanks!  -- Brian&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">brianjesse</dc:creator><pubDate>Thu, 17 Sep 2009 10:05:44 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16807611</link><description></description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Guest</dc:creator><pubDate>Thu, 17 Sep 2009 08:45:55 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16805702</link><description>&lt;p&gt;Don't forget guys.&lt;br&gt; If you are going to be using Friendfeed-Like long polling here, Facebook opensourced Friendfeed's web server (that just sounds wrong), named Tornado.&lt;/p&gt;&lt;p&gt;Find it here: &lt;a href="http://www.tornadoweb.org/" rel="nofollow noopener" target="_blank" title="http://www.tornadoweb.org/"&gt;http://www.tornadoweb.org/&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">rbonini</dc:creator><pubDate>Thu, 17 Sep 2009 07:25:10 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16804348</link><description>&lt;p&gt;I'm pretty much done with your requested interface. I'm implementing a simple authentication mechanism right now, should be done in an hour or so.&lt;br&gt;Ping me offline for the info (&lt;a href="http://henri.tel" rel="nofollow noopener" target="_blank" title="http://henri.tel"&gt;http://henri.tel&lt;/a&gt; or twitter or whatever you prefer)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Henri Asseily</dc:creator><pubDate>Thu, 17 Sep 2009 05:58:50 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16801509</link><description>&lt;p&gt;I am now sure if this is exactly what you are looking for but take a look at the API of &lt;a href="http://dreamhost.com" rel="nofollow noopener" target="_blank" title="http://dreamhost.com"&gt;http://dreamhost.com&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://wiki.dreamhost.com/Application_programming_interface" rel="nofollow noopener" target="_blank" title="http://wiki.dreamhost.com/Application_programming_interface"&gt;http://wiki.dreamhost.com/A...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Hanan Cohen</dc:creator><pubDate>Thu, 17 Sep 2009 03:15:18 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16799691</link><description>&lt;p&gt;By the same token that developers want to use HTTP POST to register their feed, won't developers want to use HTTP GET to resolve the names to feeds?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mason Lee</dc:creator><pubDate>Thu, 17 Sep 2009 01:39:44 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16799028</link><description>&lt;p&gt;You mean something like this?&lt;/p&gt;&lt;p&gt;&lt;a href="http://dvlop.in/" rel="nofollow noopener" target="_blank" title="http://dvlop.in/"&gt;http://dvlop.in/&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AndrewBurton</dc:creator><pubDate>Thu, 17 Sep 2009 01:06:52 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16798851</link><description>&lt;p&gt;Ok I'll try to get a prototype for you out today.&lt;br&gt;But it won't be a 'TXT' record, it'll be 'NAPTR'. Makes a lot more sense to use NAPTR, as this is a URI we're talking about, as a value.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Henri Asseily</dc:creator><pubDate>Thu, 17 Sep 2009 00:59:58 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16791838</link><description></description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Guest</dc:creator><pubDate>Wed, 16 Sep 2009 23:17:44 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16791400</link><description>&lt;p&gt;You need a big hug. Get going with the coding up a RESTful gateway for .tel and we;re in business. And stop worrying so much! :-)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Wed, 16 Sep 2009 23:03:27 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16790908</link><description></description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Guest</dc:creator><pubDate>Wed, 16 Sep 2009 22:51:08 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16790427</link><description>&lt;p&gt;The long polling is interesting. I'm working on that.  Some claim that eases resources on the edge and that makes sense.&lt;/p&gt;&lt;p&gt;But I was thinking today. One argument is that we need to remove the burden from the publisher, so they don't get thousands of requests when they notify everyone of new content.&lt;/p&gt;&lt;p&gt;And I say, "Okay. Put their feed on S3 or some other CDN if they are big enough to need it." Burden over.&lt;/p&gt;&lt;p&gt;Is there someone that would be willing to have a central "hub" deliver their content to subscribers and relieve their burden, but unwilling to have a neutral host serve it and relieve their burden?&lt;/p&gt;&lt;p&gt;Explain to me where the problem lies.&lt;/p&gt;&lt;p&gt;Another meetup? Yeah!!!! I want Corned Beef or Pizza this time. Lombardis or Katz! They don't eat this well at those fancy conferences! ; )&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mterenzio</dc:creator><pubDate>Wed, 16 Sep 2009 22:38:30 -0000</pubDate></item><item><title>Re: I need a Domain Name Server with a REST interface (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/16/iNeedADomainNameServerWith.html#comment-16789568</link><description>&lt;p&gt;I don't want SOAP or JSON -- I want REST.&lt;/p&gt;&lt;p&gt;I know what I'm taking about Andy. I know how to listen to people, and I know what they will go for.&lt;/p&gt;&lt;p&gt;And right now -- in 2009 that's REST.&lt;/p&gt;&lt;p&gt;I do get annoyed when people say I want to put the entire cloud under one namespace. That would be idiotic. I am not an idiot. You shoudl have rejected the notion based on that alone.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Wed, 16 Sep 2009 22:20:10 -0000</pubDate></item></channel></rss>