<?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>InfoForNYC.com &#187; Uncategorized</title>
	<atom:link href="http://www.infofornyc.com/blog/category/uncategorized/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.infofornyc.com/blog</link>
	<description>Blog for InfoForNYC.com, a superior site search for info on NYC / Manhattan</description>
	<lastBuildDate>Sat, 03 Apr 2010 17:33:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>New Site, New Info&#8230;over time</title>
		<link>http://www.infofornyc.com/blog/new-site-new-infoover-time/</link>
		<comments>http://www.infofornyc.com/blog/new-site-new-infoover-time/#comments</comments>
		<pubDate>Sat, 27 Dec 2008 21:57:04 +0000</pubDate>
		<dc:creator>infofornyc</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.infofornyc.com/blog/?p=23</guid>
		<description><![CDATA[Pardon for the prolonged absence here.  It&#8217;s been a busy year, but we are looking to revamp the entire site.  It seems that the topical search engines weren&#8217;t the best at providing the critical information that you required.
Therefore, instead of trying to tweak the searches, we are focusing on providing valuable content.  [...]]]></description>
			<content:encoded><![CDATA[<p>Pardon for the prolonged absence here.  It&#8217;s been a busy year, but we are looking to revamp the entire site.  It seems that the topical search engines weren&#8217;t the best at providing the critical information that you required.</p>
<p>Therefore, instead of trying to tweak the searches, we are focusing on providing <strong>valuable content</strong>.  Because we&#8217;re in this for quality, it will take a little while to get the information posted.  Please be patient with us as you will get high quality information over time.</p>
<p>As always, please contact us if you have any <a href="http://www.infofornyc.com/feedback/feedback.html">feedback or suggestions</a> or would like to intern with us!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.infofornyc.com/blog/new-site-new-infoover-time/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Updated Search Engine!</title>
		<link>http://www.infofornyc.com/blog/updated-search-engine/</link>
		<comments>http://www.infofornyc.com/blog/updated-search-engine/#comments</comments>
		<pubDate>Wed, 31 Jan 2007 15:14:55 +0000</pubDate>
		<dc:creator>infofornyc</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.infofornyc.com/blog/?p=22</guid>
		<description><![CDATA[The technology on the search engine has been upgraded.  We have a better way to help you find the NYC info you need.  Now you can explicitly vote on good and bad results to help your community members find relevant info and help bring spammers down.  Run some searches, cast your votes, [...]]]></description>
			<content:encoded><![CDATA[<p>The technology on the search engine has been upgraded.  We have a better way to help you find the NYC info you need.  Now you can explicitly vote on good and bad results to help your community members find relevant info and help bring spammers down.  Run some searches, cast your votes, and help keep us relevant.<!--288ea72aadb170460805e64260475f2d--><!--6e5ec6803a6c39c2073ee25dd9b834cf--><!--27541dddb2824e68f6fade34564f5018--><!--4596a8390157755a232b3e01559f5ad3--></p>
]]></content:encoded>
			<wfw:commentRss>http://www.infofornyc.com/blog/updated-search-engine/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
