Before committing code, I explain it to Donkey Kong first to make sure it makes sense #codereview /cc @iamjohnford http://t.co/0dtFTYY

April 20th, 2011 1:12 PM via Twitter for MacReplyRetweetFavorite

@JohnJamesJacoby

John James Jacoby

(Also known as rubber duck debugging)

So now I’m asking how I should have done it in the first place — on my blog. What online service do you use to backup your data? And before anyone suggests it, Dropbox is out of the running as it’s too expensive for actual backup (it’s great for sync though!).

Thanks!

Do you run YOURLS? Do you use Twitter for iPhone (aka Tweetie)? If so, this post will be of interest to you.

Twitter for iPhone supports using a custom shortening service. Thankfully the YOURLS API will output a format that Twitter for iPhone will accept.

So how do you go about setting it up you ask? Start by going to your YOURLS admin area and clicking the “Tools” link at the top. About half way down the page will be your signature (it’s like a password). It will be a 10 character string. Hang onto this, you’ll need it soon.

Now open up Twitter for iPhone and go to the “Accounts & Settings” screen. You can get there by pressing the three dots in the bottom right and then scrolling to the very bottom of the screen that comes up and pressing the “Accounts & Settings” button. There will then be a “Settings” button in the bottom left. There in the Settings, select “Services” and then “URL Shortening”. Lastly pick the “Custom…” option.

Now to enter the URL to your YOURLS API script. I found it easiest to craft this URL on my computer and then e-mail myself the URL which I could then copy/paste on my iPod Touch. It was a lot easier than typing it all out on the little keyboard.

This is the URL you will need to use:

http://yourdomain.com/yourls-api.php?action=shorturl&format=simple&signature=YOURSIGNATURE&url=%@

Replace “YOURSIGNATURE” with your signature that you located earlier in this post and leave the rest alone (the “%@” is the placeholder that Twitter for iPhone will look for). If you e-mail yourself the URL, make sure that you still have “%@” at the end of the URL and not “%25@” or something.

Now when writing a tweet, press the character count button and the keyboard will disappear. There in the bottom right will be a button to shorten all URLs in your tweet. They’ll be shortened using your custom domain!

Cool, huh?

It turns out that svn blame is the command you want. It will output something like this:

$ svn blame http://svn.red-bean.com/repos/test/readme.txt
     3      sally This is a README file.
     5      harry You should read this.

So the first line was last modified by sally in revision 3 and the second line was last modified by harry in revision 5. Awesome huh?

Props to @ArtemR, @westi, and @zamoose for informing my noob ass on how to do this!

function viper_twitter_followers( $username = 'Viper007Bond' ) {

	// Just to keep the code below cleaner, create the cache key now
	$cache_key = "viper_twitter_followers_{$username}";

	// First we look for a cached result
	if ( false !== $followers = get_transient( $cache_key ) )
		return $followers;

	// Okay, no cache, so let's fetch it
	$result = wp_remote_retrieve_body( wp_remote_get( 'http://api.twitter.com/1/users/show.json?screen_name=' . urlencode($username) ) );

	// Check to make sure we got some data to work with
	if ( empty($result) ) {
		// Cache the failure for 1 min to avoid hammering Twitter
		set_transient( $cache_key, 0, 60 );
	}

	// Parse the data
	$data = json_decode( $result );

	// Make sure we were able to parse it
	// If not, cache the failure (like above)
	if ( !isset( $data->followers_count ) )
		set_transient( $cache_key , 0, 60 );

	// Success! Cache the result for an hour.
	$followers = (int) $data->followers_count;
	set_transient( $cache_key, $followers, 3600 );

	return $followers;
}

echo 'I have ' . viper_twitter_followers( 'Viper007Bond' ) . ' followers on Twitter!';

Reading Material:

• HTTP API: http://codex.wordpress.org/HTTP_API
• Transient API: http://codex.wordpress.org/Transients_API (expiring options basically)

If you have any questions about the above code, let me know and I’ll do my best to answer them.

• I checked out a copy of the theme I use to my computer (easier to work on it from my PC than my server). The SVN URL for themes hosted on WordPress.org is http://themes.svn.wordpress.org/. Find your theme there. For example my blog’s theme is http://themes.svn.wordpress.org/mystique/1.72/ (as of the time of this post).
• I made the changes I wanted to the theme on my computer (tweaks and such) and then uploaded it to my server.
• When a new version of the theme is released, I run svn diff > file.diff on my local checkout to get a file containing all of my modifications (this will be handy for the next step).
• I use svn switch to switch to the new version SVN URL. Your SVN client will attempt to merge in any changes by the theme author into your modified files, but it may run into collisions (where the theme’s author and you have modified the same area of a file). You’ll need to manually fix any collisions (this is why I check out to my PC instead of my server). I tend to just hit revert on the file and then using the diff file from the previous step for reference, re-add my modifcations.
• Upload the new version of the theme (with your modifications to your server).

Questions? Feel free to ask via my comments section.