CINXE.COM
willnorris.com - there's more to life than this
<!DOCTYPE html> <html lang="en-US" prefix="og: http://ogp.me/ns#"> <head><script type="text/javascript" src="/_static/js/bundle-playback.js?v=HxkREWBo" charset="utf-8"></script> <script type="text/javascript" src="/_static/js/wombat.js?v=txqj7nKC" charset="utf-8"></script> <script>window.RufflePlayer=window.RufflePlayer||{};window.RufflePlayer.config={"autoplay":"on","unmuteOverlay":"hidden"};</script> <script type="text/javascript" src="/_static/js/ruffle/ruffle.js"></script> <script type="text/javascript"> __wm.init("https://web.archive.org/web"); __wm.wombat("https://willnorris.com/","20130210110921","https://web.archive.org/","web","/_static/", "1360494561"); </script> <link rel="stylesheet" type="text/css" href="/_static/css/banner-styles.css?v=S1zqJCYt" /> <link rel="stylesheet" type="text/css" href="/_static/css/iconochive.css?v=3PDvdIFv" /> <!-- End Wayback Rewrite JS Include --> <meta charset="UTF-8"/> <meta name="viewport" content="width=device-width"/> <title>willnorris.com - there's more to life than this</title> <link rel="profile" href="http://gmpg.org/xfn/11"/> <link rel="pingback" href="https://willnorris.com/wordpress/xmlrpc.php"/> <!--[if lt IE 9]> <script src="https://willnorris.com/content/themes/publish/js/html5.js" type="text/javascript"></script> <![endif]--> <link rel="alternate" type="application/rss+xml" title="willnorris.com » Feed" href="https://web.archive.org/web/20130210110921/https://willnorris.com/feed"/> <link rel="alternate" type="application/rss+xml" title="willnorris.com » Comments Feed" href="https://web.archive.org/web/20130210110921/https://willnorris.com/comments/feed"/> <link rel="stylesheet" id="openid-css" href="https://web.archive.org/web/20130210110921cs_/https://willnorris.com/content/plugins/openid/f/openid.css?ver=519" type="text/css" media="all"/> <link rel="stylesheet" id="jetpack-slideshow-css" href="https://web.archive.org/web/20130210110921cs_/https://willnorris.com/content/plugins/jetpack/modules/shortcodes/css/slideshow-shortcode.css?ver=3.6-alpha-23334" type="text/css" media="all"/> <link rel="stylesheet" id="publish-style-css" href="https://web.archive.org/web/20130210110921cs_/https://willnorris.com/content/themes/publish/style.css?ver=3.6-alpha-23334" type="text/css" media="all"/> <script type="text/javascript" src="https://web.archive.org/web/20130210110921js_/https://willnorris.com/wordpress/wp-includes/js/jquery/jquery.js?ver=1.9.0"></script> <script type="text/javascript" src="https://web.archive.org/web/20130210110921js_/https://willnorris.com/wordpress/wp-includes/js/jquery/jquery-migrate.js?ver=1.0.0"></script> <link rel="EditURI" type="application/rsd+xml" title="RSD" href="https://willnorris.com/wordpress/xmlrpc.php?rsd"/> <link rel="wlwmanifest" type="application/wlwmanifest+xml" href="https://willnorris.com/wordpress/wp-includes/wlwmanifest.xml"/> <meta name="generator" content="WordPress 3.6-alpha-23334"/> <link rel="shortlink" href="https://web.archive.org/web/20130210110921/http://wjn.me/"/> <link rel="author me" href="https://plus.google.com/111832530347449196055"/> <link rel="license" href="http://creativecommons.org/licenses/by-nc-sa/3.0/"/> <meta property="og:type" content="blog"/> <meta property="og:description" content="there's more to life than this"/> <meta property="og:locale" content="en_US"/> <meta property="og:site_name" content="willnorris.com"/> <link rel="openid2.provider" href="https://web.archive.org/web/20130210110921/https://willnorris.com/wordpress/index.php/openid/server"/> <link rel="openid2.local_id" href="https://willnorris.com/author/willnorris"/> <link rel="openid.server" href="https://willnorris.com/wordpress/index.php/openid/server"/> <link rel="openid.delegate" href="https://willnorris.com/author/willnorris"/><meta http-equiv="X-XRDS-Location" content="https://willnorris.com/?xrds"/> <meta http-equiv="X-Yadis-Location" content="https://willnorris.com/?xrds"/> <script> var _gaq = _gaq || []; _gaq.push(['_setAccount', 'UA-620101-2']); _gaq.push(['_trackPageview']); (function() { var ga = document.createElement('script'); ga.async = true; ga.src = '//web.archive.org/web/20130210110921/https://www.google-analytics.com/ga.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); })(); </script> </head> <body class="home blog"> <div id="page" class="hfeed site"> <header id="masthead" class="site-header" role="banner"> <a class="site-logo" href="https://web.archive.org/web/20130210110921/https://willnorris.com/" title="willnorris.com" rel="home"> <img class="no-grav" src="https://web.archive.org/web/20130210110921im_/https://secure.gravatar.com/avatar/2025929025b4492c58961f28cc4ed93d/?s=100&d=mm" height="100" width="100" alt="willnorris.com"/> </a> <hgroup> <h1 class="site-title"><a href="https://web.archive.org/web/20130210110921/https://willnorris.com/" title="willnorris.com" rel="home">willnorris.com</a></h1> <h2 class="site-description">there's more to life than this</h2> </hgroup> <nav role="navigation" class="site-navigation main-navigation"> <h1 class="assistive-text">Menu</h1> <div class="assistive-text skip-link"><a href="#content" title="Skip to content">Skip to content</a></div> <div class="menu-primary-container"><ul id="menu-primary" class="menu"><li id="menu-item-1002" class="menu-item menu-item-type-custom menu-item-object-custom current-menu-item current_page_item menu-item-1002"><a href="/web/20130210110921/https://willnorris.com/">Home</a></li> <li id="menu-item-1000" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-1000"><a href="https://web.archive.org/web/20130210110921/https://willnorris.com/about">About</a></li> </ul></div> </nav><!-- .site-navigation .main-navigation --> </header><!-- #masthead .site-header --> <div id="main" class="site-main"> <div id="primary" class="content-area"> <div id="content" class="site-content" role="main"> <article id="post-995" class="post-995 post type-post status-publish format-link hentry category-technology"> <header class="entry-header"> <h1 class="entry-title"><a href="https://web.archive.org/web/20130210110921/https://willnorris.com/2013/01/upcoming-wordpress-3-6-features" title="Permalink to Upcoming WordPress 3.6 features" rel="bookmark">Upcoming WordPress 3.6 features</a></h1> </header><!-- .entry-header --> <div class="entry-content"> <p>Mark Jaquith <a href="https://web.archive.org/web/20130210110921/http://make.wordpress.org/core/2013/01/07/wordpress-3-6-autosave-and-post-locking/">talking about WordPress 3.6</a>, which will be focused on the post authoring experience:</p> <blockquote><p> I want people to trust WordPress with their posts. They should never fear that something they’ve spent time creating or editing should go away due to their mistake or ours or that of a third party. Mistakes and errors should be recoverable. I can’t stress enough how important it is that people believe this and have good reason to believe it. If a post gets lost, there is a catastrophic loss of trust, that could take years to be regained (if indeed it ever is). This is people’s time and their creative output we’re talking about. If we’re not valuing those things above all else, then our priorities are seriously out of order. This is an all-hands-on-deck item for 3.6. </p></blockquote> <p>I’m not sure if I just haven’t been paying close enough attention in the past, but the last couple of WordPress releases have been marked by a very clear product focus and zeal that is impressive, even for WordPress standards.</p> </div><!-- .entry-content --> <footer class="entry-meta"> Posted on <a href="https://web.archive.org/web/20130210110921/https://willnorris.com/2013/01/upcoming-wordpress-3-6-features" title="12:36 pm" rel="bookmark"><time class="entry-date" datetime="2013-01-07T12:36:51+00:00" pubdate>January 7, 2013</time></a><span class="byline"> by <span class="author vcard"><a class="url fn n" href="https://web.archive.org/web/20130210110921/https://willnorris.com/author/willnorris" title="View all posts by Will Norris" rel="author">Will Norris</a></span></span>. <span class="cat-links"> Posted in <a href="https://web.archive.org/web/20130210110921/https://willnorris.com/category/technology" title="View all posts in technology" rel="category tag">technology</a> </span> </footer><!-- .entry-meta --> </article><!-- #post-995 --> <article id="post-990" class="post-990 post type-post status-publish format-link hentry category-technology tag-diso tag-indieweb"> <header class="entry-header"> <h1 class="entry-title"><a href="https://web.archive.org/web/20130210110921/https://willnorris.com/2012/12/rebuilding-the-web-we-lost" title="Permalink to Rebuilding the Web We Lost" rel="bookmark">Rebuilding the Web We Lost</a></h1> </header><!-- .entry-header --> <div class="entry-content"> <p>Anil Dash follows up his essay from last week with <a href="https://web.archive.org/web/20130210110921/http://dashes.com/anil/2012/12/rebuilding-the-web-we-lost.html">Rebuilding the Web We Lost</a>:</p> <blockquote><p> But the most important question we can ask is: How do we rebuild the positive aspects of the web we lost? There are a few starting points, building on conversations we’ve been having for years. Let’s look at the responsibilities we must accept if we’re going to return the web to the values that a generation of creators cared about. </p></blockquote> <p>Color me inspired and ready to jump backing to putting into practice the principles I’ve been professing for so many years. It’s time to stop talking and (re)start doing.</p> </div><!-- .entry-content --> <footer class="entry-meta"> Posted on <a href="https://web.archive.org/web/20130210110921/https://willnorris.com/2012/12/rebuilding-the-web-we-lost" title="5:58 pm" rel="bookmark"><time class="entry-date" datetime="2012-12-18T17:58:17+00:00" pubdate>December 18, 2012</time></a><span class="byline"> by <span class="author vcard"><a class="url fn n" href="https://web.archive.org/web/20130210110921/https://willnorris.com/author/willnorris" title="View all posts by Will Norris" rel="author">Will Norris</a></span></span>. <span class="cat-links"> Posted in <a href="https://web.archive.org/web/20130210110921/https://willnorris.com/category/technology" title="View all posts in technology" rel="category tag">technology</a> </span> <span class="sep"> | </span> <span class="tags-links"> Tagged <a href="https://web.archive.org/web/20130210110921/https://willnorris.com/tag/diso" rel="tag">diso</a>, <a href="https://web.archive.org/web/20130210110921/https://willnorris.com/tag/indieweb" rel="tag">indieweb</a> </span> </footer><!-- .entry-meta --> </article><!-- #post-990 --> <article id="post-985" class="post-985 post type-post status-publish format-standard hentry category-technology"> <header class="entry-header"> <h1 class="entry-title"><a href="https://web.archive.org/web/20130210110921/https://willnorris.com/2012/12/all-https-all-the-time" title="Permalink to All https, all the time" rel="bookmark">All https, all the time</a></h1> </header><!-- .entry-header --> <div class="entry-content"> <p><img src="https://web.archive.org/web/20130210110921im_/https://i1.wp.com/willnorris.com/content/uploads/2012/12/https-willnorris-com.png?resize=181%2C33" alt="willnorris.com secure URL" class="alignleft size-full wp-image-989" data-recalc-dims="1"/></p> <p>This weekend, inspired by Tim Bray’s recent post <em><a href="https://web.archive.org/web/20130210110921/https://www.tbray.org/ongoing/When/201x/2012/12/02/HTTPS">Private By Default</a></em>, I changed my website <a href="https://web.archive.org/web/20130210110921/https://willnorris.com/">willnorris.com</a> to serve all traffic using HTTPS. At least for the time being (read: until I find something I’ve terribly broken), all non-HTTPS traffic will be redirected to the secure version of the site.</p> <p>I’ve had HTTPS support enabled on my site for about a year, primarily for ensuring that my own credentials were secure when logging into the WordPress admin section of the site. You could always manually browse to the secure version of any page if you manually typed in the ‘https’, I just never really advertised it. Now this site is all HTTPS, all the time.</p> <h2>Why</h2> <p>Tim has an <a href="https://web.archive.org/web/20130210110921/https://www.tbray.org/ongoing/When/201x/2012/12/02/HTTPS#p-2">excellent list</a> of reasons why privacy should be the default, but it was his first point that really resonated with me:</p> <blockquote><p> This blog isn’t terribly controversial. But if only the “controversial” stuff is private, then privacy is itself suspicious. Thus, privacy should be on by default. </p></blockquote> <p>In a free society, one shouldn’t have to justify their right to privacy. Our view on privacy has gotten so mixed up that “Well, what have you got to hide?” is accepted as an almost <em>reasonable</em> question. As Bruce Schneier puts it so eloquently in his essay <em><a href="https://web.archive.org/web/20130210110921/https://www.schneier.com/essay-114.html">The Eternal Value of Privacy</a></em>,</p> <blockquote><p> A future in which privacy would face constant assault was so alien to the framers of the Constitution that it never occurred to them to call out privacy as an explicit right. Privacy was inherent to the nobility of their being and their cause [...] It’s intrinsic to the concept of liberty. </p></blockquote> <p>So why make communication with this little site private? Because I can; it’s the one small part of the Internet that I do have complete control of. It doesn’t protect <em>my</em> privacy in any way… my site is accessible by anyone. But it does help protect <em>your</em> privacy, as anyone listening in on your Internet traffic won’t know what you’re looking at. And more importantly, it helps combat the notion that privacy is reserved for controversial stuff.</p> <p>One of the things I’ve really appreciated about <a href="https://web.archive.org/web/20130210110921/http://indiewebcamp.com/">Indie Web Camp</a> is its focus on <em>builders</em>, people actively working to further the principles of owning one’s own identity and content online. While there is certainly effort spent on making these solutions usable for a non-technical audience, the first step must be to get things working on our own sites. If, like Tim Bray, I believe that the web should be private by default, then I first have to make my own site private by default.</p> <h2>Flipping the Switch</h2> <p>There’s basically three steps to having a secure website: finding a web host in your budget that will support HTTPS, getting an SSL certificate, and configuring your site to use HTTPS.</p> <p>Until relatively recently, you effectively needed a private IP address to run a secure website. And for the last year, I’ve been doing just that by running my site from a virtual private server at Joyent, and it’s a much more expensive hosting option. However, client support for <a href="https://web.archive.org/web/20130210110921/http://en.wikipedia.org/wiki/Server_Name_Indication">Server Name Indication</a>, which allows multiple secure sites to share an IP address, is now at a point that shared hosting providers are beginning to support secure sites for reasonable prices. This weekend, I moved my site to the <a href="https://web.archive.org/web/20130210110921/http://textdrive.com/">new TextDrive</a>, which easily supports SNI on their shared hosting accounts at no additional cost.</p> <p>As for the SSL certificate itself, Tim recommends a few sources in his article. Personally, I use a <a href="https://web.archive.org/web/20130210110921/https://www.gandi.net/ssl">certificate from Gandi</a>, which is also where I register my domains. Certificates are free for the first year when you register or transfer your domain there, and then $16 a year thereafter. A far cry from the $100+ certificates used to cost. There are of course free options as well, though in my experience (particularly with StartSSL), their sites tend to be much harder to navigate and understand.</p> <p>Finally, Apache and WordPress make it very easy to use SSL. Within WordPress, you can simply set your site URL to include ‘https’ at the beginning, and all generated URLs will be secure. Unlike Tim, I additionally chose to redirect all HTTP traffic to HTTPS. I did this with a simple rewrite rule in my <code>.htaccess</code> file:</p> <pre><code>RewriteCond %{HTTPS} off RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [L,R] </code></pre> <p>We’re finally at the point that it’s not prohibitively expensive to run a secure website. A certificate costs about the same as a domain registration, and web hosting companies are beginning to support SNI. There are still non-trivial technical hurdles to get over, and perhaps more importantly, education as to why “privacy by default” on the web matters. But it’s now at least possible.</p> </div><!-- .entry-content --> <footer class="entry-meta"> Posted on <a href="https://web.archive.org/web/20130210110921/https://willnorris.com/2012/12/all-https-all-the-time" title="9:10 pm" rel="bookmark"><time class="entry-date" datetime="2012-12-16T21:10:09+00:00" pubdate>December 16, 2012</time></a><span class="byline"> by <span class="author vcard"><a class="url fn n" href="https://web.archive.org/web/20130210110921/https://willnorris.com/author/willnorris" title="View all posts by Will Norris" rel="author">Will Norris</a></span></span>. <span class="cat-links"> Posted in <a href="https://web.archive.org/web/20130210110921/https://willnorris.com/category/technology" title="View all posts in technology" rel="category tag">technology</a> </span> </footer><!-- .entry-meta --> </article><!-- #post-985 --> <article id="post-982" class="post-982 post type-post status-publish format-standard hentry category-technology tag-pocket tag-shortlinks"> <header class="entry-header"> <h1 class="entry-title"><a href="https://web.archive.org/web/20130210110921/https://willnorris.com/2012/12/the-links-we-lost" title="Permalink to The Links We Lost" rel="bookmark">The Links We Lost</a></h1> </header><!-- .entry-header --> <div class="entry-content"> <p>Yesterday, I <a href="https://web.archive.org/web/20130210110921/https://plus.google.com/+willnorris/posts/Hwfibs334wq">shared</a> an article from Anil Dash entitled <em><a href="https://web.archive.org/web/20130210110921/http://dashes.com/anil/2012/12/the-web-we-lost.html">The Web We Lost</a></em> on Google+. The article is great, and covers a topic that I have cared very deeply about for a long time. However, today I noticed that it turns out that I didn’t actually share a direct link to Anil’s article, but rather to a pocket.co shortlink that redirected to the article. I didn’t <em>mean</em> to do this; I simply used the normal share button from within the Pocket app on my Android device and this is what got shared.</p> <p><img src="https://web.archive.org/web/20130210110921im_/https://i0.wp.com/willnorris.com/content/uploads/2012/12/pocket-share-to-google.png?resize=525%2C180" alt="pocket share to google" class="alignnone size-full wp-image-983" data-recalc-dims="1"/></p> <p>A number of others apps pull these kinds of shenanigans too like Pulse News and even Google’s own Currents app, and it annoys me to no end. I mean, I get why they do it (statistics tracking, purported <a href="https://web.archive.org/web/20130210110921/https://support.twitter.com/articles/109623">security protections</a>, etc), but it still doesn’t change the fact that it feels like we’re continuing to propagate a <a href="https://web.archive.org/web/20130210110921/http://joshua.schachter.org/2009/04/on-url-shorteners.html">very dangerous model</a>. What happens when Pocket goes under, or even if their redirect service is temporarily offline? My post on Google+ is now broken with no real remedy. In this case you could try searching for the title of the article, but what if I only shared the link without a rich snippet that included the title?</p> <p>Much has been said about the dangers of these kinds of redirects, but that’s not actually why I decided to post this. What really got my attention was the fact that the Pocket app for Android only seems to use the shortened pocket.co URLs when sharing to Google+ and Twitter. All other apps I tried sharing to (Facebook, Gmail, WordPress, etc) all included the full link. For the first couple, I thought maybe the destination app was quietly following the redirects to expand the URL, but that doesn’t seem to be the case. So the thing I’m left wondering is why does Pocket choose to use the pocket.co shortlinks for some apps and not others? And more importantly, <strong>how</strong> is it able to do so? I was always under the impression that the OS itself handles delivery of the ACTION_SEND intent, and that the app doesn’t necessarily know where the shared content is going. Is that not the case?</p> </div><!-- .entry-content --> <footer class="entry-meta"> Posted on <a href="https://web.archive.org/web/20130210110921/https://willnorris.com/2012/12/the-links-we-lost" title="2:46 pm" rel="bookmark"><time class="entry-date" datetime="2012-12-14T14:46:33+00:00" pubdate>December 14, 2012</time></a><span class="byline"> by <span class="author vcard"><a class="url fn n" href="https://web.archive.org/web/20130210110921/https://willnorris.com/author/willnorris" title="View all posts by Will Norris" rel="author">Will Norris</a></span></span>. <span class="cat-links"> Posted in <a href="https://web.archive.org/web/20130210110921/https://willnorris.com/category/technology" title="View all posts in technology" rel="category tag">technology</a> </span> <span class="sep"> | </span> <span class="tags-links"> Tagged <a href="https://web.archive.org/web/20130210110921/https://willnorris.com/tag/pocket" rel="tag">pocket</a>, <a href="https://web.archive.org/web/20130210110921/https://willnorris.com/tag/shortlinks" rel="tag">shortlinks</a> </span> </footer><!-- .entry-meta --> </article><!-- #post-982 --> <article id="post-968" class="post-968 post type-post status-publish format-standard hentry category-technology"> <header class="entry-header"> <h1 class="entry-title"><a href="https://web.archive.org/web/20130210110921/https://willnorris.com/2012/06/indie-two-factor-auth" title="Permalink to indie two-factor auth" rel="bookmark">indie two-factor auth</a></h1> </header><!-- .entry-header --> <div class="entry-content"> <p>I was noting to <a href="https://web.archive.org/web/20130210110921/http://tantek.com/">Tantek Çelik</a> this week while we were at <a href="https://web.archive.org/web/20130210110921/http://personaldemocracy.com/conference">#pdf2012</a> that as I’ve been moving to Google alternatives to various services (namely Dropbox to Google Drive), I’m reminded that my Google account is one of the most secure accounts I have anywhere. It ranks up there with my bank, Paypal, Facebook, and (somewhat ironically) World of Warcraft, as one of the few accounts that have <a href="https://web.archive.org/web/20130210110921/http://goo.gl/SOHzX">multi-factor authentication</a>.</p> <p>But what’s the #indieweb version of multi-factor authentication? I want to power my own OpenID, but I want it to be as secure as possible. Is it at all practical to try and have a more “independent” multi-factor auth? Or is it just best left to the large companies that have the security resources to invest in this? Tantek had the additional idea of an indieweb solution where each deployment was slightly different in some way, making mass attacks far less practical since it would be unique per site.</p> <p>I don’t know enough of the specifics of this problem space… mainly just thinking out loud. Anyone ever tried to setup a more secure auth mechanism on your own?</p> <p>(Of course, the huge caveat also being that all of this is only as secure as the hardware you’re running it on. I’m sure a standard off-the-shelf VPS pales in comparison to the security of Google’s production infrastructure)</p> </div><!-- .entry-content --> <footer class="entry-meta"> Posted on <a href="https://web.archive.org/web/20130210110921/https://willnorris.com/2012/06/indie-two-factor-auth" title="11:26 am" rel="bookmark"><time class="entry-date" datetime="2012-06-13T11:26:41+00:00" pubdate>June 13, 2012</time></a><span class="byline"> by <span class="author vcard"><a class="url fn n" href="https://web.archive.org/web/20130210110921/https://willnorris.com/author/willnorris" title="View all posts by Will Norris" rel="author">Will Norris</a></span></span>. <span class="cat-links"> Posted in <a href="https://web.archive.org/web/20130210110921/https://willnorris.com/category/technology" title="View all posts in technology" rel="category tag">technology</a> </span> </footer><!-- .entry-meta --> </article><!-- #post-968 --> <nav role="navigation" id="nav-below" class="site-navigation paging-navigation"> <h1 class="assistive-text">Post navigation</h1> <div class="nav-previous"><a href="https://web.archive.org/web/20130210110921/https://willnorris.com/page/2"><span class="meta-nav">←</span> Older posts</a></div> </nav><!-- #nav-below --> </div><!-- #content .site-content --> </div><!-- #primary .content-area --> <div id="secondary" class="widget-area" role="complementary"> <aside id="search-5" class="widget widget_search"> <form method="get" id="searchform" action="https://web.archive.org/web/20130210110921/https://willnorris.com/" role="search"> <label for="s" class="assistive-text">Search</label> <input type="text" class="field" name="s" value="" id="s" placeholder="Search …"/> <input type="submit" class="submit" name="submit" id="searchsubmit" value="Search"/> </form> </aside> </div><!-- #secondary .widget-area --> </div><!-- #main .site-main --> <footer id="colophon" class="site-footer" role="contentinfo"> <div class="site-info"> </div><!-- .site-info --> </footer><!-- #colophon .site-footer --> </div><!-- #page .hfeed .site --> <script> (function() { jQuery('<script>', {async:true, src:'https://web.archive.org/web/20130210110921/https://apis.google.com/js/plusone.js'}).prependTo('script:first'); })(); </script> <div style="display:none"> </div> <script type="text/javascript" src="https://web.archive.org/web/20130210110921js_/https://willnorris.com/content/plugins/jetpack/modules/shortcodes/js/jquery.cycle.js?ver=2.9999.8"></script> <script type="text/javascript"> /* <![CDATA[ */ var jetpackSlideshowSettings = {"spinner":"https:\/\/web.archive.org\/web\/20130210110921\/https:\/\/willnorris.com\/content\/plugins\/jetpack\/modules\/shortcodes\/img\/slideshow-loader.gif"}; /* ]]> */ </script> <script type="text/javascript" src="https://web.archive.org/web/20130210110921js_/https://willnorris.com/content/plugins/jetpack/modules/shortcodes/js/slideshow-shortcode.js?ver=20121214.1"></script> <script type="text/javascript" src="https://web.archive.org/web/20130210110921js_/https://willnorris.com/content/plugins/jetpack/modules/photon/photon.js?ver=20130122"></script> <script type="text/javascript" src="https://web.archive.org/web/20130210110921js_/https://s0.wp.com/wp-content/js/devicepx-jetpack.js?ver=201306"></script> <script type="text/javascript" src="https://web.archive.org/web/20130210110921js_/https://secure.gravatar.com/js/gprofiles.js?ver=2013Febaa"></script> <script type="text/javascript"> /* <![CDATA[ */ var WPGroHo = {"my_hash":""}; /* ]]> */ </script> <script type="text/javascript" src="https://web.archive.org/web/20130210110921js_/https://willnorris.com/content/plugins/jetpack/modules/wpgroho.js?ver=3.6-alpha-23334"></script> <script type="text/javascript" src="https://web.archive.org/web/20130210110921js_/https://willnorris.com/content/themes/publish/js/small-menu.js?ver=20120206"></script> <script src="https://web.archive.org/web/20130210110921js_/https://stats.wordpress.com/e-201306.js" type="text/javascript"></script> <script type="text/javascript"> st_go({v:'ext',j:'1:2.1.2',blog:'8657281',post:'0',tz:'-8'}); var load_cmc = function(){linktracker_init(8657281,0,2);}; if ( typeof addLoadEvent != 'undefined' ) addLoadEvent(load_cmc); else load_cmc(); </script> </body> </html> <!-- FILE ARCHIVED ON 11:09:21 Feb 10, 2013 AND RETRIEVED FROM THE INTERNET ARCHIVE ON 01:10:46 Nov 30, 2024. JAVASCRIPT APPENDED BY WAYBACK MACHINE, COPYRIGHT INTERNET ARCHIVE. ALL OTHER CONTENT MAY ALSO BE PROTECTED BY COPYRIGHT (17 U.S.C. SECTION 108(a)(3)). --> <!-- playback timings (ms): captures_list: 0.628 exclusion.robots: 0.028 exclusion.robots.policy: 0.016 esindex: 0.01 cdx.remote: 25.016 LoadShardBlock: 5258.617 (6) PetaboxLoader3.datanode: 5285.94 (7) load_resource: 253.991 PetaboxLoader3.resolve: 160.719 -->