<?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>Nick Heer &#187; Twitter</title>
	<atom:link href="http://nickheer.com/tag/twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://nickheer.com</link>
	<description></description>
	<lastBuildDate>Mon, 21 May 2012 19:45:47 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>&#9673; Display Your Latest Tweet With PHP</title>
		<link>http://nickheer.com/blog/display-latest-tweet-with-php/</link>
		<comments>http://nickheer.com/blog/display-latest-tweet-with-php/#comments</comments>
		<pubDate>Sat, 01 Aug 2009 03:43:45 +0000</pubDate>
		<dc:creator>Nick</dc:creator>
				<category><![CDATA[Article]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Twitter]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://nickheer.com/?p=585</guid>
		<description><![CDATA[I get asked, literally some times every so often, the best way to integrate your latest tweet into Wordpress. The beauty of this code is that it replaces common symbols with their appropriate equivalents, and it parses links perfectly.]]></description>
			<content:encoded><![CDATA[<p>I get asked, literally some times every so often, the best way to integrate your latest tweet into WordPress. There are a few ways of doing this, but the way I&#8217;ve come up with is, I think, pretty nifty.</p>

<p>The first way is using Twitter&#8217;s <a href="http://twitter.com/goodies/widget_profile">profile widget creator</a>, which displays tweets in a little box which you can change the colours and dimensions of. It&#8217;s actually not bad, but it&#8217;s a bit generic. It looks the same, despite colour differences, on everyone&#8217;s website, and it probably wouldn&#8217;t work with a site design similar to mine.</p>

<p>The next solution is using one of Twitter&#8217;s <a href="http://twitter.com/widgets/which_widget">other widgets</a>, which are hidden a little on the Twitter site (you need to go into Applications on the Twitter goodies page, not Widgets &mdash; it&#8217;s linked above for your convenience, though). You can choose between a Flash or HTML widget. The Flash version is similar to the previous widget, in that it looks pretty much the same everywhere, despite colour options. The HTML one is much, much better though. It allows for simple, easy CSS styling. I liked this method so much that I used it on the previous version of nickheer.com</p>

<p>The problem with the HTML widget is that, for whatever reason, it doesn&#8217;t seem to work smoothly 100% of the time. I think it&#8217;s a Javascript/Wordpress/Safari 4 issue, but it doesn&#8217;t matter. In addition, if you want to style it in-depth, it can be a royal pain.</p>

<p>However, I recently found a post on the Smashing Magazine site which described <a href="http://www.smashingmagazine.com/2009/03/04/15-useful-twitter-plugins-and-hacks-for-wordpress/">a method for displaying the latest tweet via PHP</a>. This intrigued me, and I implemented it into this revision of the website, and immediately I ran into a huge problem.</p>

<p>This PHP method seems to get easily confused by symbols (&lt;, &gt; and &amp; all seem to be problematic) and links. Bad news for me, since I seem to tweet links quite often. Note that this also applies to @replies, because the username is linked. After much trial-and-error, I think I&#8217;ve cracked the perfect way to show your latest tweet(s).</p>

<p><em>Update: e-sushi posted a much better version of this in the comments. Thanks for the new code.</em></p>

<p><a href="http://pastie.org/974423">Click here for the UPDATED code</a>.</p>

<p>The beauty of this code is that it replaces common symbols with their appropriate equivalents, and it parses links perfectly. The bulk of the code is from the Smashing Magazine article, but all of the string replacement code is by me. Please don&#8217;t forget to put your Twitter username on line 2.</p>

<p><em>Update (August 2011)</em>: <a href="http://blog.jamesbmarshall.com/2010/03/get-latest-tweet-php-code/">this is another fantastic implementation</a> of a Twitter PHP script. I highly recommend it.</p>
]]></content:encoded>
			<wfw:commentRss>http://nickheer.com/blog/display-latest-tweet-with-php/feed/</wfw:commentRss>
		<slash:comments>18</slash:comments>
		</item>
		<item>
		<title>&#9673; Facebook vs. Twitter</title>
		<link>http://nickheer.com/blog/facebook-vs-twitter/</link>
		<comments>http://nickheer.com/blog/facebook-vs-twitter/#comments</comments>
		<pubDate>Mon, 23 Mar 2009 19:14:41 +0000</pubDate>
		<dc:creator>Nick</dc:creator>
				<category><![CDATA[Article]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[networking]]></category>
		<category><![CDATA[Twitter]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://nickheer.com/?p=547</guid>
		<description><![CDATA[Facebook content for the most part consists of secondary information about what you're doing on Facebook. Its the ripples in the pool as you move around. Twitter content IS what you're doing. Twitter is the actual swimming - you have to take the strokes. This distinction is important because intentional content creation has to be sustained. Secondary content creation is a side affect and just happens.]]></description>
			<content:encoded><![CDATA[<blockquote>Speaking of Twitter initiatives, Facebook did a major redesign recently and the thing looks like Twitter now. Far be it from me to criticize other people&#8217;s site redesigns (my official stance with any redesign is &#8220;you&#8217;ll get over it&#8221;), but it seems strange to me that a site with 175 million users is so scared of a site with 6 million that it destroys what made Facebook unique to become an imperfect copy of Twitter.

Twitter content is actively updated. You say to yourself &#8220;I haven&#8217;t told everyone what kind of cream cheese I ate on my bagel today&#8221;, and you update your Twitter status so everyone knows. Facebook content on the other hand is secondary activity created when you try to do something like look up old friends, contact people, friend them, confirm party attendance, zombie bite them, whatever (with the exception of status updates, but that&#8217;s only one piece of the functionality). Facebook content for the most part consists of secondary information about what you&#8217;re doing on Facebook. Its the ripples in the pool as you move around. Twitter content IS what you&#8217;re doing. Twitter is the actual swimming &#8211; you have to take the strokes. This distinction is important because intentional content creation has to be sustained. Secondary content creation is a side affect and just happens.

You may have noticed that the vast majority of people don&#8217;t have anything interesting to say. They may eventually get Twitter accounts and they may update but the content sucks and no one cares. Far more people are going to be doing what they&#8217;re doing on Facebook for far longer &#8212; assuming (and this is the important bit) that Facebook doesn&#8217;t fark up and forget what the hell people were on Facebook to do in the first place&#8230; Whoops, too late.</blockquote>

<p>From Drew Curtis, of Fark.com. I think this illustrates Facebook vs. Twitter very nicely, and why Facebook&#8217;s new redesign is a bit weird.</p>
]]></content:encoded>
			<wfw:commentRss>http://nickheer.com/blog/facebook-vs-twitter/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>&#9673; Cross-Posting</title>
		<link>http://nickheer.com/scraps/cross-posting/</link>
		<comments>http://nickheer.com/scraps/cross-posting/#comments</comments>
		<pubDate>Mon, 05 Jan 2009 18:48:15 +0000</pubDate>
		<dc:creator>Nick</dc:creator>
				<category><![CDATA[Scrap]]></category>
		<category><![CDATA[cross]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[internet]]></category>
		<category><![CDATA[referral]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://nickheer.com/?p=440</guid>
		<description><![CDATA[A post from about a month ago on joestump.net is incredibly critical of cross-posting. Mr. Stump disagrees that Twitter can be used for anything except 140-character posts that let him know what the user is doing. I disagree with this viewpoint, mainly after looking at my blog statistics for the first 14 hours of the launch [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.joestump.net/2008/12/cross-posting-is-bad-for-the-internets.html">A post</a> from about a month ago on <a href="http://www.joestump.net/2008/12/cross-posting-is-bad-for-the-internets.html">joestump.net</a> is incredibly critical of cross-posting. Mr. Stump disagrees that Twitter can be used for anything except 140-character posts that let him know what the user is doing. I disagree with this viewpoint, mainly after looking at my blog statistics for the first 14 hours of the launch of the site:</p>

<p><img class="alignnone size-full wp-image-441" title="referrals" src="http://nickheer.com/wp-content/uploads/2009/01/picture-1.png" alt="referrals" width="316" height="307" /></p>

<p>As you can see, the first is from my old blog (which isn&#8217;t cross posting – that&#8217;s just about 40-odd subscribers checking out the new site). My blog feeds to Facebook and to Twitter, and you can see that the second and third referrers were exactly those two.</p>
]]></content:encoded>
			<wfw:commentRss>http://nickheer.com/scraps/cross-posting/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

