<?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>Complex Solutions to Simple Problems&#187; optimizing</title>
	<atom:link href="http://blog.heick.nu/tag/optimizing/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.heick.nu</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Fri, 12 Mar 2010 08:17:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Optimizing urls for Twitter</title>
		<link>http://blog.heick.nu/social-media/optimizing-urls-for-twitter.html</link>
		<comments>http://blog.heick.nu/social-media/optimizing-urls-for-twitter.html#comments</comments>
		<pubDate>Wed, 16 Apr 2008 22:01:23 +0000</pubDate>
		<dc:creator>Pål Heick</dc:creator>
				<category><![CDATA[Social Media]]></category>
		<category><![CDATA[blogging]]></category>
		<category><![CDATA[keywords]]></category>
		<category><![CDATA[optimizing]]></category>
		<category><![CDATA[Social Media Optimization]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://blog.heick.nu/archives/2008/04/optimizing-urls-for-twitter</guid>
		<description><![CDATA[But then again: that&#8217;s a rule of the game  &#8211; and if your aim is to promote semantically rich ...]]></description>
			<content:encoded><![CDATA[<p>But then again: that&#8217;s a rule of the game  &#8211; and if your aim is to promote semantically rich urls in your Twitter-feed, you just better keep them below 30 characters. It&#8217;s hard enough to limit the praising of a given link to 140 characters.</p>
<p>So, what are the more concrete implications of this?<br />
Well, looking at my own permalinks (that have annoyed me for some time now) &#8211; I now have another reason for skipping those non-semantical parts of the permalink: http://blog.heick.nu/archives/2008/04/. That&#8217;s 38 characters right there &#8211; and I can be pretty damn sure that any link from this blog posted on Twitter is going to be tinyurlified&#8230;<br />
Still even if I (when) change my permalinks to the shortest possible form: http://blog.heick.nu/%postname% &#8211; I only have 10 chars to do with.<br />
In any case &#8211; In the future, I might just start shortening my urls to make them Twitter-friendly&#8230;</p>
<p>Is that called Social Media Optimization? SMO?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.heick.nu/social-media/optimizing-urls-for-twitter.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Optimizing</title>
		<link>http://blog.heick.nu/general/optimizing.html</link>
		<comments>http://blog.heick.nu/general/optimizing.html#comments</comments>
		<pubDate>Wed, 09 Jan 2008 10:04:09 +0000</pubDate>
		<dc:creator>Pål Heick</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[optimizing]]></category>

		<guid isPermaLink="false">http://blog.heick.nu/archives/2008/01/optimizing</guid>
		<description><![CDATA[
So, fluffing content isn&#8217;t that hard after all  

Not at all, in fact&#8230;
]]></description>
			<content:encoded><![CDATA[<p><img src="http://farm3.static.flickr.com/2372/2180441994_a4260cb27d_o.jpg" alt="optimizing content" /></p>
<p>So, fluffing content isn&#8217;t that hard after all <img src='http://blog.heick.nu/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p><img src="http://farm3.static.flickr.com/2061/2180464826_f4b92480c6.jpg" alt="Content optimizing part 2" /></p>
<p>Not at all, in fact&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.heick.nu/general/optimizing.html/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
