Something a lot of folks asked for in TweetLater is the ability to search for people to follow based on keywords.

We’ve listened to your requests and have now built in that feature.

For each of your Twitter accounts, you can specify a range of keywords. We search for Twitter users who have recently published tweets that contain those keywords.

But, we don’t stop there. We know that many spammy accounts, which you wouldn’t want to follow, might also tweet about those keywords.

So, we’ve given you the ability to automatically filter the Twitter profiles and ignore the spammy ones.

You can filter based on the following:

• Keywords and text snippets contained in the profile bio, latest tweet, and Twitter username.
• The age of the Twitter account.
• Number of tweets.
• Following-to-follower ratio.
• Number of followers.
• Number of friends.
• The language of the tweets.
• Whether or not other TweetLater users have marked as spam or blocked the Twitter user.

We take those Twitter users who pass through your filters and place them on a queue where you can cast a human eye over them and make the final decision whether you want to follow them or not. (You can also tell the system to skip this review step and auto-follow those profiles).

Furthermore, you can pause and unpause the TweetLater Friend Finder at your discretion, and you can even tell it to automatically pause when it has found a certain number of potential friends, or when your own following-to-follower ratio exceeds a certain percentage.

It’s power at your disposal to follow quality Twitter users while you remain 100% in control. And in the process we save you the hundreds of hours you would have spent to achieve the same results.

Keyword following is available to TweetLater Professional users and, as always, this new feature is included in the low monthly subscription fee.

If you are a Professional user, you already have access to and will find the TweetLater Friend Finder keyword following under the Followers item in the menu.

If you have not yet taken up the 7-day free trial of Professional, then now is a great time to do so.

Now you can say buh-bye to spammers!

Sunday, July 26th, 2009 marks an important milestone in the development and growth of TweetLater.com.

At around 2:00 PM EST our number of users went past the 100,000 mark.

Many thanks to all our wonderful users who have made this possible.

It is our honor and privilege that you have chosen us to improve your productivity on Twitter.

Sunday, July 5th, 2009: A lot of people with legitimate Twitter accounts are currently suffering from having their accounts suspended (late Sunday afternoon).

It is not TweetLater’s doing or fault. So, please do not submit a TweetLater support request about it.

We just heard back from Twitter via email, and they said : “Spamcloud hit. We’re working on restoring accounts.”

We just need to be patient. The suspended accounts will be restored.

Update: We have no idea exactly what a “spam cloud” means. It is probably Twitter staff lingo for a massive spam attack.

Update: We have seen during previous spam attacks that Twitter tends to shoot first and ask questions later and indiscriminately lay down carpet bombing when their system comes under a spam attack. A lot of innocent-bystander accounts get massacred in the process, which they then have to restore afterwards. This is most likely what has happened again.

Update: We have no idea how long it will take Twitter to restore the wrongly suspended accounts. We do not have insight into that information.

Update: Twitter has now posted an update about the suspensions on their status blog.

Earlier today, we accidentally suspended a number of accounts.

We regret the human error that led to these mistaken suspensions and we are working to restore the affected accounts—we expect this to be completed in the next several hours.

One additional note: some the accounts suspended were using the third-party site Tweetlater. However, Tweetlater is not to blame for these suspensions nor is it in violation of our Terms.

Update: It appears that the issue has now been resolved and most suspended accounts have been restored. If your account is still suspended, please submit a support request at http://help.twitter.com and ask them to look at your account.

Post-Mortem by Dewald Pretorius, Owner of TweetLater.com

It is a real pity, but probably unavoidable, that some people have a tendency to jump to premature conclusions. A lot of folks almost immediately blamed TweetLater for the suspensions, and some even canceled their TweetLater accounts.

The reason why many TweetLater users were affected was very simple. We service a very large number of Twitter accounts. At time of writing that number exceeded 100,000 Twitter accounts. If Twitter makes a mistake that affects a large number of accounts, then naturally a large number of TweetLater users will be affected by the mistake.

I work very hard to maintain an excellent working relationship with Alex Payne, Matt Sanford, and Doug Williams of the Twitter API team, and with Del Harvey of the Twitter Spam team. They are always very responsive, professional, and helpful whenever I approach them.

And, I work equally hard to ensure, with the help and advice of the Twitter folks mentioned above, that TweetLater features always remain within the Twitter Terms and never does anything that Twitter frowns upon. TweetLater is my bread and butter, the thing that pays my mortgage. Hence, being a good neighbor of Twitter is absolutely essential, no, it is absolutely non-negotiable to me. I regularly turn down feature requests and offers of large additional payments for some new features, which I know will not sit well with Twitter and potentially jeopardize my service’s standing with Twitter.

The lesson from this is as follows: Things are often much simpler and far more benign than what some people want to believe. Perhaps it’s because conspiracy theories are more interesting, or more sensational, that people want to believe them rather than just the simple mundane truth. I don’t know.

It’s just very frustrating to watch your service, your passion, come under attack when you have done nothing wrong.

Nevertheless, there is also an upside to this matter, and I will conclude with it and close this post on a positive note.

This issue has created an enormous amount of free publicity for TweetLater, which makes me very happy.

Twitter implemented an API change on July 1st, 2009 so that all tweets originating via the API now have “from API” in the source display area of the Twitter timelines.

Previously the source area said “from web” when the originating application did not supply a source parameter when it publishes the tweet.

For the time being, TweetLater will continue to not provide a source parameter, which means your scheduled tweets will all have “from API” in the source display area.

We may evaluate this matter at a later date and decide if we should send a source parameter so that the tweets have “from TweetLater” in the source area.

Your feedback in the comments will be appreciated.

Update: Just want to clarify the following:

1. This was a change that Twitter unilaterally implemented on their side.
2. We cannot manipulate or change the source display. There are only two choices namely “from API” or “from TweetLater”. If we continue to not supply a source parameter, the tweets will continue to say “from API”.
3. We cannot go back to “from web” because Twitter does not allow that. From July 1 the only tweets that say “from web” are those that were manually entered in the web interface of Twitter.com.
4. It is not only TweetLater that is affected by this. The tweets from all third-party applications that don’t supply a source parameter now say “from API”.
5. Chances are that we will leave it as is, i.e., as saying “from API” for TweetLater. Our service is fortunately large enough, popular enough, and receive sufficient word-of-mouth exposure that we have no need to use the source display as an advertisement for TweetLater.

Update: This comment from Ryan deserves highlighting here in the post body: “If you are providing your followers with something valuable they won’t care where the tweets are coming from.” So true, Ryan! When we change over to the OAuth authentication method of Twitter, we may not have a choice anymore in terms of the source label. Our understanding is that when an application uses OAuth, all tweets from that application are automatically labeled with the name of that application. We will be changing over to OAuth as soon as Twitter takes their OAuth authentication out of beta testing. To be clear, changing to OAuth is not optional for a Twitter application. Twitter is going to deprecate the username/password authentication method.

Nobody needs to tell you that direct message SPAM is ever increasing on Twitter. Just try and wade through your DM inbox on some days.

We have just launched our brand-new integrated Direct Message Manager, where you can manage the DMs of all your Twitter accounts on one single page, in one integrated view.

From that page you can DM the senders, unfollow or block them, forward the DM to someone else, and more.

But even more powerful are the SPAM rules that you can define. The system will apply your rules every time you open or refresh your Direct Message Manager, and get rid of any unwanted DMs.

You can tell the system to just delete a DM when you mark it as SPAM, or delete it and unfollow the person, or delete it and block the person, etc.

Furthermore, you can also enter keyphrases that we must monitor. If someone sends you a DM that contains one of those keyphrases, we will automatically apply your SPAM rules to that DM.

In addition, you can also tell the system to look at what other TweetLater users think of person who sent you a DM. If someone else has already marked it as SPAM, you can tell us to automatically mark it as SPAM on all your Twitter accounts as well.

The Direct Message Manager is available to TweetLater Professional users (and those on the free trial of TweetLater Professional).

In keeping with our commitment, this powerful new feature comes at no additional charge.

You can access the Direct Message Manager by logging in to your TweetLater account, clicking the DMs menu tab, and then the DM Manager sub-menu tab.

TweetLater.com will be unavailable on Saturday May 30, 2009 between 8:00 AM EST and 11:00 AM EST.

During that time no automation will take place, and scheduled tweets and DMs will not be published.

When the site is available again, scheduled tweets and DMs that should have been published during the maintenance window will be published as soon as possible. Follower processing will then also resume where it stopped at the start of the window.

If you have any time-critical tweets or DMs, please modify their scheduled times now so that the times fall outside the maintenance window.

This blog and the support ticket system will remain online during the maintenance window.

Update:

The maintenance has been completed.

If you are still seeing the “down for maintenance page” with the message about propagation of the new IP address, you may want to consider switching over to use the DNS servers at OpenDNS.com on your computer.

In the fight against spam over the weekend, something horrible went wrong with new code in the tweet posting script. In some cases it duplicated scheduled recurring tweets. Go figure. Fix one thing and break another.

All recurring tweets that appear to be duplicates have been placed in the red error condition for you to review.

You can either bulk delete them with the Tweets, Delete function in the top menus, or, if it is a valid recurring tweet, you can simply edit and reschedule it.

There should be one non-red recurring (and still active) tweet, of which all the red ones are duplicates.

You may also find that some of your Ping.fm recurring tweets have been advanced several recurs into the future. Unfortunately we cannot fix that by means of a script. We ask that you edit those recurring tweets and reset the scheduled date and time to what it is supposed to be.

Apologies for the inconvenience.

As you probably know, the new follower vetting feature of TweetLater is very popular and very powerful in helping you follow only those folks you want to follow and yet enjoy the time-saving benefits of automation at the same time.

If you haven’t tried it yet, please do so. Follower vetting interrupts the auto-follow process for 72 hours and gives you the opportunity to decide whether you want to follow, ignore, or block a new follower.

Up to now you’ve been able to define your rules, which pre-selected the decisions for you so that you could quickly scan the list and record the decisions. But, you had no insight into how other people decided over the same followers. Did they approve the person, ignore the person, or block the person? You didn’t know.

We have now added aggregate (and anonymous) information to each new follower that will tell you what percentage of people approved the person, what percentage ignored the person, and what percentage blocked the person.

We hope this helps you keeping your Friends list in high quality, and getting rid of Twitter spammers.

To activate follower vetting on your Twitter account, login to TweetLater, click the Accounts menu tab and then the List Accounts sub-menu tab. Then click the Edit link of your Twitter account.

Select the vet new followers option. Important: You must also select either the auto-follow option or the welcome note option (or both), for follower vetting to work. If you don’t select either of those options, then there will never be anything to vet.

We’ve just switched on this feature on May 18, 2009. Over the coming weeks and months you will see more and more followers with percentages greater than zero, as we accumulate everyone’s decisions.

As part of this enhancement, and since we now keep a history of your decisions, you will now also never see the same follower more than once in your vetting list. That will deal very sweetly with the people who play the follow, unfollow, follow, unfollow game.

We are very pleased to announce that TweetLater now has an Application Programming Interface (API), which can be used by other developers to integrate their applications with TweetLater.

Twitter’s API is what enables you to use applications such as TweetDeck, Seesmic Desktop, Digsby, etc.

With TweetLater’s API those developers can now expand the functions of their applications and enable you to use TweetLater in those applications.

The API enables you to add, edit, and delete scheduled tweets. TweetLater Professional users can manipulate recurring tweets as well as scheduled @replies and DMs. More features will be added in the future. We just wanted to “get the API out the door” with this initial set of functions and not get bogged down in “enhancement paralysis”.

There is no additional charge for using the API.

The detail specs of the API are available at:

http://www.tweetlaterapi.com

Change is good, it is often said, and we hope this change will be good from your perspective.

Up to now you could delegate the management of your Twitter account to another TweetLater Professional user.

That has now changed.

You can now delegate your Twitter account management to both TweetLater Free and TweetLater Professional users.

What they can do on your account is determined by the TweetLater features they have access to in their accounts.

If you need someone to simply enter and edit scheduled tweets for you, then all they need is a TweetLater Free account.

If you want them to schedule recurring tweets, use TweetCockpit, etc., then they would need a TweetLater Professional account.

You can delegate your account to as many TweetLater users as you want.

Note: You still need a TweetLater Professional account to be able to do the delegation.

There is an issue with the TweetLater server. We’re investigating.

Further updates will follow.

Update April 27, 8:02 am — The server ran out of memory during the night. Everything is back online again.

Tired of manually deleting hundreds of direct messages from your DM Inbox?

No need to do that anymore.

With TweetLater you can now run a purge on your DM Inbox, and delete all DMs, DMs older than 7 days, or DMs older than 30 days.

The feature is available to TweetLater Free and TweetLater Professional users.

To access it, login to TweetLater, click the blue DM menu tab in the top menu bar, and then the Purge DMs sub-menu tab.

I want to give credit to Alex Payne, Matt Sanford, and Doug Williams of the Twitter API team.

They are a true pleasure to work with, they are extremely responsive, and they are very helpful.

Without their help, TweetLater would not be where it is today.

^DP

Up to now we have used several URL shortening services that provided you with no means to track the clicks on the links in your scheduled tweets and DMs.

We have now added bit.ly as a URL shortening option. All you need to do is add your bit.ly login and API key to your TweetLater profile. From that point forward we will shorten all your links using your bit.ly account. We won’t use any of the other URL shortening services.

This means you can track the clicks on all your links in your bit.ly account.

To activate bit.ly on your TweetLater profile, do the following:

1. Login to your TweetLater account.
2. Click the “Edit details” button in the sidebar on the right.
3. Enter your bit.ly login and API key in the appropriate fields.
4. Click the Save button.

It’s as easy as that. From that point forward all your links will be shortened using bit.ly.

This will also soon include also includes links on tweets created by your Blog Feeds, if you are a TweetLater Professional user. We have not yet now added it to the blog feeds processor.

The same two bit.ly fields are also available on the registration page, for folks who are registering new TweetLater accounts.

If you don’t have a bit.ly account, it’s super easy to register a free account at bit.ly.

If you don’t know where to get your bit.ly API key, login to your bit.ly account and click the “account” link in the top right corner of the page. Your API key is displayed on that page. Your “login” is the username that you use to login to bit.ly.

Friday, April 17, 7:44 PM EST.

If you’re seeing a lot of entries in TweetCockpit that say the Twitter API returned zero tweets, or if you have trouble with the Vetting page, or your tweets are not being published on time or not at all, or if you’re getting a message on the Twitter account add or edit page about invalid Twitter credentials, please note the following.

Both the Twitter API and the Twitter Search API seem to be very unresponsive at the moment.

We assume it is a fallout of the new Mikeyy worm attack that struck today.

It is not a problem in the TweetLater system. It’s just that we’re not getting data back from the two APIs.

We’re even seeing it on the batch jobs that run on two different servers. They have all slowed down to an absolute crawl, and are getting tons of fail whale errors back from Twitter.

Update April 17 9:14 PM EST — Just heard back from Alex Payne at Twitter. The Twitter system is completely overloaded at the moment. It was featured on Oprah earlier today, and is right now on Larry King. That’s why the APIs are not responding.

Update April 18 6:42 AM EST — The APIs are still extremely unresponsive. Some of the API calls are going through, but the majority are still getting fail whales.

Update April 18 12:22 PM EST — As noted in the Comments, I am waiting to hear back from Twitter. Earlier this morning I have asked them to check whether their spam team has perhaps put a block on my IP address. There is a remote possibility that someone could have scheduled tweets that the spam team considers as spam. They are not supposed to block my server IP address in that case, because it does not make sense to inconvenience 40,000+ people because of some stupid thing one person did. However, I have asked them to check whether that is the case. Personally I do not think this is the case, because some of the API calls are going through. There is not a complete blackout of calls from my server IP address. With a spam block the blackout is usually 100%, i.e., no API calls get through. Twitter is on PST, so I expect to hear back from them later this afternoon.

Update April 18 7:20 PM EST — Have not heard anything back from Twitter. It is extremely frustrating. However, let us remember that it is weekend.

Update April 18 8:27 PM EST — It appears as if the Twitter folks are still combating the new Mikeyy worm. Alex Payne and Matt Sanford of the API team are usually very responsive to my requests for assistance. I’m sure I will hear back from them the moment they are able to stop working though code and can check their emails. I’m convinced that in the Twitter offices combating the worm takes priority over everything else.

Update April 19 6:56 AM EST — The problem still persists, and Twitter has not responded yet.

Update April 19 10:36 AM EST — My head is now really very sore from repeatedly banging it against the wall. We should probably all resign ourselves that this issue will only be resolved on Monday during PST business hours. My sincere apologies to more than 44,000+ of my users who have been inconvenienced by this issue. If there were anything more I could do to have it fixed I would have done it days ago. ^DP

Update April 19 7:00 PM EST — Nothing new to report yet, except that the bruise on my head is now turning purple and black around the edges. For a third-party application like TweetLater to have an API issue, which essentially cripples the service for several days, with no support, is really not an acceptable situation. Even though it’s not done maliciously, it is an issue that Twitter will have to address. ^DP

Update April 19 9:05 PM EST — I saw Alex Payne, head of the Twitter API team, online and tweeted him. He has just replied with, “Got ‘em [my emails]. We should have it sorted for you tomorrow [Monday].”

Update April 19 10:11 PM EST — You may notice a slight improvement in TweetCockpit, adding and editing Twitter accounts, and Vetting. The API issue still exists, but I thought of a crude work-around, which I’ve now implemented. It may still be spotty, meaning it may work only intermittently. At least it’s better than nothing.

Update April 20 3:36 PM EST — The issue has now been resolved. TweetLater was unfortunately caught in the cross-fire between Twitter and spammers. With the latest round of spammers and worms that have hit Twitter, they have severely tightened their API behavior analysis algorithms. Due to the very high volume of Twitter API calls that TweetLater makes around the clock (we make several calls per second), one of the spam traps in the tightened algorithms was unfortunately triggered. As they say, **it happens. I have added additional code on my side to try and prevent this from again happening in the future. I will extend trial periods before end of day today. Follower processing will, over the next 8 hours, resume where it left off on Friday. ^DP

Update April 20 5:16 PM EST — A further update regarding follower processing. The normal 8-hour cycle of follower processing has resumed. Your account will be processed within the next 8 hours, and all the followers that followed you since Friday will be picked up. However, I’m seeing that the API is slow, which could be just because it is very busy or because the unblock is still filtering through all of Twitter’s networking equipment. The API usually speeds up late at night when the load is not so heavy. I’m expecting that things will return to normal within the next 24 hours. By then the TweetLater system should have caught up with the backlog that has built up. ^DP

The problems you’re having with TweetLater will automatically go away the moment that the Twitter API and Twitter Search API again start responding.

The trial periods of folks using the TweetLater Professional trial will be extended as soon as the issue is resolved. These extensions will be have been done between 5:20 PM EST and 5:50 PM EST.

Update April 20 9:57 PM EST — This issue is now officially resolved and closed. Follower processing has a HUGE backlog and will take 24 to 48 hours to catch up. At the time of writing there were 1.7 million unprocessed API calls on the processing queue, and the queue is still growing every second.

I want to express my sincere thanks to the Twitter API team, and to Matt Sanford in particular, for the efficient and professional help in getting this issue resolved.

Update April 21 10:38 AM EST — I have now employed a second server, which will process new API calls from the top of the processing queue. Hence, you may find that new followers of today are processed before folks who followed you during the outage. The outage has created a backlog of nearly 4 million API calls and it will take the system a few days to work through that backlog. ^DP

Update April 21 5:33 PM EST — Working through the backlog is going smoothly. There are now only 2.3 million API calls left. Piece of cake. ^DP

Update April 22 10:30 AM EST — It is official. The system has now finished working through the backlog of nearly 4 million API calls. We are now fully caught up, and just normal processing will take place from now on. At various points during the catch-up process, we were making in excess of 30 calls per second to the Twitter API, and the API handled it without blinking an eye.

The TweetLater website was unavailable for roughly 20.5 hours, from around 4:00 PM EST on April 16, 2009 to 12:30 PM EST on April 17, 2009.

Scheduled Tweets

All scheduled tweets that were supposed to have been published during the downtime have been placed into an error condition. They will not be automatically published. You need to review each one and decide if you want to reschedule it, or if you want to delete it.

Follower Processing

Follower processing has resumed where it stopped when the server went down. In other words, followers who have followed you during the downtime will be processed. It will take roughly 8 hours from 12:30 PM EST to cycle through all the Twitter accounts.

Profile Banners

We have already sent credits to the two people whose profile banners were affected by the downtime.

TweetLater Professional Subscriptions

All payment information sent by PayPal to our system during the downtime have been manually applied to the user accounts.

If any TweetLater Professional customer requires a partial refund for the downtime, we will be more than happy to oblige. On payments of $19.97 the credit is $0.57, and on payments of $29.97 the credit is $0.85. Please submit a support ticket and let us know if you want a credit.

TweetLater Professional Trial Members

We added two additional days to all TweetLater Professional trials that were active when the server went down.

Lessons Learned

1. Communication under these circumstances is vital. We’re blown away by the understanding and support that folks expressed on the other blog post that gave status updates during the downtime.
2. Hosting your blog and support system on a different server is very important, so that they are available even when your main site is down. This is something we put in place a little more than a week ago (thankfully).
3. We’re just again reminded that we’re working with a machine that can break. These server disks normally have a life span of 50,000 power on hours. However, just like any other piece of machinery they can break.
4. An attribute of crap is that it usually hits the fan at the most inconvenient times.

The TweetLater.com server is currently not responding.

We’re working on getting it back online as soon as possible.

If you happen to get to the login form, and it says your credentials are invalid, it’s because the database is down.

We will update this message when service has been restored.

Update 9:24 PM EST — The faulty drive is being replaced on the server. Unfortunately it was the primary drive, which holds the operating system. The OS needs to be reloaded, which they tell us will take between 6 and 8 hours.

Update 10:51 PM EST — The server rebuild is being started now. The database has been backed up, so there should not be any data loss. Follower processing and scheduled tweets are currently in mid-air suspension. When we reactivate the batch jobs once the server is rebuilt, follower processing will resume. All unpublished scheduled tweets and DMs that should have been published during the downtime will be published at that point. You may experience a sudden publishing of several tweets at the same time in your timeline if you had several tweets that should have been published during the downtime.

Update 11:04 PM EST –The hosting folks say that the server rebuild will take 6 to 8 hours. We’re going to assume a horizontal position for a few hours. When we’re awake and fresh, we’ll check that everything has been correctly configured on the server before we open TweetLater.com for logins. Will update here again in the morning.

Update 5:08 AM EST — The server has been rebuilt, and the backups are currently being restored.

Update 6:55 AM EST — Backups have been restored. There has been no data loss, apart from a few Keyword Alert archives that were corrupted beyond repair. It shouldn’t be an issue because those archives are only kept for 24 hours anyway. There are a few more configuration tasks left to do. It will probably be another hour, maybe two.

Update 7:02 AM EST — After doing an analysis of the scheduled tweets that should have been published during the downtime, we felt it would be prudent to put those tweets into an error condition so that they do not publish, and that you can decide whether you want to delete them or reschedule them. There are many Twitter accounts that will have a small avalanche of tweets published on them all at once if we just let the system publish the tweets. We’ll make a separate blog post regarding these tweets as soon as the system goes live.

Update 8:33 AM EST — It’s still going to be a while. Apache is still recompiling. Once that’s done, there are still a few configuration tasks to perform.

Update 9:14 AM EST — Apache recompile has finished. Now doing the last configuration tasks. It won’t be much longer.

Update 9:55 AM EST — Nearly there. Some of the batch jobs are already running, so you will see scheduled tweets being published. The site is still down because MEMCACHE is not yet running, and without it the site simply unceremonially crashes.

Update 11:01 AM EST — The hosting provider technicians forgot to compile several essential libraries into PHP. Just waiting for them to do that, then the site should come back online.

Update 12:01 PM EST — Just learned an important lesson. HostGator works on the tickets that have the oldest customer reply time first. When you keep submitting replies, such as “Please work on this, it is really important,” you bump your own ticket just further down the queue because the reply is new. So we learn a new thing every day.

Update 12:30 PM EST — And…….

WE ARE BACK!!!!

The big site header graphic at the top of each TweetLater page has been bugging us for a while, because it was taking up so much screen real-estate.

The site header has now been reduced in height, which allows you to see more above the fold on every page of the site.

The font used in the header has also been changed. The new font, we believe, looks a little more “professional” than the old one.

Last night a real rookie mistake with regex (regular expressions) caused some of our follower snapshots to become corrupted. Really badly corrupted.

The system is currently rebuilding all follower snapshots from scratch (April 10th, 2009 9:00 AM EST). This process will run until 12:00 PM EST.

The nett effect is that folks that followed you before 12:00 PM EST will not be processed. In other words, they will not be auto-followed and they will not receive your DM.

After 12:00 PM follower processing will resume as usual.

The rookie has been sent to stand in the village square so that all the children can ridicule him.

For the time being we have disabled the Friends/Followers counts that were displayed for each Twitter account on the List Accounts page.

The Twitter API was returning 0 Friends for certain accounts, which made the display rather useless, and the API has been extremely slow the past few days.

The slowness in the API resulted in the List Accounts page being very slow to load.

Once the API is back to its usual speedy self, we will re-enable the display of those counts.