BLOGGER TEMPLATES AND TWITTER BACKGROUNDS »

Saturday, April 17, 2010

Armon Bassett's Twitter

 Ohio guard Armon Bassett has been mum on whether or not he will return for his senior season next year, and while no official statements have been made, it's easy to make educated guesses based on his tweets.  
I hope this post doesn't cause him to delete me from his Twitter followers, but Armon Bassett has been dropping huge hints at what he is going to do next year in terms of his basketball career.  Three tweets that have stuck out to me are the following:
  1. Today should be John Groce Appreciation Day. In my heart I kno he couldve had that Clemson job but didn't take it bcuz of Us
  2. Hello world! Great day to be a bobcat..
  3. Bout to tell coach groce to schedule butler next yr.. At butler too.. I want a piece them
This first tweet insinuates that Groce was offered the coaching job at Clemson, but he stayed because of the team he is going to have next year.  No official statements have been made by Groce nor the Athletic Department on this issue, so Armon made a statement to those who happen to be following him on his social network. 

The second tweet is a little more generalized, but it stills give us a look at what is going through his head right now.   He loves being a Bobcat, and it sounds like through his other tweets, he loves being in Athens and on campus.  

The last is the biggest red flag of all.  Not because it holds untruths or defames any person or thing, but because it is a total giveaway to what Armon wants.  He straight up tells his followers, "I want a piece of Butler, NEXT YEAR."  

Hint, you can't play Butler if you're not in college. 
So followers, you can always trust your athletes to give you the most personal and up to date information on themselves, without ever having to talk to them.  Twitter is wonderful.  

And if for some reason, Armon starts moderating his content (Say, moderates it so that the journalists can't figure out whats going on), I'll be happy to say I wrote this on my blog first. 

0 comments: