<?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>Twitual Blog &#187; Tech</title>
	<atom:link href="http://twitual.com/blog/posts/category/tech/feed/" rel="self" type="application/rss+xml" />
	<link>http://twitual.com/blog</link>
	<description>Explore your Twitter friends and followers.</description>
	<lastBuildDate>Fri, 13 Mar 2009 15:41:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1-alpha-15359</generator>
		<item>
		<title>Count limits lifted</title>
		<link>http://twitual.com/blog/posts/count-limits-lifted/</link>
		<comments>http://twitual.com/blog/posts/count-limits-lifted/#comments</comments>
		<pubDate>Fri, 13 Mar 2009 15:41:35 +0000</pubDate>
		<dc:creator>dougal</dc:creator>
				<category><![CDATA[Tech]]></category>

		<guid isPermaLink="false">http://twitual.com/blog/?p=22</guid>
		<description><![CDATA[We have removed the cap on the total number of friends and followers, so you can now try to analyze any Twitter user on Twitual. We will warn you, however, that with very large friend + follower counts, the process of fetching all of the information can be slow. To give you a general idea, [...]]]></description>
			<content:encoded><![CDATA[<p>We have removed the cap on the total number of friends and followers, so you can now try to analyze any Twitter user on <a href="http://twitual.com/">Twitual</a>. We will warn you, however, that with very large friend + follower counts, the process of fetching all of the information can be slow. To give you a general idea, some recent tests were taking about 3 minutes to analyze a user with 10,000 combined friends and followers. Obviously, this makes it pretty impractical to analyze highly networked users like <a title="Wil Wheaton" href="http://twitter.com/wilw">@wilw </a>or <a href="http://twitter.com/mashable">@mashable</a> (who each have over 200,000 followers).</p>
<p>The reason it takes so long is that the Twitter API only allows us to fetch 100 entries at a time. There are API calls to return all of the friend/follower IDs for a user at once, but they only return numeric IDs, not the screen name, which is far more useful for display. So we either need to find a way to fetch multiple batches of information in parallel, or we need to mirror the entire database of Twitter IDs and screen_names on our own server. Or maybe both. Even better would be a new API call to fetch all the screen names, but that&#8217;s not our call.</p>
<p>And, we realize that there is currently no feedback in the browser while Twitual is doing its thing. We&#8217;re going to be working on that, and hopefully when we&#8217;re done, we&#8217;ll have some spiffy whiz-bang progress bars to let you know what&#8217;s going on, and how close we are to being done with your request. Just don&#8217;t expect it to happen overnight &#8212; we&#8217;ll have to take our current, simple, no-nonsense code and transmogrify it into a bunch of complex, full-of-nonsense code. Those kinds of things take time!</p>
<p>In the meantime, we still think Twitual is a pretty nifty tool, and we hope you do, too. If you agree, keep spreading the word about us. Let us feel the love, we&#8217;re needy that way!</p>
]]></content:encoded>
			<wfw:commentRss>http://twitual.com/blog/posts/count-limits-lifted/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
