<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: The Whirring Sound of GMT+0</title>
	<atom:link href="http://www.bytesurgery.com/blog/2008/04/24/the-whirring-sound-of-gmt0/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bytesurgery.com/blog/2008/04/24/the-whirring-sound-of-gmt0/</link>
	<description>Digital Media Engineering</description>
	<pubDate>Thu, 04 Dec 2008 19:21:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Robert Synnott</title>
		<link>http://www.bytesurgery.com/blog/2008/04/24/the-whirring-sound-of-gmt0/#comment-21367</link>
		<dc:creator>Robert Synnott</dc:creator>
		<pubDate>Thu, 24 Apr 2008 11:03:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytesurgery.com/blog/?p=357#comment-21367</guid>
		<description>Actually, Google Reader gets Blogger and Feedburner-ed posts pretty much instantly now.</description>
		<content:encoded><![CDATA[<p>Actually, Google Reader gets Blogger and Feedburner-ed posts pretty much instantly now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eoghan McCabe</title>
		<link>http://www.bytesurgery.com/blog/2008/04/24/the-whirring-sound-of-gmt0/#comment-21366</link>
		<dc:creator>Eoghan McCabe</dc:creator>
		<pubDate>Thu, 24 Apr 2008 09:27:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytesurgery.com/blog/?p=357#comment-21366</guid>
		<description>I think the argument for posting early is quite straight-forward:

* The older the post, the less likely people are to interact with it (leave a comment, write a post about it, add it to social bookmarking site, e-mail it). Obviously, this is a generalisation, but often a post it most relevant at the moment it's published.
* Given this, you want people to see it as close to the publish time as possible. A lot of folks will do their reading first thing in the morning (the spike here for my reading is at 10am: http://skitch.com/eoghanmccabe/krs2/google-reader-1000, the spike for a sample from contrast.ie is at 10am: http://skitch.com/eoghanmccabe/krs9/visits-for-all-visitors-google-analytics), so if your post is not ready by then, you have to wait another 24 hours for them to see it, by which time they are less likely to interact.

I post at about 7am which I've guessed is the latest time I can publish while still getting most (you can see in the Analytics picture, traffic starts to build after 7am) morning readers in GMT+0.

But what to do if you've a perfectly geographically-distributed reader-base?</description>
		<content:encoded><![CDATA[<p>I think the argument for posting early is quite straight-forward:</p>
<p>* The older the post, the less likely people are to interact with it (leave a comment, write a post about it, add it to social bookmarking site, e-mail it). Obviously, this is a generalisation, but often a post it most relevant at the moment it&#8217;s published.<br />
* Given this, you want people to see it as close to the publish time as possible. A lot of folks will do their reading first thing in the morning (the spike here for my reading is at 10am: <a href="http://skitch.com/eoghanmccabe/krs2/google-reader-1000" rel="nofollow">http://skitch.com/eoghanmccabe/krs2/google-reader-1000</a>, the spike for a sample from contrast.ie is at 10am: <a href="http://skitch.com/eoghanmccabe/krs9/visits-for-all-visitors-google-analytics" rel="nofollow">http://skitch.com/eoghanmccabe/krs9/visits-for-all-visitors-google-analytics</a>), so if your post is not ready by then, you have to wait another 24 hours for them to see it, by which time they are less likely to interact.</p>
<p>I post at about 7am which I&#8217;ve guessed is the latest time I can publish while still getting most (you can see in the Analytics picture, traffic starts to build after 7am) morning readers in GMT+0.</p>
<p>But what to do if you&#8217;ve a perfectly geographically-distributed reader-base?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
