<?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 DNS for RSS feeds (Scripting News)</title><link>http://scripting.disqus.com/</link><description></description><atom:link href="https://scripting.disqus.com/dns_for_rss_feeds_scripting_news/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 21 Sep 2009 13:23:01 -0000</lastBuildDate><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17043284</link><description>&lt;p&gt;that's how I designed my rssCloud Rest/DNS server.. when you make a new zone like &lt;a href="http://supercloud.org" rel="nofollow noopener" target="_blank" title="supercloud.org"&gt;supercloud.org&lt;/a&gt;, it puts an A record there at the top level and then starts pumping out new TXT records for the subdomains&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">brianjesse</dc:creator><pubDate>Mon, 21 Sep 2009 13:23:01 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17040461</link><description>&lt;p&gt;Do popular DNS hosts support NAPTR record configuration?  I didn't see support at the DNS host that I use.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tommy Jones</dc:creator><pubDate>Mon, 21 Sep 2009 12:15:38 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17037081</link><description>&lt;p&gt;Right, but why not treat your browser as an aggregator? Do you know if there's a way to get this in JavaScript?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dean Michael Berris</dc:creator><pubDate>Mon, 21 Sep 2009 10:52:43 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17036641</link><description>&lt;p&gt;It's not for browsers, it's for aggregators.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Mon, 21 Sep 2009 10:41:02 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17036460</link><description>&lt;p&gt;Hey Dave, are TXT records cached just like the A's and CNAME entries? And besides, this means application specific knowledge for fetching TXT records -- hardly something browsers right now support. Cool idea still.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dean Michael Berris</dc:creator><pubDate>Mon, 21 Sep 2009 10:36:24 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17035808</link><description>&lt;p&gt;Doh! thanks for the correction... haven't had enough coffee yet! Trying to&lt;br&gt;re-invent myself as a morning person (kid in middle school) and that's&lt;br&gt;fighting decades of late-nightism ;-)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Fred Davis</dc:creator><pubDate>Mon, 21 Sep 2009 10:21:16 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17035617</link><description>&lt;p&gt;@Fred Your RSS feed is this:&lt;/p&gt;&lt;p&gt;&lt;a href="http://twitter.com/statuses/user_timeline/14270436.rss" rel="nofollow noopener" target="_blank" title="http://twitter.com/statuses/user_timeline/14270436.rss"&gt;http://twitter.com/statuses...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steve Garfield</dc:creator><pubDate>Mon, 21 Sep 2009 10:15:07 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17035462</link><description>&lt;p&gt;&lt;a href="http://twitter.com/freddavis" rel="nofollow noopener" target="_blank" title="twitter.com/freddavis"&gt;twitter.com/freddavis&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Fred Davis</dc:creator><pubDate>Mon, 21 Sep 2009 10:10:19 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17035253</link><description>&lt;p&gt;What's the URL of your feed?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Mon, 21 Sep 2009 10:04:02 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17035172</link><description>&lt;p&gt;Hmmmm... got an error msg: "We couldn't read your feed, or it isn't valid XML." Twitter Fail Whale?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Fred Davis</dc:creator><pubDate>Mon, 21 Sep 2009 10:02:00 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17028045</link><description>&lt;p&gt;A possible solution would be to create a new DNS Resource Record Type instead of reusing TXT once again.&lt;/p&gt;&lt;p&gt;This is the approach favored by IAB, in RFC 5507, "Design Choices When Expanding DNS"&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stéphane Bortzmeyer</dc:creator><pubDate>Mon, 21 Sep 2009 04:04:30 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17027846</link><description>&lt;p&gt;Hi Tommy, why not use NAPTR instead (or in addition)?&lt;br&gt;I just published a post explaining why I think NAPTR is much better than TXT for this: &lt;a href="http://rikkles.blogspot.com/2009/09/rsscloud.html" rel="nofollow noopener" target="_blank" title="http://rikkles.blogspot.com/2009/09/rsscloud.html"&gt;http://rikkles.blogspot.com...&lt;/a&gt;&lt;br&gt;Essentially, NAPTR gives the following advantages:&lt;br&gt;- service type and protocol&lt;br&gt;- order and preference&lt;br&gt;- regex replacement (not just mapping)&lt;/p&gt;&lt;p&gt;NAPTR works on any TLD as well.&lt;br&gt;I'd be interested to know your thoughts as to the relative advantages of DNS-SD and NAPTR.&lt;/p&gt;&lt;p&gt;And my own Disclosure: I work with Telnic, the registry for .tel. .tel domains extensively use NAPTR records for discovery of communication channels (any URIs, essentially)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Henri Asseily</dc:creator><pubDate>Mon, 21 Sep 2009 03:46:23 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17023407</link><description>&lt;p&gt;On a bit of a tangent, that raises what could be an interesting side-effect. The major client-side implementations (Apple Bonjour and Avahi) implement multicast DNS for advertising services to the local network using the "local." namespace. With an appropriately enabled reader it would in-effect be a primitive form of location-based discovery.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Guest</dc:creator><pubDate>Mon, 21 Sep 2009 00:08:58 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17014488</link><description>&lt;p&gt;The other protocol to consider is WebFinger:  &lt;a href="http://hueniverse.com/2009/08/introducing-webfinger/" rel="nofollow noopener" target="_blank" title="http://hueniverse.com/2009/08/introducing-webfinger/"&gt;http://hueniverse.com/2009/...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;At a high level, WebFinger can be used to map "user@domain" do a document describing the user. The document can link to just about anything, so WebFinger can be used to find the user's rss feed, avatar image and other user metadata that might be useful in the 140 char network.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tommy Jones</dc:creator><pubDate>Sun, 20 Sep 2009 23:29:48 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17013919</link><description>&lt;p&gt;Note that a DNS host does not need to have specific support for DNS-SD as long as the host supports SRV, TXT and PTR records.  DNS-SD does not define anything new at the DNS layer, but instead describes how to use existing DNS features as a service discovery mechanism. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tommy Jones</dc:creator><pubDate>Sun, 20 Sep 2009 23:20:01 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17012852</link><description></description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Guest</dc:creator><pubDate>Sun, 20 Sep 2009 23:05:05 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17009025</link><description>&lt;p&gt;Thanks for the info and especiallly thanks for the disclosure. Everyone who pitches some product, service or protocol should say what interest they have in it, or say they have none if they have none. So seriously thanks.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Sun, 20 Sep 2009 22:36:25 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17008173</link><description>&lt;p&gt;DNS-SD as method of finding a persons public services could be quite cool. For those not familiar DNS-SD uses PTR, SRV and TXT records to advertise services. To find services you look for PTR records name _servicetype._protocol.domain. So to find all the HTTP services associated with me you could look up &lt;a href="http://_http._tcp.andrewtj.com" rel="nofollow noopener" target="_blank" title="http://_http._tcp.andrewtj.com"&gt;_http._tcp.andrewtj.com&lt;/a&gt;. which might give you something like the following:&lt;br&gt;&lt;br&gt;&lt;a href="http://_http._tcp.andrewtj.com" rel="nofollow noopener" target="_blank" title="http://_http._tcp.andrewtj.com"&gt;_http._tcp.andrewtj.com&lt;/a&gt;. PTR AndrewTJ's\032RSS\032Feed&lt;br&gt;&lt;a href="http://_http._tcp.andrewtj.com" rel="nofollow noopener" target="_blank" title="http://_http._tcp.andrewtj.com"&gt;_http._tcp.andrewtj.com&lt;/a&gt;. PTR AndrewTJ's\032FriendFeed&lt;br&gt;&lt;a href="http://_http._tcp.andrewtj.com" rel="nofollow noopener" target="_blank" title="http://_http._tcp.andrewtj.com"&gt;_http._tcp.andrewtj.com&lt;/a&gt;. PTR AndrewTJ's\032Twitter&lt;br&gt;&lt;br&gt;\032 is how a space is encoded in a DNS name so the above would display a list like:&lt;br&gt;AndrewTJ's RSS Feed&lt;br&gt;AndrewTJ's FriendFeed&lt;br&gt;AndrewTJ's Twitter&lt;br&gt;&lt;br&gt;Subtypes of services are also catered for - if you were just after RSS only you could look up &lt;a href="http://_rss._sub._http._tcp.andrewtj.com" rel="nofollow noopener" target="_blank" title="http://_rss._sub._http._tcp.andrewtj.com"&gt;_rss._sub._http._tcp.andrewtj.com&lt;/a&gt;, eg:&lt;br&gt;&lt;br&gt;&lt;a href="http://_rss._sub._http._tcp.andrewtj.com" rel="nofollow noopener" target="_blank" title="http://_rss._sub._http._tcp.andrewtj.com"&gt;_rss._sub._http._tcp.andrewtj.com&lt;/a&gt;. PTR AndrewTJ's\032RSS\032Feed&lt;br&gt;&lt;br&gt;To then resolve the service you grab the TXT and SRV records the PTR points to:&lt;br&gt;&lt;br&gt;AndrewTJ's\032RSS\&lt;a href="http://032Feed._http._tcp.andrewtj.com" rel="nofollow noopener" target="_blank" title="http://032Feed._http._tcp.andrewtj.com"&gt;032Feed._http._tcp.andrewtj.com&lt;/a&gt;. SRV 0 0 80 &lt;a href="http://andrewtj.com" rel="nofollow noopener" target="_blank" title="http://andrewtj.com"&gt;andrewtj.com&lt;/a&gt;.&lt;br&gt;AndrewTJ's\032RSS\&lt;a href="http://032Feed._http._tcp.andrewtj.com" rel="nofollow noopener" target="_blank" title="http://032Feed._http._tcp.andrewtj.com"&gt;032Feed._http._tcp.andrewtj.com&lt;/a&gt;. TXT path=/rss.xml&lt;br&gt;&lt;br&gt;Under DNS-SD only the target and port from the SRV record are used, in this case — &lt;a href="http://andrewtj.com" rel="nofollow noopener" target="_blank" title="http://andrewtj.com"&gt;andrewtj.com&lt;/a&gt; on port 80. The TXT record contains key=value pairs which are service-specific. In the case of _http._tcp., 'u' and 'p' have been defined for use as username and password key names along with 'path' for the path. The end result: &lt;a href="http://andrewtj.com" rel="nofollow noopener" target="_blank" title="http://andrewtj.com"&gt;http://andrewtj.com&lt;/a&gt;:80/rss.xml&lt;br&gt;&lt;br&gt;More information on DNS-SD can be found at &lt;a href="http://dns-sd.org" rel="nofollow noopener" target="_blank" title="http://dns-sd.org"&gt;dns-sd.org&lt;/a&gt;.&lt;br&gt;&lt;br&gt;Disclosure: I'm building a DNS-SD Firefox extension (&lt;a href="http://bonjourfoxy.net" rel="nofollow noopener" target="_blank" title="http://bonjourfoxy.net"&gt;bonjourfoxy.net&lt;/a&gt;) and a DNS-SD hosting service so I happen to think DNS-SD is kinda neat ;)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Guest</dc:creator><pubDate>Sun, 20 Sep 2009 22:31:08 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17007925</link><description>&lt;p&gt;Okay thanks -- now no more selling of .tel. This is the last comment on this topic. We understand what it is. We'll use it if we want to. Thanks.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Sun, 20 Sep 2009 22:29:36 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17005774</link><description></description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Guest</dc:creator><pubDate>Sun, 20 Sep 2009 22:13:52 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17003610</link><description>&lt;p&gt;What I like about it is that it's connecting up the lizard brain -- DNS with the cerebral cortex -- HTTP. They're at opposite ends of the evolutionary spectrum, but they're still a nice way to integrate them.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Sun, 20 Sep 2009 21:56:31 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17002306</link><description>&lt;p&gt;I like that idea, hadn't thought of a combo deal. :)&lt;/p&gt;&lt;p&gt;Anything where the user only needs to know one thing (their address) and the technology (browser/cloud app) figures the rest out seamless is a good way to start.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jeremy Felt</dc:creator><pubDate>Sun, 20 Sep 2009 21:39:52 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17002119</link><description>&lt;p&gt;BTW, it's not at all impossible to have &lt;a href="http://dave.supercloud.org" rel="nofollow noopener" target="_blank" title="dave.supercloud.org"&gt;dave.supercloud.org&lt;/a&gt; redirect to my feed, even if it's just a TXT record, without doing anything horrible. The DNS would return the same IP address for all *.supercloud.org hosts, where the web server would look up the host's TXT record and redirect to it. Nicely loosely coupled, no hacks, it should work.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Sun, 20 Sep 2009 21:34:33 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17002041</link><description>&lt;p&gt;We're doing all this work, in part, to stop working for Twitter-the-Company, at least I am. I'm so fed up with these business models that have a line that says Over Here You Are And You Don't Get Paid and Over Here Are We and We Make Huge Money. Fuck it. If I'm going to make nothing I'll do it where no one makes anything. Telnic looks like Twitter except they don't have the critical mass. What are they offering us other than free use of their TLD. I paid $10 for &lt;a href="http://supercloud.org" rel="nofollow noopener" target="_blank" title="supercloud.org"&gt;supercloud.org&lt;/a&gt;. Okay that's a nice deal. I get $10 and...?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Sun, 20 Sep 2009 21:31:47 -0000</pubDate></item><item><title>Re: DNS for RSS feeds (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/20/dnsForRssFeeds.html#comment-17001519</link><description>&lt;p&gt;To some extent, I can't blame them.&lt;br&gt;Everyone is just trying to make nice things out of prior art. :)&lt;/p&gt;&lt;p&gt;But you said it right there. "they've got a nice web app for editing my DNS profile";&lt;/p&gt;&lt;p&gt;So to some degree they just lowered another barrier for people who do not/cannot/will not run their own Internet enabled vCard and they also just happened to have the right amount of money for ICANN to bless them with control over a TLD.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">playerx</dc:creator><pubDate>Sun, 20 Sep 2009 21:12:23 -0000</pubDate></item></channel></rss>