the twitterbot has been unplugged [long live the twitterbot]
Approximately one month ago we launched an experiment called twitterbot. Over the course of one month, twitterbot gathered tweets related to items being discussed on current.com and posted them as comments. It racked up a total of 308 comments, and proceeded to spark a debate in the community about whether or not the twitterbot was useful, or just a nuisance.
You spoke, we listened.
As of a few days ago, twitterbot has posted it’s last tweet on current.com for a while. We still have a pretty definitive set of plans we intend to work on for twitterbot, which means it will return one day, but for the time being we felt it was best to pull the plug.
Here are a couple examples of plans we have for the twitterbot:
Tie current.com profiles to twitter profiles and allow our community to post items and comments via tweets. these wouldn’t appear as “twitterbot” posts, but instead as your own post/comment on current.com. just another way to participate
The twitterbot would continue to scan twitter for tweets related to articles, but once the tweet has been posted as a comment, the original twitterer would get an @reply informing them of the discussion going on over in the current.com community. They could then have the option of signing in on current.com via their twitter profile, and reclaim the tweet as their own comment.
A few of you might be thinking, “Aw, those ideas sound sweet! Why kill twitterbot if that’s the plan?”
The answer is pretty simple. We have a lot on our development plate, and in order to get where we are going we needed to make some compromises. In my opinion, the twitterbot test was a success. However, it did rub some of our community members the wrong way. We have a somewhat lengthy road ahead of us working on some unannounced projects like xxxxxxx xxxxxxx, xxxxxxx xxxxx, and xxx xxxxxxx xxx. We want to get our “bumps to TV” concept back in action, and this is proving to be a pretty big endeavor. In addition, after groups launches we will have another cycle dedicated to added group functionality. All of this stuff takes time and resources, so we decided to forgo some of the twitterbot work for the time being.
Plus, it felt wrong to keep it plugged in and active when so many were frustrated and/or confused by it in the first place. Thank you guys for the feedback, we certainly take it into consideration, and when twitterbot finally gets plugged back in you can rest assured it will be a different experience.
We honestly had no idea how hard Current:News was for her. Her reaction to the news definitely shed some light on the situation, and the more we discussed it the more this change made sense for everyone involved.
In case you haven’t checked it out yet, take a look at