cpjolicoeur

<p>FeedCache Pipes will retrieve, cache and store locally a list of RSS feeds that you can then display on your WP site. This prevents multiple HTTP requests with each page load since the feeds can be read from the cache file.</p>
<h3>Requirements</h3>
<ul>
<li>Ruby</li>
<li>CRON access</li>
</ul>
<h3>Upgrading</h3>
<ol>
<li>
<p>Deactivate the previous version of FeedCache Pipes through your WordPress plugins menu</p>
</li>
<li>
<p>Upload the new feedcache-cron.rb, feedcache-pipes.php and complete lib/ directory files to your existing feedcache-pipes directory.  You do not need to overwrite your existing files/ directory or the fcpipes-config.yml file.</p>
</li>
<li>
<p>Activate the newly uploaded plugin.</p>
<ul>
<li>Go to Settings -> FeedCache Pipes and update your FeedCache Pipes settings (click update even if you haven’t made changes)</li>
</ul>
</li>
<li>
<p>Enter the correct FCPIPES_DIR variable in the feedcache-cron.rb script</p>
<ul>
<li>update your MYSQL_SOCKET setting as well if the MySQL socket on your server is not the default (/tmp/mysql.sock)</li>
</ul>
</li>
</ol>


FeedCache Pipes

Caches RSS Feeds for display on your WP sidebar. A list of RSS urls can be entered and the feeds will be aggregated into one list ordered by date.

padraic

<p>Implements <a href="http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.1.html" title="the PubSubHubbub protocol" rel="nofollow ugc">the Pubsubhubbub protocol</a> based on the current PubSubHubbub Core 0.1 Specification and any changes since its publication. <a href="http://code.google.com/p/pubsubhubbub/" title="PubSubHubbub" rel="nofollow ugc">PubSubHubbub</a> is an open, simple web-scale pubsub (publish/subscribe) protocol capable of notifying one or more Hub Servers (e.g. the reference open source <a href="http://pubsubhubbub.appspot.com/" title="implementation on Google App Engine" rel="nofollow ugc">implementation on Google App Engine</a>) of your blog updates so they may be forwarded to any of your feed’s Pubsubhubbub enabled Subscribers as quickly as possible.</p>
<p>Any Pubsubhubbub enabled Subscriber can then receive an almost immediate update from any of your Hubs containing the actual update for immediate use. Subscribers know what Hubs to use when subscribing to your RSS 0.92, RDF/RSS 1.0, RSS 2.0, or Atom 1.0 feeds since this plugin will insert one or more links to your configured Hubs into these feeds.</p>
<p>WP Pubsubhubbub has the following features:</p>
<ul>
<li>Supports multiple Hubs configured from the settings page</li>
<li>Pings all Hubs whenever you publish/edit a blog post</li>
<li>Adds suitable Atom namespaced link elements for each configured Hub to the top of your RSS 0.92, RDF/RSS 1.0, RSS 2.0, or Atom 1.0 feeds</li>
<li>Maintains compliance with the Pubsubhubbub 0.1 Core Specification and any outstanding amendments</li>
<li>WP Pubsubhubbub utilises a Pubsubhubbub Publisher implementation which is fully unit tested for reliability and specification conformance, based on Zend Framework’s upcoming Pubsubhubbub component for which I am the lead developer.</li>
<li>Where no replacement Hubs are configured, WP Pubsubhubbub defaults to the reference Hub hosted on Google App Engine. This is a very reliable Hub. We also default to using the Superfeedr Hub as an alternative to ensure reliable service. You may replace or add to this list as needed.</li>
<li>Version 1.1.0 also enables Hub notification of changes to your RSS 2.0 Comment Feeds</li>
</ul>
<p>As the specification authors state on the main Pubsubhubbub site, the protocol is decentralized and free. No company is at the center controlling it. Anybody can run a hub, or anybody can ping (publish) or subscribe using open hubs.</p>


WP Pubsubhubbub

Implements a Pubsubhubbub Real Time Publisher informing Planet Earth of your updates now, not later!

FeedCache Pipes vs WP Pubsubhubbub