Hello! Today, am just going to step a side(from code) and share with you some of the coolest things I have in my pocket! First of all, let us both agree that the web is too big to beat and you could spend the rest of your life roaming around in search for the right information!
I don’t know about you but I face information overload quite often and I end up not getting the answers to my questions even though I have the whole day to sit in front a computer. You are probably thinking, ‘what about just opening a browser and typing some key words into Google ?’ Yeah, trust me, you can do that and still find nothing useful.
Let us learn how to use github public repository.This happens to be my last post on this Programming With Twitter API journey. I do not feel sad because this is actually just the beginning! I will not stop here, I will keep making something better out of it. This has been a great adventure, very informing and fun. So, without much a do, I want to show you(if you have not done this before), how to make our code publicly accessible to interested people who want to read it and even use it for their own learning or applications. I am going straight to github – by the way this is not the only one, look for bitbucket or something that makes you happy.
In this challenge, we are required to perform some data parsing using JSON methods. Since I am going to use Python, I will be importing some libraries into my file and then make some real API calls to Twitter instead of using the provided JSON data.
I am going to do several things and still make this post as short as possible!
#perform some data parsing using json.
#make api calls to twitter servers
#### mozilla challenge – programming with twitter api
import urllib2 #python module for handling urls
import json #json anyone??
url = ‘http://api.twitter.com/1/statuses/user_timeline/eenvincible.json’
Hi! I am starting to dive deeper into the current challenge – Programming Twitter API. Just a quick basic review of the API requirements before we make any calls! Oh wait, why not take a look at what an API call looks like?
If you type the URL shown in that snapshot into your browser of choice, you will see something like this displayed:
Ugh! How messy is that? I really hope you will be able to look through that mess and identify some information that could help you build something useful!