<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Latest Comments for indiekid</title><link xmlns="http://www.w3.org/2005/Atom" rel="http://api.friendfeed.com/2008/03#sup" href="http://disqus.com/sup/all.sup#usercomments-45597f9e" type="application/json"/><link>http://disqus.com/people/indiekid/</link><description></description><language>en</language><lastBuildDate>Mon, 23 Nov 2009 12:40:53 -0000</lastBuildDate><item><title>Re: The GeoAPI vs SimpleGeo: Is Real-Time The Final Word</title><link>http://click2map.hyveup.tv/2009/11/geoapi-vs-simplegeo-is-real-time-final.html#comment-23887051</link><description>This is Matt from SimpleGeo (CEO). Thanks for the writeup! We're really stoked to see all the different kinds of apps looking to leverage our platform.&lt;br&gt;&lt;br&gt;You're absolutely right when it comes to our strengths. Real-time is a huge target for us, mainly because that's the way that the web is going, and in turn, mobile apps need to follow suit. Imagine all of the checkin data that apps represent, people moving throughout the world at a rapid pace. There needs to be an infrastructure that can handle that. I'd like to think that's us.&lt;br&gt;&lt;br&gt;Beyond that, scalability with this data is also of utmost importance. The problem with most solutions today is that they're based on traditional relational databases. Whereas this has worked in the past, the move to real-time, and thus, the insane amount of data being pushed around causes need for an alternative. We've built our on solution based on Google's BigTable and Amazon's Dynamo so that it's multi-mastered, and thus, lacks the "single point of failure" issue. The other key differentiator between our tech and say, PostGIS is that we don't have to partition our data the way they do. Partitioned geo-data is a nightmare.&lt;br&gt;&lt;br&gt;Again, thanks for the mention and we can't wait to get this open to the public!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">indiekid</dc:creator><pubDate>Mon, 23 Nov 2009 12:40:53 -0000</pubDate></item><item><title>Re: AOL&amp;#8217;s Socialthing for Websites Ties It All Together</title><link>http://mashable.com/2009/04/28/socialthing-for-websites/#comment-8773966</link><description>Stan, great writeup.&lt;br&gt;&lt;br&gt;This is Matt, one of the Founders of (the original) Socialthing.  One thing to note is that while we currently only support installation via the "bar", that will be changing.  Our plan is to be able to peel away any feature into its own distinct widget.  Hope that helps!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">indiekid</dc:creator><pubDate>Tue, 28 Apr 2009 09:42:08 -0000</pubDate></item><item><title>Re: http://blog.louisgray.com/2009/03/apple-iphoto-to-integrate-facebook.html</title><link>http://blog.louisgray.com/2009/03/apple-iphoto-to-integrate-facebook.html#comment-7222209</link><description>Louis, they're actually already using Facebook Connect in iPhoto (just not in the typical "Connect" button experience).&lt;br&gt;&lt;br&gt;When you click on the "F" in the toolbar to upload a picture to Facebook, it's using the Facebook Connect product to actually make the authentication happen between iPhoto and Facebook.&lt;br&gt;&lt;br&gt;Just wanted to clarify...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">indiekid</dc:creator><pubDate>Sat, 14 Mar 2009 15:46:14 -0000</pubDate></item><item><title>Re: Who Be You Be?</title><link>http://learntoduck.com/twitter/who-be-you-be#comment-6875492</link><description>So I totally get where you're coming from, Micah, but truthfully, my changing from @indiekid to @mattgalligan was because I wanted to get away from the nickname.  Everyone in real life calls me Matt.  That's my name.  And as a result, I wanted people to call me "Matt" online too.  Simple as that.&lt;br&gt;&lt;br&gt;The "real name" as your identity thing really works well on Facebook, and I think that the more people are using services like that, the more the same principles will start to leak into other places.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">indiekid</dc:creator><pubDate>Wed, 04 Mar 2009 13:01:09 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-932465</link><description>So I'd just like to chime in as an API user.  While Socialthing! uses the authenticated API and we're not at all affected by this, we have similar restrictions at other sites.  Up until now, Twitter had really been an anomaly when it comes to how their API is served up (in both authenticated and unauthenticated calls.  First off, almost every single other site out there with a popular API has rate limiting on the IP level.  Yeah, it sucks, but there's really not many other ways of doing it until push comes to pass.  &lt;a href="http://gnipcentral.com" target="_blank" rel="nofollow"&gt;Gnip&lt;/a&gt; is a solution for sure, but those same API providers need to plug into Gnip for it to happen.&lt;br&gt;&lt;br&gt;Twitter is just coming to a point where they're realizing that they can't easily sustain their previous models.  Anyone that is currently using unauthenticated calls will soon be able to pull from Gnip to be able to optimize their calls (and likely, be more accurate than they were before).&lt;br&gt;&lt;br&gt;APIs are a tough game...both on the consumer and the producer level.  Twitter understands that their developers are their lifeblood, that's why they're working hard to improve the service for all.  I think it's safe to say that the reason they're bumping up the auth'ed calls, and down the unauth'ed calls is because more people actually interact with services that are authenticated.  Think Twhirl, Twitterrific, Socialthing!, etc.  Now, the non-authenticated services are probably pulling far more data at a much larger detriment to Twitter, but most of the activity isn't going on with those places.  This move is a very positive thing for the API as a whole, and you can rest assured that they will likely have other solutions for folks that simply can't auth the API going forward.&lt;br&gt;&lt;br&gt;Great post, Louis</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">indiekid</dc:creator><pubDate>Fri, 18 Jul 2008 10:37:03 -0000</pubDate></item><item><title>Re: Hahlo or Twitterific To Follow Summize Acquisition</title><link>http://gosdot.com/unity/2008/07/16/hahlo-or-twitterific-to-follow-summize-acquisition/#comment-920953</link><description>I'm not totally certain that this would be a smart move for them.  Search made complete sense, but bringing a client in house doesn't to me.  This is because they thrive on their developer program.  If all of the sudden, there's an app that's in-house, it will get downloaded WAY more often than anything else, and effectively kill the other solutions.  You see this all the time when Mac OS X builds a feature that had been a program for years.&lt;br&gt;&lt;br&gt;Summize made total sense because they were already picking up a lot of slack and had made by far the best search program based off of the Twitter platform.  Of course this will kill tweetscan and the like, but that's nothing like killing desktop or mobile apps for sure.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">indiekid</dc:creator><pubDate>Thu, 17 Jul 2008 10:34:54 -0000</pubDate></item><item><title>Re: Swurl and Second Brain: Feeding your past into the present</title><link>http://www.cloudnotes.net/2008/07/swurl-and-second-brain-feeding-your.html#comment-880204</link><description>Basically for now you can just scroll down.  Maybe in the future we can implement something where we provide a list of dates that you can pop back to...that might be cool...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">indiekid</dc:creator><pubDate>Sun, 13 Jul 2008 12:53:38 -0000</pubDate></item><item><title>Re: Swurl and Second Brain: Feeding your past into the present</title><link>http://www.cloudnotes.net/2008/07/swurl-and-second-brain-feeding-your.html#comment-880138</link><description>Just to clarify, Socialthing! does go historical with profiles.&lt;br&gt;&lt;br&gt;&lt;a href="http://indiekid.socialthing.com" target="_blank" rel="nofollow"&gt;My profile&lt;/a&gt; goes all the way back to May 2005 with my very first comment on Digg.&lt;br&gt;&lt;br&gt;Thanks for the mention, though!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">indiekid</dc:creator><pubDate>Sun, 13 Jul 2008 12:39:51 -0000</pubDate></item><item><title>Re: Google Just Bought Jaiku</title><link>http://gosdot.com/unity/2008/06/16/google-just-bought-jaiku/#comment-684385</link><description>Don't know if you knew this happened last year...&lt;br&gt;&lt;br&gt;&lt;a href="http://www.techcrunch.com/2007/10/09/google-buys-social-mobile-startup-jaiku/" rel="nofollow"&gt;http://www.techcrunch.com/2007/10/09/google-buy...&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">indiekid</dc:creator><pubDate>Mon, 16 Jun 2008 12:37:30 -0000</pubDate></item><item><title>Re: louisgray.com: Dealing With Capacity Overload and "Laying Off" Features</title><link>http://blog.louisgray.com/2008/05/dealing-with-capacity-overload-and.html#comment-674636</link><description>Andy, thanks for the comment for sure!&lt;br&gt;&lt;br&gt;Louis, just thought I'd let you know that 2.0 is up and running, so why don't you come on back and check it out...much more stable, put some old services back in and tossed a few new features in there while we were at it.  Check out the blog post describing everything here:&lt;br&gt;&lt;br&gt;&lt;a href="http://blog.socialthing.com/2008/06/12/whats-new-in-20/" rel="nofollow"&gt;http://blog.socialthing.com/2008/06/12/whats-ne...&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">indiekid</dc:creator><pubDate>Fri, 13 Jun 2008 23:04:30 -0000</pubDate></item><item><title>Re: SocialThing upgrades to 2.0 ads Digg and YouTube support</title><link>http://www.techau.tv/blog/?p=490#comment-649233</link><description>The key about the update notification is that they're new updates that you haven't seen yet.  By clicking on "See them" we return you to the Home tab and load in the new updates...&lt;br&gt;&lt;br&gt;That help?  Hope you're enjoying 2.0!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">indiekid</dc:creator><pubDate>Thu, 12 Jun 2008 17:43:26 -0000</pubDate></item><item><title>Re: Lis311 - Tumblr Tags, Anyone?</title><link>http://lis.tumblr.com/post/38146951#comment-646960</link><description>You should try out &lt;a href="http://lijit.com" rel="nofollow"&gt;http://lijit.com&lt;/a&gt; - they add on search for you!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">indiekid</dc:creator><pubDate>Thu, 12 Jun 2008 13:45:28 -0000</pubDate></item><item><title>Re: And Now . . . The Backlash</title><link>http://howtosplitanatom.com/columnists/and-now-the-backlash/#comment-578970</link><description>Greg, terribly sorry it's taken us so long to comment on this.  I'm one of the founders of Socialthing! and I just want to let you know we're far from dead and gone.  We've got a good loyal userbase, but most importantly, for the past two months we've been hard at work on our massively revamped version 2.0.  It's now almost done, and it will really change the way people think about our service.  I hope once it's out, you get a chance to check it out and let us know what you think...we'd really love to hear what you think!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">indiekid</dc:creator><pubDate>Tue, 03 Jun 2008 10:08:54 -0000</pubDate></item><item><title>Re: louisgray.com: Dealing With Capacity Overload and "Laying Off" Features</title><link>http://blog.louisgray.com/2008/05/dealing-with-capacity-overload-and.html#comment-567292</link><description>Hey J. Phil and Louis...we had to disable them simply because of the sheer number of calls we were sending them.&lt;br&gt;&lt;br&gt;We call the services in a very different way than FriendFeed and others, mainly because our goal isn't just to aggregate you and your profiles, but rather, aggregate your friends on that service.  The end result is a single dashboard with all of your friends' activity elsewhere.&lt;br&gt;&lt;br&gt;What this does, is cause a whole lot of extra calls that we have to make to the services.  Some of the APIs that we call are prepared for this, and deliver most all of that information in a single, or maybe two calls.  However, in the case of del.icio.us, Digg, Last.fm and YouTube, the process was like this:&lt;br&gt;&lt;br&gt;1 call for your activities&lt;br&gt;1 call for your friends list&lt;br&gt;x calls for x friends&lt;br&gt;&lt;br&gt;In a very short period of time, we might call a service like Digg 102 times in 1 second (let's say, if you had 100 friends).&lt;br&gt;&lt;br&gt;To remedy this, we've worked with the services to find alternative ways of calling them, as well as have completely re-written our architecture and ways that we call the services from our end.  When we launch 2.0, it will reflect this, and all of those services will be added back in immediately.  The new infrastructure also allows for us to call RSS based sites and services, as well as opens us up to many other services.  We're expecting to launch the 2.0 features very soon (I can't give a specific date, but I can say that we're almost done testing, and pretty much just awaiting deployment now)&lt;br&gt;&lt;br&gt;I hope that could answer a few of your questions.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">indiekid</dc:creator><pubDate>Sun, 01 Jun 2008 11:22:45 -0000</pubDate></item></channel></rss>