Twitter – Page 5 – Stay N Alive

SocialToo is Proud to Launch With OneForty’s New App Store

Oneforty_logoIn an unprecedented move, Laura Fitton’s OneForty.com launched their own app store for Twitter today, enabling Twitter developers to finally have a platform to sell and promote their apps in a single location, to a large audience.  The company, with apps that you can purchase for Twitter, will become like iTunes or even Amazon, in enabling developers to sell, and Twitter app seekers to find and purchase, in a virtual Twitter marketplace.  My startup, SocialToo, is proud to be one of the companies launching with OneForty in this effort.

We know with the launch of the iTunes app store that bringing developers to a single location that others can search, find, and purchase apps, has proven to be a lucrative business for developers.  This launch will make Twitter itself a similar breeding ground for new entrepreneurial ideas and business opportunities that were previously not thought of.  The completion of an app store is the icing on the already baking Twitter ecosystem cake that should seal the deal for many entrepreneurs and developers in why they should write Twitter apps.

What can you purchase from SocialToo?

Until now you have already been able to purchase several features on the SocialToo website – those include the ability to unfollow everyone you’ve followed on Twitter at once, catching up those who followed you before joining SocialToo that you want to follow back, along with a powerful daily e-mail that includes stats as to who followed you and stopped following you the previous day on Twitter.  In fact, we just announced an affiliate program which enables anyone with a Twitter account to gain a cut of the revenues just by sharing with their friends on Twitter!

With today’s launch with OneForty, we are starting by allowing users to purchase our daily stats e-mail that sends you a digest of who followed you and who stopped following you the previous day on Twitter.  Because our current services are one-time for life, it gives us a unique opportunity to offer one-time purchases like this on 3rd party sites like OneForty.  The specific stats e-mail we’re offering on OneForty sells for just $20, and you get it for life.  In fact, because you’ve already given your e-mail address to OneForty, once you’ve purchased, you don’t even have to ever visit SocialToo.com (although we always appreciate the visit!) – you’ll start receiving stats e-mails the very next day.

I’m excited for this new development.  OneForty has already proven to be one of the best ways to find apps in the Twitter ecosystem.  It can only get better now as developers are able to now start monetizing their offerings through the directory.

So if you get a chance, go on over to OneForty and try out the SocialToo stats e-mail.  Be sure to leave us a review!  This is an incredible opportunity I’m proud to be a part of.

Nobody Has a Million Blog Subscribers

BlogSubscribers-main_FullA recent blog post by Anil Dash has everyone talking about what I thought was a long-assumed fact that just because someone is on the Twitter Suggested User List (or SUL) and has a million followers doesn’t necessarily mean they actually have all of those followers listening to them.  Dash, who recently had the opportunity to be on the Suggested User List himself, cited examples of various other Twitter accounts put on the list that saw absolutely no additional response after being added to the list.

I’d like to take this a bit further though and suggest something that, because of its open nature as compared to Twitter, just hasn’t been talked about much. That is the fact that, just like Twitter followers, a blog’s subscribers is also subject to this phenomena.  I’d like to suggest that despite that number in the upper-right-hand corner, it means absolutely nothing in the sense of how many people are actually reading that content.  It’s just a number.

Speaking From Experience

Let me start with this blog, since I vowed to be more transparent.  If you read the Feedburner number in the upper-right section of this blog it says I have over 7,500 subscribers.  Let’s start right off with the fact that 6,030 of those are because FriendFeed includes its subscription counts in with my Feedburner stats.  I have 6,030 subscribers on FriendFeed, and those are part of that 7,500 you see above.  If you subscribe to me on FriendFeed, that increases the number.  Still, that 6,030 still has potential of seeing my content.  It’s still just a number though.

Now, let’s assume those FriendFeed numbers don’t count.  That leaves about 1,500 subscribers  that assumedly subscribe to this blog through some sort of Feed Reader (Google Reader, Newsvine, etc).  I don’t believe that number at all.  I’d bet that at most, half of those actually read the articles I publish, as I usually average between 2 and 5 comments on each blog post I write.  As for traffic, any time I post I get around 200-500 additional visitors per post.  On a really good day that could be in the thousands.  The thing is that most of those come from Twitter, Facebook, and FriendFeed, as well as other blogs that provide commentary. Those numbers aren’t even reflected in my subscriber count!

The Big Guys

If that’s my experience, I can only imagine the accuracy of those with hundreds of thousands or even millions of subscribers.  I know their numbers can’t be accurate, not only based on my experience on this blog, but also after being linked numerous times by them.  I must admit that, directly, I usually average 100-300 visitors from the millions of subscribers on each of these blogs.  I’m very grateful for this traffic, and that they’re talking about me – the fact that they’re writing about me has much more impact and influence than just traffic (as I’ll show later).  However, the fact that only 100 out of over a million subscribers are clicking seems to imply a very similar truth to what Dash is implying with Twitter subscribers and what I’m seeing on my blog: while a few hundred thousand may be reading each and every article, the rest are simply casual bystanders skimming headlines if anything at all.

Let’s add to that how many of these blogs are on FriendFeed’s default list and other services, adding to their numbers there, along with how many are the default on the Kindle, or many RSS Readers out there.  Many users just get subscribed to these blogs by default.  Sure, some casually discover the blogs and start reading, but there is a strong possibility that many of those subscribed to these blogs never even read them, some perhaps not even aware that they’re subscribed!

Yet, Numbers Still Do Matter

As Dash implies with Twitter, the number still has an effect.  He mentioned the possibility of brand managers getting raises because their bosses see the number of new subscribers they were able to get for their brand.  From my own personal experience, I’ve seen this on both Twitter and my blog.  I can’t tell you the number of times I’ve been introduced as “influential” because I’m one of “the most followed Twitter users in Utah”, or “he has over 7,000 subscribers to his blog!”  Like it or not, many opportunities have opened up because of this.  All that and I don’t even have a million subscribers!

Let’s add to that the fact that I can sell it for money too.  On my blog I can sell ads for more because of this.  People are more likely to subscribe and tell their friends because beyond just content, they see that number as “influential”.  I’ve been introduced to many consulting opportunities because of this.  Of course I insist on proving myself beyond the numbers (I sincerely hope no one would hire me or anyone else based on numbers alone!), but numbers do matter!  For instance, if you have more subscribers than anyone else you get to say you are the top blog on the internet – that’s a powerful statement!  You bet it works.

Numbers also lead to better content.  As I consult for others I can’t tell you the number of people that want to pitch to blog X or blog Y because they have more subscribers than the others.  Having more people pitch to you means you get the scoop on more and better content, and you’re given more control.  The articles written may not bring much traffic, but the fact that “a big blog wrote about you” also means you can feature this in Press Releases, on your company blog, or more, giving the entrepreneur more attention from VCs, big businesses deals, and potential acquisitions down the road.  But if you’re looking for traffic some times it’s better to pitch to numerous smaller blogs than one or two big blogs.  If you want influence pitch to the bigger blogs.

Organic vs. Inorganic

There are many bloggers like Scoble, Chris Brogan, Louis Gray, and others that have built their audiences by working to build relationships with their readers, one-by-one.  Yet, others that have built their entire business model around blogging do it by creating business relationships, signing contracts, and then interacting with their readers as they have time.  I think both types of bloggers have similar trust with their readers.  Producing lots and lots of good content vs. building relationships with content are both good strategies, and both can produce similar results in how they affect those that read their content, as well as individual opportunities for the bloggers.

I think in the end it comes down to which is most rewarding.  I’m not going to say which one that is as that’s a matter of opinion – can a pure focus on numbers and subscriber counts vs. building relationships and organically building your audience be more or just as rewarding?  In the end we know one thing – that little number up there doesn’t mean what you think it says.

Or does it?

FriendFeed Turns on the Twitter Firehose (Again)

friendfeed-logo.jpgIt seems that some time today, the FriendFeed team has just re-enabled their live Twitter stream (using Twitter’s “Birddog” API) for real-time updates from Twitter.  I noticed the update when posting a cool bookmarklet by Kynetx, and re-tested it again – sure enough the update to Twitter hit FriendFeed almost immediately after I posted it to Twitter.  Looking over FriendFeed, I learned that Paul Buchheit, one of FriendFeed’s founders now working for Facebook, confirmed this earlier today.

Long before many were embracing Twitter’s real-time stream, FriendFeed was one of the first Real-time Twitter stream consumers to take advantage of the platform.  Shortly after the Facebook acquisition the FriendFeed team turned off the real-time updates, others speculating that it was the beginning of the end for FriendFeed.  FriendFeed’s Paul Buchheit assured users that the FriendFeed team was simply working out details with the Facebook lawyers to ensure the real-time stream met up with Facebook’s stringent legal policies.  Others remained skeptical.

Tonight it appears they’ve turned that live stream on for good, and boy is it fast!  FriendFeed continues to remain one of the most powerful Twitter clients and Social Management tools out there.  I think this continues to prove that FriendFeed will continue to improve even after the Facebook acquisition.

If you’re not yet, you can follow me on FriendFeed at http://friendfeed.com/jessestay.

Cinch Enables On-Site Recording of Audio for the Stream

CinchEarly this morning Rob Blackin posted a Cinch, debuting finally the ability to record audio straight from CinchCast.com’s own website.  Until today users could post photos and status updates on the micro-podcasting network, but its core service, audio, could not be recorded from the site itself.  Today they fixed that, enabling you to hit record, and save audio from any audio input on your computer.  I’m sure there will be many podcasters and audiophiles rejoicing.

BlogTalkRadio’s CinchCast.com, up until recently, has had an iPhone app to record audio, along with an API, and the ability to just call a number on your phone and record audio straight from any phone.  The service enables anyone, no matter where they are, to record audio even without an internet connection, and it gets added to their stream of Cinch updates on CinchCast.com.  Each stream has its own RSS feed which can be fed into your favorite reader or feed aggregator as well. (I feed mine into FriendFeed)

This move should enable podcasters and those that want to use more professional audio equipment to also post high quality audio shares to the site.  For instance, let’s say you’re a musician and you want to share a quick, live, bootleg preview of a song you just released.  This enables such capability straight from the desktop and any sound equipment you have.  Or perhaps you’re just sitting at work at your computer and just want to record some thoughts.

Screen shot 2009-12-22 at 10.44.27 AM

It will be interesting to see what new types of Cinches get produced from this.  Currently, the company is already broadcasting short audio snippets from Bill Cosby, and tech bloggers Robert Scoble and Louis Gray, along with many others are using it to post short interview clips from the conferences they attend and companies they visit.  I’m using it as a daily personal journal as well.

Cinch’s focus on audio brings some interesting use-cases for a social media stream that text and video simply just don’t satisfy.  I can’t wait to see what comes next for the company.  You can follow me on Cinch at http://cinchcast.com/jessestay.

Disclosure: Cinch and BlogTalkRadio are clients of Stay N’ Alive Productions, LLC, my consulting company

http://www.cinchcast.com/cinchplayerext.swf?file=http://www.cinchcast.com%2f/CinchPlaylist.aspx%3FRecordingID%3D14762&playermode=full&autostart=false&bufferlength=5&volume=80&callback=http://www.cinchcast.com/FlashPlayerCallback.aspx&width=300&height=200&volume=80&corner=rounded

Developers, It’s Time to Open Up Twitter’s API

TwitterIf you’ve read my previous post on this, you’ll notice how I re-worded the title of this article.  That’s because I’m delusional to think Twitter is going to open source their API any time soon – I’ve been requesting this for over a year now.  I think I’ve come to a new understanding that if we’re to see an open standard built around Twitter’s API, it’s going to be we, the developers, who implement this.

It won’t be Twitter.

I mentioned earlier that developers are starting to catch onto this idea.  It all started almost 2 years ago when Laconi.ca introduced their own Twitter-compatible API into their platform allowing any client library based on the Twitter platform to very simply add Laconi.ca instances to their preferred Twitter client.  Unfortunately it took 2 years for that idea to catch on.  Finally, we’re seeing some big players in this, and my predictions are coming true.  Automattic just released their own Twitter-like API into WordPress.com.  Tumblr just released their own Twitter-like API.  The problem here is that all these developers are re-inventing the wheel every time they re-produce Twitter’s API, and any time Twitter releases a new feature they are stuck re-configuring and re-coding their server code to stay up with Twitter’s new API features.  That’s fine though – this is all a step in the right direction.

The Vision

Imagine now if there were a standard that, at first duplicated what Twitter was producing on their end, but other developers could code off of.  Open Source software could be built around this standard, and now any provider would be able to easily install code that integrated well with their own environments very easily.  We’d see many more providers than just WordPress and Tumblr and Laconi.ca instances like TodaysMama Connect (of which I am an advisor) integrate this.  We’d see big brands and big companies start to implement this.

Soon Twitter will be in the minority amongst services these “Twitter clients” (like TweetDeck, Tweetie, or Seesmic) support.  The Twitter clients will no longer feel obligated to cater to just Twitter, and new layers, such as real time and meta APIs could be added to this API standard in a way that benefits the community, not a single company.  Twitter would no longer have a choke-hold on this and we would have a new, distributed architecture that any developer can implement.

The Proposal

What I’m proposing is that we work together to build an open source set of libraries and services, perhaps a gateway of some sort, all built on a standard that we set (it will most likely copy Twitter’s API at the start).  I’ve built a Google Group, called “OpenTwitter” for now, with the purpose of opening up Twitter’s APIs.  The group will have a primary focus of determining how we want to build this software, establishing documentation for such software, and attaching a completely open standard on top of all that we can modify as it makes sense.  The goal here is that the public will now control how this data gets distributed, not a single company.

But What About RSS?

The question always comes up, why not just push these clients to support RSS and rssCloud or Pubsub Hubbub?  The answer is that we’ve been trying this for too long.  It may still happen, but it’s going to take Twitter clients a lot longer to modify their code to support RSS than an open Twitter-compatible standard.  Ideally, a Twitter client, which there are many, ought to be able to quickly and easily just change the base domain of where calls are sent, and everything with the providing service should “just work”.  RSS complicates this too much.  The fact is that Twitter has taken over and we need to accept that as a fact and work with it.

The Invitation

If you can, I’d like to invite you to join our “OpenTwitter” list on Google.  Let’s get some conversations going, and get this thing off the ground.  My hope is that we can get people like Dave Winer, Matt Mullenweg, Chris Messina, David Recordon, Joseph Smarr, DeWitt Clinton, and Mike Taylor all joining this effort.  My goal is that we can even get Twitter involved in this effort – this isn’t meant to snub Twitter by all means.  The entire goal here is to build a much more open, distributed web in as simple a manner as possible.

You can join the “OpenTwitter” list here.  I’ll be posting a kickoff message there very soon.

Twitter, It’s Time to Open Source Your API

twitter.pngWith the recent launch of a “Twitter API” by both Automattic (WordPress.com) and Tumblr, it is evident that developers have a need to implement similar APIs, on similar platforms, reducing the effort to retrieve data from multiple platforms in a single client.  With Tweetie, for instance, you can simply change a single URL to “WordPress.com” or “Tumblr.com” or “Identi.ca” and immediately be receiving updates from your friends on those services, and even post back to those services.  I argue this approach is very closed though, as for each and every implementation of a “Twitter API” (which ironically has nothing to do with Twitter), the developers need to completely re-invent the wheel and copy what Twitter has done based on documentation of Twitter’s own API to access its data.  Readwriteweb even went to the extent of calling this approach “open”.  There’s nothing open about it.  Each developer implementing their own “Twitter API” (and especially calling it such) is blatantly ripping off Twitter’s API to do so under no license whatsoever and Twitter’s just standing back and watching.  I think it’s time Twitter releases their API under an Open Source license to relieve this mess and protect their IP.

Open Sourcing APIs is nothing new.  Of course, Google, with OpenSocial, did it and even standardized their own API for “containers” to easily implement the same API across multiple sites.  All the code was provided for developers to do this and we quickly saw sites such as MySpace, Hi5, Orkut, and others all implement the same standard, reducing the code needed to port an app from platform to platform.

Facebook did the same with their platform.  A little known fact is that any developer can go to http://developers.facebook.com/opensource.php and download the Facebook Open Platform, along with many other very useful open source tools.  Immediately they have access to enable FBML, FBJS, and other aspects of the Facebook API to developers on their own sites, standardizing the Facebook platform amongst sites that implement it.  Bebo was one of those who took up Facebook on this offer.  Others can too.

What we need now is a standardized platform for sharing micro-content.  Some have proposed RSS do this, which is fine with me, but since developers already have apps built on Twitter which this would go with it makes sense to also enable a standardized platform for developers to code on for these types of apps.  Such an open-sourced code-base would enable developers to not have to change their code to enable access to similar sites beyond just Twitter.  Twitter right now is a closed platform, plain and simple.  With the exception of OAuth, they are based on a proprietary API, do not support open content protocols, and even their real-time stream is proprietary.

A good step for Twitter would be to open source this API.  Enable sites such as WordPress, Tumblr, Status.net, and others to easily integrate it into their own platformse without the need to re-invent the wheel.  Put it under an open license, and then your IP remains protected.  Until that point  developers are going to continue ripping off Twitter’s API, and Twitter’s IP slowly starts to go down the drain.  I’d love to see Twitter take a lead in this process – it took Facebook just about 6 months to open source their API.  Why haven’t we seen this yet from Twitter?

Or are they the next Compuserve?

Twitter – TIMTOWTDI

IMG_1366I love Twitter for its variety.  In many ways it’s a lot like my favorite programming language Perl, whose mantra is “There is more than one way to do it.”  Some people choose the messy, spaghetti code way, while others choose nicely formatted, object-oriented way, even taking it to the extent of protecting it further with libraries like Moose.  On the web I can do basic, old-style CGI, or take it as far as a full MVC structured framework using Catalyst (if you don’t know anything about what these are that’s okay – just know that they’re good, and well structured).  Perl has both a good and bad reputation because of this, and I like it that way.  I like it the same way I like Twitter – there’s more than one way to do it.

That’s why I get so bugged when I see so many people trying to tell me how to write my Twitter stream.  Some say I have to have multiple accounts to organize the data.  Others say I can’t run ads and my content can’t be promotional in any way.  Funny thing is most of those people are promoting something of their own, whether they admit it or not. Personally that doesn’t matter to me.

What matters to me is that I can use Twitter the way I want to.  I can write everything in one stream if I want to, or I can run ads if I want to (which actually, I just signed up for ad.ly yesterday to see what it was all about – no one has purchased anything yet though so no worries there, if there ever were any in the first place).  I can be profane if I like (but generally I prefer not to, just like real life).  I can even retweet the way I like to.  The cool thing about Social Media is we all have our own purposes and our own ways of doing things and when we do such we use the best tools for the job.  The great thing about Twitter is that it allows us to do such.  I use Twitter the way I use Perl, however I want to and what works for me – and I get criticized in the same manner.  There will always be a critic of the way you use Social Media, just like there is always a critic of how I write Perl.

And I’m okay with that.

The fact of the matter is I’m interesting because I’m ME.  Hopefully you follow me because of that.  If I advertise it’s going to because that’s something I think will help pay for me to be me, and it will always be some sort of reflection of myself.  If I don’t advertise it’s because I don’t think that’s necessary.  If I separate my content into multiple accounts it’s because I want you to find out different bits of information about me in different ways.  If I keep it all in one stream that’s because I think that’s the best way of learning who I am.  If I retweet it’s for my own reasons, not anyone else’s.

I think we get way too caught up in what we think is the best way that works for us, and thinking others should do the same.  What works for me will not always work for you or the next guy.  What works for Chris Pirillo or what works for Chris Brogan will not always work for Robert Scoble or Leo Laporte or someone else.  We are all unique, and that’s what makes Social Media a beautiful thing.  Social Media is all about how you receive, not about how other people give.  Receive well, and you will give much.  Social Media is all about ME. And you. And him. And her. It’s about connecting Individuals, which individuals are not the same.

And if you don’t like that concept, I’m okay if you unfollow me.  After all, there’s always more than one way to do it.

This is What an RSS Reader is For

RSSYesterday Robert Scoble wrote a critical post claiming Chris Brogan was using Twitter wrong, stating Chris isn’t separating his content on Twitter well enough.  As one who had to create multiple Twitter accounts to separate out my activity, I am one of the first to support this method.  As it stands though, even I will be first to admit this is a hack.  The only reason I’m creating multiple Twitter accounts is because Twitter, by nature, makes it very difficult to separate out activity like this.  What Scoble wants is a way for him to better read people’s feeds on Twitter, and separate out your blog post from the rest of the content on Twitter.  The problem is, despite what everyone says, I think Scoble is realizing the weakness of Twitter which is that it isn’t really an RSS Reader.

Scoble wants a way to take all the Tweets, by list of those he follows, and read their blog posts, just like he would in an RSS Reader.  My guess is that this is so he doesn’t have to leave Twitter to find new blog posts, a legitimate excuse.  However, Twitter just wasn’t built that way.  As one of the most vocal critics of Google Reader, I think what Scoble and others with this problem need is just what they’re criticizing – an actual RSS Reader built around reading blog posts.

I’ve always been a proponent of the mantra that Social Media is not how you give – it’s how you receive.  If you have a problem with the way others are Tweeting or blogging or posting on Facebook, then find a better way of receiving that data, unfollow, or do something so that you’re only getting the data you want to receive.  There are so many tools out there – FriendFeed (FriendFeed is so much more than just community – it’s an incredible tool!), Google Reader, TweetDeck, Seesmic Desktop, Brizzly, Twitter’s own interface, Facebook’s own interface, and many, many more, that surely there has to be something that enables this.

If not, bloggers need to be petitioning developers, not individual users of these services, to change their ways.  For instance, why can’t I separate out the Tweets with links in them from the rest of the Tweets on Seesmic Desktop?  Or why can’t I specify what my blog is on Twitter and have Twitter distinguish that as meta data for other developers to separate from the rest of the stream?  Why can’t I preview the links before clicking on them?

If you’re not getting what you want from Social Media, this is the fault of the innovators, not the users.  In the case of RSS, if it ain’t broke, don’t fix it – this is why I never left Google Reader or FriendFeed in the first place, and don’t anticipate doing so any time soon.  They solve the problem Robert Scoble is speaking of for me.

That said, to be considerate of those on Twitter I may still start an additional account that imports just my blog posts, but why? So just one or two individuals can read it? At what point am I separating my Twitter stream so much that you can’t find everything you want to find out about me?  IMO the mantra still exists that you should always be using the best tool for the job, and for reading blogs, Twitter just doesn’t cut it.

Does Twitter Have An Internal iPhone App?

TwitterA while back I was surfing the Twitter developers wiki and noticed 2 interesting images uploaded by Ryan Sarver, Twitter’s Platform Project Manager.  One of the images looks like a very rough status message entry screen, with a toggle button for Twitter’s new geolocation feature.  This same feature just launched in read-only mode on Seesmic’s new desktop app yesterday.  The second image is what looks like a screenshot of an iPhone screen prompting the user to enable Geolocation, taking the user to their Geolocation settings to enable it on a user’s account.

Then, today, Robert Scoble pointed out that you could see the new Geolocation feature launched in Seesmic Desktop in action by viewing Ryan Sarver’s tweets in the Twitter client.  This makes me wonder how Ryan is broadcasting his location.  Does Twitter have an internal iPhone app they are using, or are these just proof of concept images for other developers to use in their own apps?

Twitter has long been criticized for the lack of a good native mobile client.  They have also admitted in the past that a new version of at least the mobile web client is in the roadmap.  Could they be taking this a step further and building an entire iPhone app out of it?

Based on current facts the natural assumption would be that this is just an internal app they are using to test out mobile features like geo-location.  The roughness of the screenshots and focus on just geolocation that we know of thus far lends to that conclusion.  However, it’s important for all developers to be prepared, and be aware that in any market sustained by just Twitter your greatest competitor could just be your supplier of information (a concept I learned in business school), Twitter itself.  If you’re developing an iPhone or mobile app for Twitter this is indeed something you should always be prepared for.

Here are the screenshots – you tell me. Is Twitter building an internal iPhone app?

Geotagging Toggle UXPopup+Disclosure

Twitter Hires Another Facebook Veteran

Brian SutoriusAccording to Twitter’s Team list, Brian Sutorius, who, according to his Facebook profile, was previously on Facebook’s Platform Policy team, is now Twitter’s newest API Support team member.  After the loss of Alex Payne moving to more operational roles, and Chad Etzel, who was on a contract basis with the team, Sutorius joins the likes of Ryan Sarver and Doug Williams in the Support role.  Twitter’s API Support team are in charge of managing the Twitter development mailing list and ensuring the Twitter API is managed properly.

Sutorius worked since July of 2007 on Facebook’s Platform Policy team, the team at Facebook in charge of enforcing policy infringements on Facebook’s developer platform.  The team ensures applications are following policy, not storing information more than 24 hours, aren’t serving deceptive ads, etc.  Now it would appear he could be doing similar things on a team working to shore up its own platform policy agreement.  Brian was there when Facebook grew through their own policy changes – Facebook Platform was launched around May of 2007.

It’s exciting to see Twitter bringing more veteran talent into their team.  With the previous hire of Josh Elman, Facebook’s former Platform Manager, and now Brian Sutorius, Twitter is solidifying its effort to innovate and bring Twitter closer to Facebook as a competitor.  As I said earlier, it’s these types of hires that are making me more excited about Twitter.  We’ll see if they live up to the people they’re hiring and keep things moving forward.