<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Integrating Gnip Notifications</title>
	<atom:link href="http://blog.gnip.com/integrating-gnip-notifications/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.gnip.com/integrating-gnip-notifications/</link>
	<description>Social media data tracking, updates from Twitter, Facebook, and other publishers, Gnip product updates, and more.</description>
	<lastBuildDate>Mon, 09 Jan 2012 18:39:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: AJ McKee &#187; Blog Archive &#187; Building a Simple PHP Twitter Client Without Twitter</title>
		<link>http://blog.gnip.com/integrating-gnip-notifications/comment-page-1/#comment-100</link>
		<dc:creator>AJ McKee &#187; Blog Archive &#187; Building a Simple PHP Twitter Client Without Twitter</dc:creator>
		<pubDate>Sat, 18 Oct 2008 12:55:42 +0000</pubDate>
		<guid isPermaLink="false">http://Nowthatwe&#039;vegotsometimeunderourbelt,we&#039;veobservedapatterninDataConsumerswhoareusingGnip.ManyDataConsumersalreadyhaveeventdetectioninplacewithpollinginfrastructurethey&#039;vebuilt.Theypollvariousendpointslookingforchange#comment-100</guid>
		<description>[...] to push their content to the GNIP network. From there, we as developers or consumers of that data, can access it and do some pretty clever things like create filters on it, or have it pushed to a script somewhere [...]</description>
		<content:encoded><![CDATA[<p>[...] to push their content to the GNIP network. From there, we as developers or consumers of that data, can access it and do some pretty clever things like create filters on it, or have it pushed to a script somewhere [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

