<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>everything flows &#187; web and tech</title>
	<atom:link href="http://www.lukerodgers.ca/category/web-tech/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lukerodgers.ca</link>
	<description>a celestial emporium of benevolent knowledge</description>
	<lastBuildDate>Wed, 11 Jan 2012 02:35:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>HTTP status cats</title>
		<link>http://www.lukerodgers.ca/2011/12/http-status-cats/</link>
		<comments>http://www.lukerodgers.ca/2011/12/http-status-cats/#comments</comments>
		<pubDate>Wed, 14 Dec 2011 17:19:35 +0000</pubDate>
		<dc:creator>Luke Rodgers</dc:creator>
				<category><![CDATA[fabulous and random things]]></category>
		<category><![CDATA[web and tech]]></category>

		<guid isPermaLink="false">http://www.lukerodgers.ca/?p=776</guid>
		<description><![CDATA[From Felix Rieseberg, HTTP Status-Katzen.
]]></description>
			<content:encoded><![CDATA[<p>From Felix Rieseberg, <a href="http://www.felixrieseberg.com/deutsch/2011/12/http-status-katzen/"><abbr title="HyperText Transfer Protocol">HTTP</abbr> Status-Katzen</a>.</p>
<p><a href="http://www.lukerodgers.ca/wp-content/uploads/2011/12/6508023065_8dae48a30b.jpg"><img class="alignnone size-full wp-image-777" title="6508023065_8dae48a30b" src="http://www.lukerodgers.ca/wp-content/uploads/2011/12/6508023065_8dae48a30b.jpg" alt="" width="500" height="400" /></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.lukerodgers.ca/2011/12/http-status-cats/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Performance comparison of doubling a number in javascript</title>
		<link>http://www.lukerodgers.ca/2011/10/performance-comparison-of-doubling-a-number-in-javascript/</link>
		<comments>http://www.lukerodgers.ca/2011/10/performance-comparison-of-doubling-a-number-in-javascript/#comments</comments>
		<pubDate>Sat, 08 Oct 2011 20:21:47 +0000</pubDate>
		<dc:creator>Luke Rodgers</dc:creator>
				<category><![CDATA[programming]]></category>
		<category><![CDATA[web and tech]]></category>

		<guid isPermaLink="false">http://www.lukerodgers.ca/?p=772</guid>
		<description><![CDATA[Three ways of doubling, inspired by Will it optimize?
Opera 10.6.3 failed to run the tests.]]></description>
			<content:encoded><![CDATA[<p><a href="http://jsperf.com/three-ways-of-doubling">Three ways of doubling</a>, inspired by <a href="http://ridiculousfish.com/blog/posts/will-it-optimize.html">Will it optimize?</a></p>
<p>Opera 10.6.3 failed to run the tests.</p>]]></content:encoded>
			<wfw:commentRss>http://www.lukerodgers.ca/2011/10/performance-comparison-of-doubling-a-number-in-javascript/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bug in ckeditor version 3.6.1 revision 7072</title>
		<link>http://www.lukerodgers.ca/2011/07/bug-in-ckeditor-version-3-6-1-revision-7072/</link>
		<comments>http://www.lukerodgers.ca/2011/07/bug-in-ckeditor-version-3-6-1-revision-7072/#comments</comments>
		<pubDate>Fri, 15 Jul 2011 20:51:02 +0000</pubDate>
		<dc:creator>Luke Rodgers</dc:creator>
				<category><![CDATA[annoying things]]></category>
		<category><![CDATA[web and tech]]></category>

		<guid isPermaLink="false">http://www.lukerodgers.ca/?p=769</guid>
		<description><![CDATA[Using ckeditor and jquery adapter, and with a textarea that is initialized as a ckeditor instance more than once, once with content, once without, you may encounter a bug in Firefox, p is null.
Go to line 126, change
p.setHtml('');
to
if (p) { (&#8230;)</p><p><a href="http://www.lukerodgers.ca/2011/07/bug-in-ckeditor-version-3-6-1-revision-7072/">Read the rest of this entry &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<p>Using ckeditor and jquery adapter, and with a textarea that is initialized as a ckeditor instance more than once, once with content, once without, you may encounter a bug in Firefox, p is null.</p>
<p>Go to line 126, change</p>
<p><code>p.setHtml('');</code></p>
<p>to</p>
<p><code>if (p) { p.setHtml(''); }</code></p>]]></content:encoded>
			<wfw:commentRss>http://www.lukerodgers.ca/2011/07/bug-in-ckeditor-version-3-6-1-revision-7072/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How does your website fare on text resize?</title>
		<link>http://www.lukerodgers.ca/2010/08/how-does-your-website-fare-on-text-resize/</link>
		<comments>http://www.lukerodgers.ca/2010/08/how-does-your-website-fare-on-text-resize/#comments</comments>
		<pubDate>Sun, 29 Aug 2010 03:04:45 +0000</pubDate>
		<dc:creator>Luke Rodgers</dc:creator>
				<category><![CDATA[web and tech]]></category>
		<category><![CDATA[web development]]></category>

		<guid isPermaLink="false">http://www.lukerodgers.ca/?p=729</guid>
		<description><![CDATA[In the age of page zoom being the default way browsers allow users to increase the size of content on a webpage (standard on most browsers for a while, and on IE since version 7), it can be easy to (&#8230;)</p><p><a href="http://www.lukerodgers.ca/2010/08/how-does-your-website-fare-on-text-resize/">Read the rest of this entry &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<p>In the age of page zoom being the default way browsers allow users to increase the size of content on a webpage (standard on most browsers for a while, and on <abbr title="Internet Explorer">IE</abbr> since version 7), it can be easy to lump in users who resize text with those using <abbr title="Internet Explorer 6">IE6</abbr>, and unwittingly subject the former to your disregard for <abbr title="Internet Explorer 6">IE6</abbr>.<span id="more-729"></span>In case you needed a reminder that this is a bad idea, consider a scenario I was unaware of until recently. On Windows (and presumably with other operating systems, though a quick glance at the Universal Access panel on my mac suggests that zoom is, again, the default and perhaps only possible behaviour), users can increase the default size of the system fonts from the &#8220;normal&#8221; settings of 96 DPI to the &#8220;large&#8221; setting of 120 DPI (and also, seemingly, other custom values). This seems to be roughly equivalent to twice increasing the font size via Firefox&#8217;s &#8216;Zoom Text Only&#8217; option.</p>
<p>While Firefox ignores this <abbr title="Operating System">OS</abbr>-level increase, and will leave the font settings you, as a web developer, have so carefully crafted, IE7 (and later versions? I wasn&#8217;t able to test this) maintains the increased font size, wreaking havoc on your layout if you&#8217;ve been cavalier enough to count on users zooming rather than resizing.</p>]]></content:encoded>
			<wfw:commentRss>http://www.lukerodgers.ca/2010/08/how-does-your-website-fare-on-text-resize/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Testing your websites on Android phones</title>
		<link>http://www.lukerodgers.ca/2010/07/testing-your-websites-on-android-phones/</link>
		<comments>http://www.lukerodgers.ca/2010/07/testing-your-websites-on-android-phones/#comments</comments>
		<pubDate>Sat, 17 Jul 2010 20:50:26 +0000</pubDate>
		<dc:creator>Luke Rodgers</dc:creator>
				<category><![CDATA[fabulous and random things]]></category>
		<category><![CDATA[web and tech]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[mobile]]></category>

		<guid isPermaLink="false">http://www.lukerodgers.ca/?p=711</guid>
		<description><![CDATA[Setting up an Android developer environment on your Mac is easy]]></description>
			<content:encoded><![CDATA[<p>Been reading up on web development/design for mobile devices recently, and came across some helpful instructions on <a href="http://themattharris.com/2009/06/testing-websites-on-google-android/">testing websites on Google Android</a>. Turns out it&#8217;s pretty easy, but I thought I&#8217;d write up these instructions for OSX since the steps seem to have changed a bit since the above article was written. <span id="more-711"></span>You will need <a href="http://java.sun.com/javase/downloads/index.jsp"><abbr title="Java Development Kit">JDK</abbr></a> 1.5 or higher to begin. Type &#8220;java -version&#8221; into your Terminal (Applications &#8211;&gt; Utilities &#8211;&gt; Terminal.app) to see what version you have.</p>
<p>You will also obviously need the Android <a href="http://developer.android.com/sdk/installing.html"><abbr title="Software Development Kit">SDK</abbr></a>. If you just want to play around with the emulator or test websites, ignore the stuff on the installation instructions about Eclipse or other IDEs. If you meet the system requirements, <a href="http://developer.android.com/sdk/index.html">download the right <abbr title="Software Development Kit">SDK</abbr> version for your computer</a>.</p>
<p>Once it&#8217;s downloaded, unzip it wherever is convenient for you (into a /code or /development directory, or just in your home directory).</p>
<p>Next, you will probably want to add the directory where android is to your system PATH. You can see what your path is by typing in your terminal &#8220;echo $PATH&#8221;. You will want to go to your home directory /Users/&lt;yourloginname&gt; and edit your .profile file. If it already has something that looks like this:</p>
<p><code>export PATH=/opt/local/bin:$PATH</code></p>
<p>Then just add the android directory onto the end like so:</p>
<p><code>export PATH=/opt/local/bin:$PATH:/Users/&lt;yourusername&gt;/android-sdk-mac_86/tools</code></p>
<p>When that&#8217;s done, close Terminal.app, restart it and type &#8220;android.&#8221; This will start the <abbr title="Software Development Kit">SDK</abbr> and AVD (Android Virtual Device) Manager. You will not have any virtual devices downloaded/installed yet, so that will be your first step.</p>
<p>Click on &#8220;Available Packages&#8221; on the menu on the left side, and you will get a list of SDKs to download.</p>
<p><a href="http://www.lukerodgers.ca/wp-content/uploads/2010/07/Picture-1.png"><img class="alignnone size-medium wp-image-713" title="Picture 1" src="http://www.lukerodgers.ca/wp-content/uploads/2010/07/Picture-1-300x173.png" alt="" width="300" height="173" /></a></p>
<p>Check the box next to the latest one (in this case, <abbr title="Software Development Kit">SDK</abbr> Platform Android 2.2, <abbr title="Application Programming Interface">API</abbr> 8, revision 2). Click &#8220;Install Selected&#8221; then click &#8220;Install&#8221;. The <abbr title="Software Development Kit">SDK</abbr> will probably take a few minutes to download and install.</p>
<p>When it&#8217;s done installing, click on &#8220;Virtual Devices&#8221; then click the button &#8220;New&#8221; to create a new virtual device. Call it something like android2.2HVGA for the <abbr title="Software Development Kit">SDK</abbr> and screen resolution (HVGA is for Half VGA). The size of the SD card doesn&#8217;t matter much for our purposes here, but it must be at least 9 <abbr title="Megabyte">MB</abbr>. There are other configuration options you can tweak, but again we don&#8217;t need to worry about them now. If you want, you can change the skin to WVGA 800 or 854, which are common on the latest generation of Android phones.</p>
<p>Click the button to create the AVD, then select it from the Virtual Devices manager and click &#8220;Start&#8230;&#8221;, leaving the options at their default before you click &#8220;Launch&#8221;.</p>
<p>It will take anywhere from 30 seconds to a couple minutes to start (takes me a couple minutes on a MBP 2.53 ghz core 2 duo), during which you will see the following screens:</p>
<p><a href="http://www.lukerodgers.ca/wp-content/uploads/2010/07/Picture-3.png"><img class="alignnone size-medium wp-image-714" title="Picture 3" src="http://www.lukerodgers.ca/wp-content/uploads/2010/07/Picture-3-300x208.png" alt="" width="300" height="208" /></a></p>
<p><a href="http://www.lukerodgers.ca/wp-content/uploads/2010/07/Picture-4.png"><img class="alignnone size-medium wp-image-715" title="Picture 4" src="http://www.lukerodgers.ca/wp-content/uploads/2010/07/Picture-4-300x211.png" alt="" width="300" height="211" /></a></p>
<p>Eventually, you&#8217;ll see the home screen and you&#8217;re ready to go.</p>
<p><a href="http://www.lukerodgers.ca/wp-content/uploads/2010/07/Picture-5.png"><img class="alignnone size-medium wp-image-716" title="Picture 5" src="http://www.lukerodgers.ca/wp-content/uploads/2010/07/Picture-5-300x209.png" alt="" width="300" height="209" /></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.lukerodgers.ca/2010/07/testing-your-websites-on-android-phones/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Two interesting fonts</title>
		<link>http://www.lukerodgers.ca/2010/07/two-interesting-fonts/</link>
		<comments>http://www.lukerodgers.ca/2010/07/two-interesting-fonts/#comments</comments>
		<pubDate>Fri, 09 Jul 2010 03:09:15 +0000</pubDate>
		<dc:creator>Luke Rodgers</dc:creator>
				<category><![CDATA[fabulous and random things]]></category>
		<category><![CDATA[things about which I am not ambivalent]]></category>
		<category><![CDATA[web and tech]]></category>
		<category><![CDATA[typography]]></category>

		<guid isPermaLink="false">http://www.lukerodgers.ca/?p=707</guid>
		<description><![CDATA[Whimsical and retro]]></description>
			<content:encoded><![CDATA[<p>Typography is somewhere between a passing interest and a form of professional dilettantism. I like the <a href="http://www.myfonts.com">Myfonts</a> newsletter, the <a href="http://new.myfonts.com/newsletters/rs/201007.html">most recent edition of which</a> highlights a couple particularly outstanding fonts. <span id="more-707"></span>Lady René</p>
<p><a href="http://new.myfonts.com/fonts/sudtipos/lady-rene/"><img class="alignnone size-full wp-image-708" title="41805" src="http://www.lukerodgers.ca/wp-content/uploads/2010/07/41805.jpg" alt="" width="200" height="200" /></a></p>
<p>Vow</p>
<p><a href="http://new.myfonts.com/fonts/thinkdust/vow/"><img class="alignnone size-medium wp-image-709" title="41867" src="http://www.lukerodgers.ca/wp-content/uploads/2010/07/41867-300x150.png" alt="" width="300" height="150" /></a></p>
<p>Vow also has extended glyph and European character support. Too bad I&#8217;m too poor to pay the (eminently reasonable) ~$50 for each one <img src='http://www.lukerodgers.ca/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>]]></content:encoded>
			<wfw:commentRss>http://www.lukerodgers.ca/2010/07/two-interesting-fonts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Updated RSS feeds</title>
		<link>http://www.lukerodgers.ca/2010/07/updated-rss-feeds/</link>
		<comments>http://www.lukerodgers.ca/2010/07/updated-rss-feeds/#comments</comments>
		<pubDate>Mon, 05 Jul 2010 20:46:25 +0000</pubDate>
		<dc:creator>Luke Rodgers</dc:creator>
				<category><![CDATA[web and tech]]></category>

		<guid isPermaLink="false">http://www.lukerodgers.ca/?p=704</guid>
		<description><![CDATA[Which ones made the cut? so exciting]]></description>
			<content:encoded><![CDATA[<p>I&#8217;d been using Google reader pretty heavily for a few years, then abandoned it pretty heavily since I began school last fall. Now that I&#8217;m getting back to it, I&#8217;ve culled my list pretty ruthlessly.  Here are (most) of the ones I kept:</p>
<p><span id="more-704"></span></p>
<ul>
<li><a href="http://www.456bereastreet.com/">456 Berea Street</a></li>
<li><a href="http://adactio.com/articles/">Adactio</a></li>
<li><a href="http://www.adaptivepath.com/blog/">Adaptive Path</a></li>
<li>Cameron Moll&#8217;s <a href="http://www.cameronmoll.com/">Authentic Boredom</a></li>
<li><a href="http://bokardo.com/">Bokardo </a></li>
<li><a href="http://www.boxesandarrows.com/">Boxes and Arrows</a></li>
<li>Dave Shea&#8217;s <a href="http://www.mezzoblue.com/">Mezzoblue</a></li>
<li><a href="http://factoryjoe.com/blog/">FactoryCity</a></li>
<li><a href="http://typography.com/ask/">Hoefler &amp; Frere-Jones</a></li>
<li><a href="http://nicewebtype.com/">Nice Web Type</a></li>
<li><a href="http://noisebetweenstations.com/personal/weblogs/">Noise Between Stations</a></li>
<li><a href="http://www.phpied.com/">phpied</a></li>
<li><a href="http://37signals.com/svn/">Signal vs. Noise</a></li>
<li><a href="http://stream.simplebits.com/">Simplebits</a></li>
<li><a href="http://snook.ca/">Snook.ca</a></li>
<li><a href="http://stopdesign.com/">StopDesign</a></li>
<li><a href="http://tantek.com/">Tantek&#8217;s Updates</a></li>
<li><a href="http://www.paciellogroup.com/blog/">The Paciello Group Blog</a>, which does good work on web accessibility</li>
<li><a href="http://meyerweb.com/">Thoughts from Eric</a> (Meyer)</li>
<li><a href="http://www.uie.com/brainsparks/">UIE Brain Sparks</a></li>
<li><a href="http://unstoppablerobotninja.com/">Unstoppable Robot Ninja</a> (aka Ethan Marcotte)</li>
<li><a href="http://www.uxmatters.com/">UXMatters</a></li>
<li><a href="http://www.web-strategist.com/blog/">Web Strategy by Jeremiah</a></li>
<li><a href="http://wordpress.org/development/">Wordpress Development</a></li>
<li><a href="http://jontangerine.com/">Jon Tan</a></li>
<li><a href="http://www.zeldman.com/">Zeldman.com</a></li>
</ul>
<p>Got rid of Smashing Magazine, which suffers from a poor signal:noise ratio, and Surfin&#8217; Safari, which was mostly just Webkit reviewer notifications. Dropped a few others that basically just re-posted their tweets and/or too frequently mixed in ill-informed political opinion.</p>]]></content:encoded>
			<wfw:commentRss>http://www.lukerodgers.ca/2010/07/updated-rss-feeds/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Paragraph-level commenting for Wordpress</title>
		<link>http://www.lukerodgers.ca/2009/08/paragraph-level-commenting-for-wordpress/</link>
		<comments>http://www.lukerodgers.ca/2009/08/paragraph-level-commenting-for-wordpress/#comments</comments>
		<pubDate>Tue, 25 Aug 2009 00:15:17 +0000</pubDate>
		<dc:creator>Luke Rodgers</dc:creator>
				<category><![CDATA[things about which I am not ambivalent]]></category>
		<category><![CDATA[web and tech]]></category>
		<category><![CDATA[social media]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://www.lukerodgers.ca/?p=610</guid>
		<description><![CDATA[Digress.it is a Wordpress plugin enabling threaded, paragraph-specific discussion on posts and pages]]></description>
			<content:encoded><![CDATA[<p>The team from the <a href="http://www.futureofthebook.org/">Institute for the Future of the Book</a> team have announced the release of <a href="http://digress.it/">digress.it</a>, a completely overhauled version of the old Commentpress theme for Wordpress, which allowed paragraph-level commenting. Digress.it is a plugin which<span id="more-610"></span></p>
<blockquote><p>offers paragraph-level commenting in the margins of a text. digress.it is based on the architecture of weblogs, but is geared toward in-depth discussions of longer documents: article, essay or even book-length. With digress.it, you can annotate, gloss, workshop and debate on a fine-grained level, turning a document into a conversation.</p></blockquote>
<p>I worked on the old Commentpress platform to get it running in English and French, and contributed some minor bug fixes, and really liked the idea behind the project, so this is an exciting development to see. I haven&#8217;t explored the plugin yet, but hopefully it will make the functionality much easier to integrate into an existing Wordpress installation.</p>]]></content:encoded>
			<wfw:commentRss>http://www.lukerodgers.ca/2009/08/paragraph-level-commenting-for-wordpress/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Facebook uses browser-specific body classes</title>
		<link>http://www.lukerodgers.ca/2009/08/facebook-uses-browser-specific-body-classes/</link>
		<comments>http://www.lukerodgers.ca/2009/08/facebook-uses-browser-specific-body-classes/#comments</comments>
		<pubDate>Thu, 20 Aug 2009 04:00:53 +0000</pubDate>
		<dc:creator>Luke Rodgers</dc:creator>
				<category><![CDATA[web and tech]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[html]]></category>

		<guid isPermaLink="false">http://www.lukerodgers.ca/?p=607</guid>
		<description><![CDATA[Use browser-specific body classes to avoid extra stylesheets or invalid CSS]]></description>
			<content:encoded><![CDATA[<p>Having recently worked on a website for which page load and performance was really important, I&#8217;ve found myself viewing the source code for more and more sites. Taking a look at Facebook recently revealed that they use browser-specific classes on the body element, so that if you&#8217;re browsing with Safari 4, you&#8217;ll see something like:<span id="more-607"></span></p>
<p><code class="block">&lt;body class="home safari4 Locale_en_GB chat_body"&gt;</code></p>
<p>If you&#8217;re already browser sniffing, this might be a better idea for applying targeted <abbr title="Cascading Style Sheets">CSS</abbr> rules than including an extra stylesheet with conditional comments (which means an extra <abbr title="HyperText Transfer Protocol">HTTP</abbr> request), or using the underscore hack (<abbr title="Internet Explorer 6">IE6</abbr>), or star hack (IE7) which cause invalid <abbr title="Cascading Style Sheets">CSS</abbr>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.lukerodgers.ca/2009/08/facebook-uses-browser-specific-body-classes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google doesn&#8217;t like twitter</title>
		<link>http://www.lukerodgers.ca/2009/08/google-doesnt-like-twitter/</link>
		<comments>http://www.lukerodgers.ca/2009/08/google-doesnt-like-twitter/#comments</comments>
		<pubDate>Fri, 14 Aug 2009 00:21:38 +0000</pubDate>
		<dc:creator>Luke Rodgers</dc:creator>
				<category><![CDATA[unpredictable things]]></category>
		<category><![CDATA[web and tech]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://www.lukerodgers.ca/?p=604</guid>
		<description><![CDATA[Can't really blame them]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.lukerodgers.ca/wp-content/uploads/2009/08/Picture-2.png"><img class="alignnone size-medium wp-image-605" title="Picture 2" src="http://www.lukerodgers.ca/wp-content/uploads/2009/08/Picture-2-300x218.png" alt="Picture 2" width="300" height="218" /></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.lukerodgers.ca/2009/08/google-doesnt-like-twitter/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

