voidfiles

{
    'cannonical_link': 'http://www.livemixtapes.com/mixtapes/2184/gang_related.html',
    'dj': {
        'link': 'http://livemixtapes.com/djs/404/dj_messiah.html',
        'name': 'DJ Messiah'
    },
    'img_url': 'http://images.livemixtapes.com/artists/messiah/gangrelated-5star/tn_cover.jpg',
    'score': {
        'value': '127',
        'views': '31,076',

voidfiles

{
    "result": "ok", 
    "value": {
        "more_pics": true, 
        "last_pic_id": 153217, 
        "pic_count": 200, 
        "pics": [
            {
                "city": {
                    "url": "/city/san-francisco-ca/", 

voidfiles

<?xml version="1.0" encoding="UTF-8"?>
<table xmlns="http://query.yahooapis.com/v1/schema/table.xsd" securityLevel="any">
    <meta>
        <author>Picplz</author>
        <documentationURL>http://picplz.com</documentationURL>
        <sampleQuery>select * from {table} WHERE entity='feed' AND type='interesting'</sampleQuery>
        <sampleQuery>select * from {table} WHERE entity='city' AND id=2 AND include_pics=1</sampleQuery>
        <sampleQuery>select * from {table} WHERE entity='user' AND username='zubillaga' AND include_pics=1;</sampleQuery>
    </meta>
    <bindings>

voidfiles

long_tweet = 'asdfasdf asd fasd fasdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdfasdf asdfasdfas dfasd fasd fasdf asdf asdf asdf asdf asdf asdf '
short_tweet = 'asdfasdf asd fasd fasdf asdf asdf asdf asdf asdf asdf asdf asdf'

url = "http://sia.tw/4fgs4"


def join_url(tweet, url):
    max_tweet_length = 139

voidfiles

"""
Extractive is a cool new service that does some on the fly web
crawling, and machine learning stuff like Entity Extraction, Full
text extraction, and more things I don't even understand. There
on demand api was very easy to use, but I built my first crawl 
job the other night, and had some trouble parsing the results. 

I thought I would put this up so people can see how I fixed the 
output.
"""

voidfiles

(function(F) {
    var registered_ids = {},
        id_to_module_map = {},
        interim_actions = {},
        cleanup_actions = {},
        clicked_ids = {},
        queueing = true;

    function register_id(id, callbacks, required_module) {
        id = id.replace('*', '.*');

voidfiles

(function(F) {
    var registered_ids = {},
        id_to_module_map = {},
        interim_actions = {},
        cleanup_actions = {},
        clicked_ids = {},
        queueing = true;

    function register_id(id, callbacks, required_module) {
        id = id.replace('*', '.*');

voidfiles

F.actionQueue.register('button-bar-fave', {
    interim: function(id) {
        var fave_button = document.getElementById(id);
        if (fave_button.className.search(/fave/) === -1) {
            fave_button.className = 'Butt ywa-track fave-button fave';
        } else {
            fave_button.className = 'Butt ywa-track fave-button';
        }
    },
    cleanup: function(id) {

voidfiles

<a href="#" class="Butt ywa-track fave-button fave" id="button-bar-fave" data-ywa-name="Favorites star" onclick="return F.actionQueue.queue_click(this.id);" tabindex="4">
    <span class="ie-hack">&nbsp;</span>
    <span class="star">★</span> &nbsp;Favorite
</a>

voidfiles

Production Tear Down 

How does flickr handle the problems of loading scripts asynchrounsly.

Wether, or not you are using an asynch loader, or you are puting your script loading at the bottom of your dom you have a problem. In some cases your scripts will load after the user has clicked on something that requires there to be a javascript function to handle the click. 

If you have built out a fully accessible site you might have a non-js flow, but that is usually substandard if the user has javascript, and it just is taking to long for your scripts to load. What you need some way of handling events before all of your scripts have finished loading.

First we I am going to take a look at how flickr does this, and then I want to break down a more generic way of doing this.