ManageFlitter Blog

 

50 thousand users & 10 million unfollows

Just a quick update to let you know that we've passed some pretty big milestones on ManageFlitter. We've now made over 10 million unfollows for the 50 thousand accounts who have used our service! Almost every day we have more new users than the day before.

Thank you to everyone who continues to use ManageFlitter.

We want to keep making our service better for you. Please let us know what features you'd most like to see added in the comments below!

Posted by ManageFlitter 

Comments [5]

Welcome to the new way to manage Twitter with, er, ManageFlitter!

Well, our last blog post caused a bit of a stir. Thank you to the nearly 2000 people who tweeted and commented about it! Even TechCrunch offered their support.

After chatting with Twitter, it became clear that their main problem with our existing service was that users were not being individually selected to be unfollowing. We've removed the "Select All" button and the default selection on accounts when a page is loaded. Instead we've come up with a bit of an interface compromise which Twitter has tentatively approved. Each page now has an expandable overview where you can now drag your mouse across the avatars of accounts to select them for unfollowing. We've included a screenshot below.

In addition to this interface change, we have also changed the name of our application to ManageFlitter to avoid using Twitter's trademark in our name. Why Flitter? Well flitter means "to flutter" which birds do, particularly when you get a lot of them! Also it's, uh, only two letters from "Twitter" :)


We hope these changes will allow us to continue opperating within Twitter's guidelines indefinitely.

Happy unfollowing!

Posted by ManageFlitter 

Comments [13]

Save ManageTwitter!

If you are a user of ManageTwitter.com and you would like ManageTwitter.com's service to continue, please retweet this tweet, use the tag #savemanagetwitter or leave a comment below. Twitter want us to remove the heart of our application - we need your support!

Here at Melon Media, we love Twitter. I mean REALLY love Twitter. We developed ManageTwitter.com in our "10% project time". Our other twitter products include AdAdmire - a monetisation platform with a twist for third party Twitter applications & @_spell - a spelling tool for tweets.

Managetwitter.com was developed in the spirit of strengthening the Twitter ecosystem. We believe the more relevant your Twitter stream is to the user, the more the user will engage with Twitter and thereby more value the user will add to the Twitter ecosystem. We've unfollowed nearly 6 million people for the over 35000 users who have used ManageTwitter. We receive constant thanks and compliments from users about the system and how the application assisted in raising the quality of their tweet stream. Here is a graph of the activity on ManageTwitter per day (the initial spike coming from a TechCrunch article). People love our service, they keep coming back, using it again and again.

It surprised me therefore when we received an email this morning from Twitter:

"We're writing to let you know that your application, ManageTwitter, breaks our Automation Rules and Best Practices (http://help.twitter.com/entries/76915). Specifically, it facilitates bulk automated user unfollowing, which is not allowed. It's best for both our
users and your users if your application follows the rules, so please make the necessary changes, such as removing the "Select All" option (and requiring users to decide on each user individually) to bring your application into compliance. "

Yes our application does facilitate bulk unfollowing BUT ManageTwitter does not facilitate any *automated* bulk unfollowing, the user has to filter based on criteria. The user is still required to do significant processing to unfollow groups of people. Furthermore the system only allows unfollowing of up to only 100 at a time.

I do understand the spirit of Twitter's "Automation Rules and Best Practises" - unfiltered, unregulated automatic following and following is not what Twitter is about - we get that and support that.

But surely a service such as ManageTwitter.com that ENHANCES the Twitter user experience is adding value to the Twitter ecosystem? Over time a Twitter account can get "bloated" - accounts that you follow can become inactive, accounts that you thought would be interesting become stale, accounts that you followed can overtweet cluttering your stream and so on. Managing your followers and people that you follow can easily become a chore. We developed Managetwitter.com to assist users prune and clean their twitter account with the aim that the user will engage MORE with their own Twitter account.

We would like Twitter to reconsider their request to us to change the way our service works.

If you are a user of ManageTwitter.com and you would like ManageTwitter.com's service to continue, please retweet this tweet, use the tag #savemanagetwitter or leave a comment below.

Twitter want us to remove the heart of our application - we need your support!

Thanks.

Kevin Garber (@ke_ga) , James Peter (@zemaj) and the team.

 

Update Tuesday 27 April 2010: We are currently in discussions with Twitter and hope to report back on a positive way forward.  Thank you for all of your support.  

Update Tuesday 3 May 2010: As per request from Twitter we will be changing the name of our service  - to ManageFlitter.com and we will also make the system changes that they have requested.  Hopefully the service will still remain of strong value to Twitter users.  Twitter have been professional and reasonable in their communications with us and we look forward to a good working relationship with them

Filed under  //   api   follow   managetwitter   tweets   twitter   unfollow  
Posted by keving 

Comments [218]

10 Most Unfollowed Accounts

managetwitter.com has been live for about 1 month.

In that time managetwitter.com has assisted over 30 000 Twitter users unfollow over 5.5 million people that they are following.

30 000 users and 5.5 million unfollows is a decent size dataset - we thought that it would be interesting to see which Twitter accounts were the
most unfollowed via managetwitter.com.

So hear you have it *drum roll* - the 10 most unfollowed Twitter accounts via managetwitter.com over the list month.

10. UberTwiter
9. MrTweet
8. BillGates
7. twibbon
6. mashable
5. BarackObama
4. twitter
3. google
2. tinychat
Most unfollowed Twitter account: 1. wefollow

The biggest surprise of the list was Bill Gates. Out of the 100 million plus users on Twitter we wouldn't have predicted that one of the world's richest men and original technology heavyweights would also be the most unfollowed. 


Could it be because Gates mainly tweets about philanthropic based activities which the technology/entertainment/business skewed Twitter audience may be more averse to?

 

Kevin Garber
@ke_Ga

 

Posted by keving 

Comments [0]

First hand: Scaling under load spikes with Rackspace Cloud Server

Here at Melon Media we've tried many different hosting options for scalable infrastructure. From dedicated servers, to Amazon EC2, to Rackspace Cloud Sites, they all have their benefits and weaknesses. What can be really interesting is how they handle when they get hit with a large traffic spike. When the pressure is on and time is critical, some systems shine and others... cause nervous breakdowns.


With ManageTwitter we decided to use a Rackspace Cloud Server instance for the first time in a production. It has some interesting benefits over other cloud options including the ability to be resized to a larger instance on the fly. Since this was a small app, that we didn't really want to expend huge resources on, starting with a small Cloud Server and resizing it if needed seems like a good solution for scaling a small project.

ManageTwitter does not involve much writing to the hard drive. Most of the data used in the application is stored temporarily in memory. We started off with a 512 MB / 20 GB server which handled our initial load easily. The application performance is mostly limited by CPU performance.

Our first traffic spike came when TechCrunch posted an article about the service. I'd just briefly stopped by the computer to check my email after a healthy dinner of leftover crackers, yogurt and chocolate when I saw a retweet of TechCrunch's twitter stream about ManageTwitter pop-up on Tweetdeck. The article had only gone up minutes earlier but after firing up up http://managetwitter.com in my browser I saw the server was already not responding. A quick check confirmed SSH access wasn't going to respond under the load either. While Cloud Servers do provide burst capability, we'd clearly expended all resources.

I triggered a resize on the server within the Rackspace Cloud control panel and waited with anticipation of the server coming back up. The control panel show how the resize is progressing.

5%.... 10%... 

Flicking through TechCrunch & twitter in other windows I saw numerous complaints coming in about ManageTwitter being inaccessible. "Another Techcrunch review effect ?" posted jacopogio in the TechCrunch comments.

15%... 18%...

The site had been inaccessible for about 15 minutes at this point. Beads of sweat were starting to form.

19%... 20%... 10%...

What? I quickly fired up a chat window with Rackspace Cloud support.

"Hi, I've got a cloud server that's undergoing a high traffic spike. I'm trying to resize it, but the progress meter is falling back down. Will it complete, or is something wrong."

RS: "It will complete."

"Is it normal for it to go slowly like this? I've resized similar servers that went signficantly faster."

RS: "Yes, it's normal under high traffic."

"Is there anything I can do to make it go faster?"

RS: "Stop the traffic." 

Not the most useful thing to hear. I decided that I wasn't going to get much out of that conversation, so went and made some changes to the code, moving static files to a CDN, that would help reduce load if the server did get back up.

After about another 20 minutes things looked promising. The resize operation had got to 99%.

Suddenly it dropped to 0%. Frantically I jumped back into the Rackspace support chat and explained what had happened. I gave them my IP. Several minutes later a pop-up asked me to verify that the server had resized successfully. I decided to confirm without checking the integrity - we didn't have much valuable data stored at that point and at worst I could rebuild the code base from our development repository.

Fortunately most of the data was copied across successfully. It looked like a few hours of data was lost from the database for some reason, but otherwise it was a clean migration. I copied across the CDN integrated code and fired the site up my browser. The IP change seemed to happen almost instantly as the site came up straight away. We've been running smoothly on the 8192 MB / 320 GB instance ever since.

Ultimately the resize operation took 40mins to go from a 512 MB / 20 GB instance to 8192 MB / 320 GB under TechCrunch review traffic load. While the process was a little stressful and support could have been a little more helpful (a rare complaint from my experience with Rackspace!) it all worked pretty much as expected. For very little resources & cost the outcome was pretty much as good as we could have expected.

One interesting idea that we might recommend Rackspace implementing is using whatever technology rackspace use for IP switching to temporarily give a server a new IP so unexpected high load repairs/resizes can be performed faster.

What have your experiences been? Do you have any recommendations for how we could have handled this situation better?

James Peter

Posted by ManageFlitter 

Comments [2]

10,000 users & 550,000 unfollows

Wow, it's been a crazy 20 hours. After a surprising (and nice!) review on TechCrunch http://tcrn.ch/9sW6F3 traffic flew through the roof. We've gone from just under 400 users to over 10,000 and from just under 20,000 unfollows to over 500,000.

We're really glad people like the app. We've had it in the planning stages for several months. Everyone we mentioned it to who was an active Twitter user said they needed something that did what we do - make unfollowing people easy. We went through quite a few iterations of the interface before settling on one that was both straightforward and fast to use.

Thanks to everyone who's tweeted and posted about how much they enjoy using the app. We've already pushed out a few updates including a Dashboard and improvements to the backup to handle the increased load. Please keep us sending us suggestions and we'll see what we can do.

James Peter
Senior Developer
Melon Media

Posted by ManageFlitter 

Comments [0]