Renée

Last weekend, Mom and I babysat Julia, a 4yo family friend. We went to the zoo (and the heat index got up to 103, so we didn't stay too long - ended up at Dairy Queen, Julia's "favorite ice cream place EVER!" lol).

Here are the pictures from the zoo trip:

If you had to invite five friends or celebrities (or a combination of both) to a slumber party at your house tonight, who would you include and what movies would you rent?

I guess I'll just go for the girls. :)  It's hard to narrow to just 5! So, I'm going with 5 of my girl friends who love Smallville....and we will watch Smallville and Superman!

Crystal, Kim, Heidi, CylonBetty, and Faith :D

I've noticed that there are many tweeters out there that find the "API requests" aspect of Twitter very confusing.  Twitter doesn't do a very good job of explaining it, either.

I used to be one of these people...and no matter how many times I asked, I never got a good answer.

That is, until I found TweetDeck.  TweetDeck actually gives you a report of how many API requests you have sent and how many you have left in each hour - and it allows you to set how many requests you want to make an hour.

This information helped me to understand what and API really is...and I thought I'd share that with everyone else.  :)  It's extremely helpful if you use clients and are an avid tweeter like me.  I haven't gone over my API limit since I figured all this out. :)

So, here's the deal.

Think of API requests as a question you are asking a teacher in class.  Everytime you ask a question, you get an "API" mark on the board.  You are allowed a certain number of questions per class.  (It's not a perfect analogy, I know. lol)

So, basically, everytime you refresh the Twitter webpage, those are API requests.  One request for each refresh.

Now, if you are using a client like TweetDeck or Twhirl, then everytime the client asks Twitter for a list of all your friend's tweets, it is an API request.  And, everytime the client asks for your newest @replies, that is an API request.  So, everytime a client refreshes...it is using up at least two API requests.  If you are also getting your Direct Messages in your client, then that is a 3rd API request each refresh.

Twitter allows a certain number of these API requests per user, per hour.  It varies, depending on how friendly Twitter is being at the time.  ;)  (that pesky Fail Whale)  Usually, it is between 70 requests to 100 requests per hour.  It's best to stick to 70 or 80 per hour, to avoid going over your limit, since Twitter doesn't really tell you what the current API is.  (Once, it was down to 40 API per hour!)

Now, if you are just using the website to read your tweets, just make sure you are refreshing less than 70 or 80 times an hour and you should stay under the API limit. (Remember, looking at your @replies and DM's are additional API requests).

If you use a client, many of them offer a feature to set how many requests you want to make.  Then, the client will automatically refresh for you every minute or two minutes or ten minutes...depending on how you set it.

In TweetDeck, you can go into the settings and move the slider to 1 minute or 30 minutes for each of the following: tweets (the feed of tweets from everyone you follow), replies (the feed of tweets directed at you), and direct messages (the feed of tweets privately directed at you).  TweetDeck also shows you the percentage of API you use in an hour with the refresh times you've chosen.  TweetDeck automatically sets the API limit (meaning it automatically says you are allowed 70 or 80 or what ever it is per hour), so the percentage is based on that number.  TweetDeck knows how many API requests are being allowed per person at any given time.

This is a screenshot of my TweetDeck settings:

You can see that I have set my refresh times to 1min 40sec for both Tweets and Replies (meaning that every 1 minute and 40 seconds, TweetDeck will update both my tweets and replies) and my direct messages refresh every 7 minutes and 30 seconds.  Even though my tweets and replies both update at the same time...it's still a request for each one, so that's 2 API every 1.40.  And then there is an additional API request every 7.30 when TweetDeck checks for new direct messages.  All together, I'm using only 80% of the total API that Twitter is currently allowing me (which is actually 100 per hour, at the time of writing).  I like having this set lower like this, so I have extra API to play with.  If I want to get a quick refresh without waiting another 1.40, I can just hit refresh and use up a couple of my extra API.  TweetDeck now features the ability to look at tweeps twitter profiles on the web, rather than within TweetDeck, so you are not charged an API to look at the profile. :)  Another nifty feature of TweetDeck is that it tells you how many API you have left in your hour - and when your next refresh will happen.

Here you can see that I have 56 out of 100 API requests left this hour, and that my next hour begins at 2:34: (when I actually arrived at 2:34, I still had 21 requests left to use..tons of extra!)

Here you can see that my last refresh happened at 2:05 and I recieved 5 tweets.  My next refresh is at 2:07 (remember, I set my refresh time to 1 minute 40 seconds):

So, I always know when my next refresh is coming and I also know how many API I have left before my hour is done. :)

Other clients, like Twhirl, allow you to set your limit.  You can choose to allow 80 API per hour, and then set your refresh times for your tweets, replies, and DM's.  The only problem here is that if Twitter is only allowing you to have 60 API and hour and you set Twhirl to 80 per hour...then you are asking for 20 extra calls per hour.  You will exceed your limit and be unable to get your tweets, replies, and DM's until the next hour begins.  But, like I said, if you stick with 70 API per hour and then set your refresh times to, say, 85% of the total API (meaning you're not going to make a full 70 API requests in an hour, you'll make 59.5 requests that hour, which is 85% of 70.)  If you do this, and Twitter is only allowing 60 API per hour....you'll still be under the limit (just!).  :)

My Twhirl settings:

You can see that Twitter is allowing 100 requests per hour right now, but I have my settings to 'follow reduced API limits', meaning, I am only allowing myself 80 API requests per hour.  I do this so I have extra API to work with, and also so that when Twitter gets wonky and reduces the API limits for a little while, I won't get caught over my limit (hopefully).  Like in TweetDeck, you can slide the little arrow over to set the refresh times.  I have my tweets and replies set at every 2 minutes and my direct messages set at every 4 minutes.  Twhirl doesn't show you the percentage because it automatically keeps it at 100%.  If I were to move the arrow for replies refreshes...Twhirl would automatically adjust the other two arrows (for tweets and DM's) to keep me at 100%.  This is another reason I use the 'reduced limits' in Twhirl.  I like to stay under 100% per hour. :)

In Twhirl, you have to actually hover your mouse over a little image at the lower right corner to get your API info:

Twhirl shows you how many you've already used (below, you can see I have used 35 out of 100.  Since I'm set at 80 already, I know I'll never get to 100 and I won't go over my limit).  This is opposite of TweetDeck, which shows you how many API you have left in an hour.  The 'health' is a Twitter thing.  If Twitter is slow or not updating correctly, the health will be lower.  If the health is bad, you can pretty much bet that the API is temporarily reduced (so Twitter's servers aren't being worked so hard with all the requests coming in).

I hope this helped you understand Twitter API limits!  If you would like to follow me on Twitter, I'm @annabethblue.  My dogs also have a Twitter account (LOL) and they are @SheltieWorld.

Have fun tweeting!

What one thing, without fail, puts you in a bad mood?

Being interrupted when I'm speaking.  And especially being interrupted with a completely different topic.  SO RUDE.  I have to seriously control my anger when that happens.  I feel the immediate urge to destroy things and scream.  But, I can usually keep the temper down.

My best friend is a photographer and she got some cool shots today at the Botanical Center.  Here are a few of my favorites that didn't come out on my camera.  If you would like to see the rest of her pictures from our outing today, you can check out her pictures at Facebook: Botanical Center Album 1  &  Botanical Center Album 2.
.

More pictures from the Botanical Center!

The Botanical Center had a bonsai exhibit. :)

Today my bff and I went to the Botanical Center to see the displays. Here are the flowers we saw:

Suggested by Janet:

How about, “What’s the worst ‘best’ book you’ve ever read — the one everyone says is so great, but you can’t figure out why?”

Well, honestly, I don't know.  If a book doesn't get me hooked in the first 30 pages or so, I put it down for good.  It doesn't matter if it 'redeems' itself in the middle/end.  If the beginning is crap - I'm done. I don't waste my time.  

The only books I can think of right now that are not as 'awesome' as people say are the Twilight books.  They are just fanfic...it's not great writing.  I enjoyed the first one.  The characters are interesting to me.  I love character studies and highly descriptive writing, so I did like that aspect of Twilight. The middle books were ok, but the last book was positively atrocious.  I understand why the teens are loving them though...it's that little obsession that all teens have.  Mine was New Kids on the Block. ;)  I didn't go nuts over them or anything, I've never been that kind of person.  I really dislike that kind of behavior....it's not flattering.

The thing is, while I'm glad teens are reading - I'm appalled that they say things like "omg, they are the best books ever written!".  WHAT?  Someone needs to introduce these kids to classic literature, STAT.  When you read a book and there is layer upon layer of brilliance...THAT is great writing.  Twilight is just a nice, cute, safe story - not great writing.  But, I'll enjoy the frenzy of Twilight while it's here.  It's fun, anyway.

Although, I'll be avoiding any store that sells DVD's this weekend though - mass chaos.  Mass chaos.  I have no interest in being in a room full of screaming children. LOL

On a side note, there are some books that are 'hyped' up that really are amazing books.  The Road by McCarthy is one of them.  The Book Thief by Zusak is another.  Both of these books are written brilliantly.  Not only are the stories within great stories - beautiful portraits of humanity, hope, death, love, etc...but also, the authors were very clever in how they formatted the books.  The physical experience of reading these books is wonderful. 

In The Road, you are thrust into this stripped down, wasteland of a book - very little punctuation and structure...just like the world you are reading about.  You EXPERIENCE the loss, the emptiness, the alarming oddness of it all with the characters.  It took a while to get comfortable enough to read the book - and even then, you never really get comfortable.  Just like the characters, we experience this unnerving story in an unnerving way.  It's moving.  It's poignant.

The Book Thief does the same thing.  It's as if you are the diary that the narrator is writing upon.  Scribbles.  Thoughts.  Random sentences and random ponderings.  Descriptions of images.  It pulls you in and you are experiencing these memories with the narrator - like an elderly person telling stories of their youth.  Partial - something are faded, some things are vibrant.  Sometimes they remember the smell more than the conversation.  Sometimes colors are vibrant, even if the memory is not clear.  This is the way of human memory.  The author did a great job developing a visual style in the book that allows us to experience these memories with the narrator.

Maybe the stories aren't for you - the pain and the dispair.  But there is hope, happiness, love as well.  What makes these books great is that they are accurate portrayals of humanity.  Real, raw - nothing is photoshopped or airbrushed.  It's honest.  Heartbreaking.  Hopeful.  Human.  I think, if you read these books and allow yourself to actually EXPERIENCE them....you will understand how they are great peices of art.

If you had to teach something, what would you teach?

I do teach!  :)  I teach Information Literacy courses (college level).  I also teach private music lessons from time to time and I have taught art/cake decorating before.  :)  I love teaching.  :D