I want to thank everyone who helped to make the "Twitter Bomb" to promote the Petition to End Racial Violence a mild success. Especially @MAfreedom who went above and beyond the call of duty to ensure it's success. He committed early to the game plan and stayed through to the end. Tweeting dozens of times in an attempt to get the ball rolling.
By mild success I mean that, although we fell short of our primary goal of getting the hashtag #EndRacialViolence to trend, we did achieve some secondary goals. The first, was that we got over two dozen pro-white activists to work together in an extended day long effort to advance our cause. Together, we tweeted hundreds of messages in a 20 hour period, most of them coming the the eight hour period between 8am-2pm yesterday. You can see them on the Twitter results page for the hashtag, "#EndRacialViolence". Second, we were able to increase the pace of signature gathering from about 1-2 signatures per hour, when we started, to an average of 10-12 an hour as things heated-up. The signature pace slowed in the evening as our efforts began to flag after eight tedious hours of tweeting.
We also learned a lot about how to be more effective for next week's Twitter Bomb, which is scheduled for the early hours of Monday morning.
One of the things I learned was that under a massive load, Tweetdeck isn't reliable. I scheduled almost 200 tweets to go out from 8am yesterday morning to 5am this morning -- less than half of them were actually posted. At first I thought Twitter's servers were overloaded from Super Bowl tweets, but, as the night wore-on, it became clear that wasn't the problem. Because many of them had identical wording (I tweeted the same 12 messages or so all day) I think Tweetdeck was reading them as duplicate Tweets and dropping them. If that's the case, they must be using an algorithm to determine when something is a duplicate or not. I'll change how I schedule them next week, to avoid that problem.
More on that later . . .
No comments:
Post a Comment