<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Visible Workings (redux)</title>
	<atom:link href="http://blog.jonudell.net/2008/12/30/visible-workings-redux/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jonudell.net/2008/12/30/visible-workings-redux/</link>
	<description>Strategies for Internet citizens</description>
	<lastBuildDate>Wed, 17 Mar 2010 18:06:41 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jon Udell</title>
		<link>http://blog.jonudell.net/2008/12/30/visible-workings-redux/#comment-126274</link>
		<dc:creator>Jon Udell</dc:creator>
		<pubDate>Wed, 31 Dec 2008 14:34:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/?p=889#comment-126274</guid>
		<description>&quot;do you rely on google alerts or do you do periodic searchs on known services like eventful and such?&quot;

The latter. Every scan of Eventful produces a list of events within a radius around a target location. Every event has an owner. If an owner hasn&#039;t been seen before, that Eventful account goes into the &quot;new contributor&quot; bucket. Monitoring the feed of eventful+new+contributor produces an alert. The feed item&#039;s link points to the events created by that new contributor, so an admin can easily click through, evaluate, and make a decision.</description>
		<content:encoded><![CDATA[<p>&#8220;do you rely on google alerts or do you do periodic searchs on known services like eventful and such?&#8221;</p>
<p>The latter. Every scan of Eventful produces a list of events within a radius around a target location. Every event has an owner. If an owner hasn&#8217;t been seen before, that Eventful account goes into the &#8220;new contributor&#8221; bucket. Monitoring the feed of eventful+new+contributor produces an alert. The feed item&#8217;s link points to the events created by that new contributor, so an admin can easily click through, evaluate, and make a decision.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vitor Silva</title>
		<link>http://blog.jonudell.net/2008/12/30/visible-workings-redux/#comment-126272</link>
		<dc:creator>Vitor Silva</dc:creator>
		<pubDate>Wed, 31 Dec 2008 10:28:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/?p=889#comment-126272</guid>
		<description>&gt;&gt;I plan to delete that contributor and wait to see if he or she shows up again with actual event contributions. 

i imagine that you may have already described the process by which other potential contributors may &quot;show up&quot; but i can&#039;t seem to find it.
could you elaborate a bit on how that process of discovering potential contributors happens? do you rely on google alerts or do you do periodic searchs on known services like eventfull and such?</description>
		<content:encoded><![CDATA[<p>&gt;&gt;I plan to delete that contributor and wait to see if he or she shows up again with actual event contributions. </p>
<p>i imagine that you may have already described the process by which other potential contributors may &#8220;show up&#8221; but i can&#8217;t seem to find it.<br />
could you elaborate a bit on how that process of discovering potential contributors happens? do you rely on google alerts or do you do periodic searchs on known services like eventfull and such?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
