- http://twit.grayghostvisuals.com
- Green light for any browser on all Operating Systems (Windows, Mac, Linux)
<head>
<!-- jQuery -->
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.8.0/jquery.min.js"></script>
<script>window.jQuery || document.write('<script src="js/vendor/jquery-1.8.0.min.js"><\/script>')</script>
<!-- Twit -->
<script src="js/twit.js" async></script>
</head>
<body>
<!-- twit -->
<div id="twit-container">
<ul id="twitter_update_list">
<li id="twitter_feed"></li>
</ul>
</div>
<!-- twit -->
</body>
// Load Twit
window.onload = function() {
var ajax_load = "<img class='twit-loader' src='img/loading.gif' alt='Loading...'>",
twitter_preferences = {
count : [enter_twit_count_here],
username : '[username_goes here]'
retweets : [false, true],
replies : [false, true]
},
twitterUrl = 'http://twitter.com/statuses/user_timeline.json?screen_name=' + twitter_preferences.username + '&callback=twitterCallback&count=' + twitter_preferences.count + '&include_rts=' + twitter_preferences.retweets + '&exclude_replies=' + twitter_preferences.replies;
script = document.createElement('script');
$("#twitter_feed").html(ajax_load);
script.setAttribute('src', twitterUrl);
script.setAttribute('async', true);
document.body.appendChild(script);
};
-
Unauthenticated Twitter API calls are permitted 150 requests per hour https://dev.twitter.com/docs/rate-limiting
-
Retweets and favorites will not display currently. Only single user tweets will display at the moment (this will eventually change)
-
jQuery Plugin → checkout our jQueryPlugin feature branch
-
Due to unauthenticated Twitter API requests being limited to 150 per hour we're working out a way to cache them properly. Feel free to chime in if you have a better way or are great with Twitter's oAuth (350 per hour)
August 16, 2012 – API v1.1 migration period
- Version 1.1 of the Twitter API. https://dev.twitter.com/blog/changes-coming-to-twitter-api
- required authentication on every API endpoint
- a new per-endpoint rate-limiting methodology
- changes to our Developer Rules of the Road, especially around applications that are traditional Twitter clients.
- No Whitespace
- Play Nice
- Keep it simple stupid
- Use a clean branching model with forks (We use Gitflow Model w/SourceTree: Master → Develop → Feature → Hot Fix → Release)
- Don't shoot the bird
We would like to thank the following contributors and their awesome-nesses...
- JSHint corrections (twit.js)
- Callback Function Rewrites (twit.js)
- Twitter API Unauthenticated calls research