<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The NetDNA Blog</title>
	<atom:link href="http://blog.netdna.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.netdna.com</link>
	<description>Keep up with everything NetDNA</description>
	<lastBuildDate>Fri, 24 May 2013 23:27:01 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Converting Our API Docs from Closed to Open</title>
		<link>http://blog.netdna.com/developer/converting-our-api-docs-from-closed-to-open/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=converting-our-api-docs-from-closed-to-open</link>
		<comments>http://blog.netdna.com/developer/converting-our-api-docs-from-closed-to-open/#comments</comments>
		<pubDate>Fri, 24 May 2013 20:54:46 +0000</pubDate>
		<dc:creator>Guest Post</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[docs]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[github]]></category>
		<category><![CDATA[grunt]]></category>
		<category><![CDATA[markdown]]></category>
		<category><![CDATA[maxcdn]]></category>
		<category><![CDATA[netdna]]></category>
		<category><![CDATA[node]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[wintersmith]]></category>

		<guid isPermaLink="false">http://blog.netdna.com/?p=2520</guid>
		<description><![CDATA[This guest post is by Nick Baugh, an open source developer from the east coast. He has developed over 30+ MIT-licensed NPM modules for Node.js that receive 4000+ monthly user downloads. You can follow him on Twitter, or write him &#8230; <a href="http://blog.netdna.com/developer/converting-our-api-docs-from-closed-to-open/">Continued</a>]]></description>
		<wfw:commentRss>http://blog.netdna.com/developer/converting-our-api-docs-from-closed-to-open/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Now Accepting Bitcoins</title>
		<link>http://blog.netdna.com/maxcdn/now-accepting-bitcoins/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=now-accepting-bitcoins</link>
		<comments>http://blog.netdna.com/maxcdn/now-accepting-bitcoins/#comments</comments>
		<pubDate>Tue, 14 May 2013 17:30:44 +0000</pubDate>
		<dc:creator>Justin Dorfman</dc:creator>
				<category><![CDATA[MaxCDN]]></category>
		<category><![CDATA[bitcoin]]></category>
		<category><![CDATA[bitpay]]></category>
		<category><![CDATA[maxcdn]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[payment]]></category>

		<guid isPermaLink="false">http://blog.netdna.com/?p=2512</guid>
		<description><![CDATA[We&#8217;re happy to announce that we now accept Bitcoins as payment on the MaxCDN order form. We’re supporters of the open source ecosystem, and a large component is being responsive to requests from the community. Developers, a core portion of our &#8230; <a href="http://blog.netdna.com/maxcdn/now-accepting-bitcoins/">Continued</a>]]></description>
		<wfw:commentRss>http://blog.netdna.com/maxcdn/now-accepting-bitcoins/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>W3 Total Cache + MaxCDN</title>
		<link>http://blog.netdna.com/maxcdn/w3-total-cache-maxcdn/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=w3-total-cache-maxcdn</link>
		<comments>http://blog.netdna.com/maxcdn/w3-total-cache-maxcdn/#comments</comments>
		<pubDate>Tue, 14 May 2013 01:20:39 +0000</pubDate>
		<dc:creator>David Henzel</dc:creator>
				<category><![CDATA[MaxCDN]]></category>
		<category><![CDATA[cdnpanel]]></category>
		<category><![CDATA[maxcdn]]></category>
		<category><![CDATA[plugin]]></category>
		<category><![CDATA[pull zone]]></category>
		<category><![CDATA[reporting]]></category>
		<category><![CDATA[w3 total cache]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://blog.netdna.com/?p=2396</guid>
		<description><![CDATA[Today, we&#8217;re happy to announce new integration of MaxCDN &#38; NetDNA with the W3 Total Cache WordPress plugin. We wanted it to be dead simple to speed up your WordPress blog: Create a Pull Zone with one click Get basic &#8230; <a href="http://blog.netdna.com/maxcdn/w3-total-cache-maxcdn/">Continued</a>]]></description>
		<wfw:commentRss>http://blog.netdna.com/maxcdn/w3-total-cache-maxcdn/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>How To Improve Your SEO With Robots.txt and Canonical Headers</title>
		<link>http://blog.netdna.com/maxcdn/manage-seo-with-cdn/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=manage-seo-with-cdn</link>
		<comments>http://blog.netdna.com/maxcdn/manage-seo-with-cdn/#comments</comments>
		<pubDate>Fri, 10 May 2013 18:20:27 +0000</pubDate>
		<dc:creator>Ivan Dabic</dc:creator>
				<category><![CDATA[MaxCDN]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[CDN]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[maxcdn]]></category>
		<category><![CDATA[netdna]]></category>
		<category><![CDATA[robots.txt]]></category>
		<category><![CDATA[sem]]></category>
		<category><![CDATA[seo]]></category>

		<guid isPermaLink="false">http://blog.netdna.com/?p=2502</guid>
		<description><![CDATA[Search engine crawlers (aka spiders or bots), scan your site and index whatever they can. This happens whether you like it or not, and you might not like sensitive or autogenerated files, such as internal search results, showing up on &#8230; <a href="http://blog.netdna.com/maxcdn/manage-seo-with-cdn/">Continued</a>]]></description>
		<wfw:commentRss>http://blog.netdna.com/maxcdn/manage-seo-with-cdn/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>May 15th: XML-RPC API Blackout</title>
		<link>http://blog.netdna.com/developer/may-15th-xml-rpc-api-blackout/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=may-15th-xml-rpc-api-blackout</link>
		<comments>http://blog.netdna.com/developer/may-15th-xml-rpc-api-blackout/#comments</comments>
		<pubDate>Tue, 07 May 2013 22:45:17 +0000</pubDate>
		<dc:creator>Eamonn Pascal</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[blackout]]></category>
		<category><![CDATA[maxcdn]]></category>
		<category><![CDATA[netdna]]></category>
		<category><![CDATA[rest]]></category>
		<category><![CDATA[rws]]></category>
		<category><![CDATA[xml-rpc]]></category>

		<guid isPermaLink="false">http://blog.netdna.com/?p=2503</guid>
		<description><![CDATA[Last year we released an alpha version of our REST API to replace our XML-RPC API. After a solid two years of development and testing, the new REST API is ready for prime time. Although most of our customers have &#8230; <a href="http://blog.netdna.com/developer/may-15th-xml-rpc-api-blackout/">Continued</a>]]></description>
		<wfw:commentRss>http://blog.netdna.com/developer/may-15th-xml-rpc-api-blackout/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
