* Update: We’ve suspended new signups on TweetPo.st until further notice. Full details here. *
I’m very happy to announce we have begun private beta testing the new version of TweetPo.st. I’ll include the full back-story below, but I personally apologize for the lack of communication on TweetPo.st the last few months and for any frustration it may have caused. We’re really excited about the new version because, in addition to being able to take on new users again, we have added support for Facebook Pages, our top requested feature.
TweetPo.st is a smarter way to update Facebook from Twitter. Here are the key features of the new version:
- Post tweets as Facebook Status Updates
- Post links you tweet on your Facebook Wall (so your friends can watch videos and see pictures right in their News Feed)
- Ignore @replies
- Change @mentions to real names
- Only post the tweets you specify to Facebook (using either inclusive or exclusive filters)
- Track links posted to Facebook with awe.sm
- *NEW* Supports both Facebook Profiles and Pages
- *NEW* Manage multiple posting configurations from Twitter accounts to Facebook Profiles or Pages
While we’re eager to get as many people using the new version of TweetPo.st as soon as possible, we need to limit the number of users until we work out all the kinks. We don’t anticipate this private beta period lasting more than a couple of weeks, but feel free to email support [at] tweetpo.st if you’d like to help us test before then. Otherwise, please follow @tweet_post to be the first to know when it’s publicly available.
The Back-Story
About 4 months ago, we started seeing bug reports from users who were encountering errors signing up for TweetPo.st. It took some investigation, but we soon figured out that, due to the way we originally built the app (i.e. not using Twitter OAuth, which wasn’t available at the time), TweetPo.st had hit Twitter’s following/follower ratio limit. Without going into too much detail, this required us to completely re-architect TweetPo.st from the ground-up using Twitter’s new Streaming API.
Originally, we thought we’d get this all done in December. But, we’re a small team working on 3 products (awe.sm, TweetPo.st, and fbShare.me). So, sometimes things don’t happen as quickly as we’d like. However, we dropped the ball on communications in this case. We didn’t want to announce a revised schedule until we had one we felt we could stick to, and new things continued to come up that kept us from finishing TweetPo.st. So, instead we went radio silent, which was not the right thing to do.
We apologize for not handling the situation as well as we should. And we hope you find the new version of TweetPo.st worth the wait when we make it publicly available in the next few weeks.






