<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The strange case of Giles Hattersley&#8217;s Wikipedia article</title>
	<atom:link href="http://www.qwghlm.co.uk/2009/02/08/the-strange-case-of-giles-hattersleys-wikipedia-article/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.qwghlm.co.uk/2009/02/08/the-strange-case-of-giles-hattersleys-wikipedia-article/</link>
	<description>Because all the other domain names were taken</description>
	<lastBuildDate>Sat, 24 Jul 2010 11:45:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Fluffy Links - Tuesday 10th February 2009 &#171; Damien Mulley</title>
		<link>http://www.qwghlm.co.uk/2009/02/08/the-strange-case-of-giles-hattersleys-wikipedia-article/comment-page-1/#comment-3247</link>
		<dc:creator>Fluffy Links - Tuesday 10th February 2009 &#171; Damien Mulley</dc:creator>
		<pubDate>Tue, 10 Feb 2009 05:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.qwghlm.co.uk/blog/?p=1213#comment-3247</guid>
		<description>[...] Times journo writes scatching article on Wikipedia page about him. Except. There never was a page. [...]</description>
		<content:encoded><![CDATA[<p>[...] Times journo writes scatching article on Wikipedia page about him. Except. There never was a page. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.qwghlm.co.uk/2009/02/08/the-strange-case-of-giles-hattersleys-wikipedia-article/comment-page-1/#comment-3245</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Mon, 09 Feb 2009 07:55:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.qwghlm.co.uk/blog/?p=1213#comment-3245</guid>
		<description>It&#039;s worth noting that &lt;a href=&quot;http://en.wikipedia.org/wiki/Talk:Giles_Hattersley#Roy_Hattersley&quot; rel=&quot;nofollow&quot;&gt;no-one can find the offending error anywhere&lt;/a&gt; on Wikipedia, including Roy Hattersley&#039;s article. Furthermore, it would have to be a truly appalling piece of subbing to willingly edit an accusation of libel against someone without checking with the author.

This doesn&#039;t exactly reflect better on Hattersley&#039;s journalism skills either. He states: &lt;i&gt;&quot;The mistake pointed out in the piece, was pointed out to me a year or two ago in some corresponding page where my name cropped up - either Roy Hattersley&#039;s entry, or a third party&#039;s page. I&#039;m glad to hear it no longer exists!&quot;&lt;/i&gt; - it shows he was relying on hearsay, and failed to do even the most basic research to see whether it was true. If he had, he would have found out Wikipedia&#039;s ability to self-correct itself so quickly is actually a good thing, but that wouldn&#039;t have fitted into the narrative of his article.

Speaking of which, while Wikipedia has now sorted this affair out (with not inconsiderable fuss), the original piece on the Times website remains unchanged.</description>
		<content:encoded><![CDATA[<p>It&#8217;s worth noting that <a href="http://en.wikipedia.org/wiki/Talk:Giles_Hattersley#Roy_Hattersley" rel="nofollow">no-one can find the offending error anywhere</a> on Wikipedia, including Roy Hattersley&#8217;s article. Furthermore, it would have to be a truly appalling piece of subbing to willingly edit an accusation of libel against someone without checking with the author.</p>
<p>This doesn&#8217;t exactly reflect better on Hattersley&#8217;s journalism skills either. He states: <i>&#8220;The mistake pointed out in the piece, was pointed out to me a year or two ago in some corresponding page where my name cropped up &#8211; either Roy Hattersley&#8217;s entry, or a third party&#8217;s page. I&#8217;m glad to hear it no longer exists!&#8221;</i> &#8211; it shows he was relying on hearsay, and failed to do even the most basic research to see whether it was true. If he had, he would have found out Wikipedia&#8217;s ability to self-correct itself so quickly is actually a good thing, but that wouldn&#8217;t have fitted into the narrative of his article.</p>
<p>Speaking of which, while Wikipedia has now sorted this affair out (with not inconsiderable fuss), the original piece on the Times website remains unchanged.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.qwghlm.co.uk/2009/02/08/the-strange-case-of-giles-hattersleys-wikipedia-article/comment-page-1/#comment-3244</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Mon, 09 Feb 2009 01:07:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.qwghlm.co.uk/blog/?p=1213#comment-3244</guid>
		<description>I&#039;m a bit surprised at how lots of people&#039;s reactions to the initial false claim seem to have been approximately in the &quot;so what?&quot; camp. It may be just weariness on the part of Wikipedia&#039;s defenders, having seen it before, but it still feels like selling themselves a bit short - unnecessarily ceding the ground that Wikipedia will always have flatly untrue things written about it. If the claim had instead been, for example, that a rival newspaper had published an erroneous, libellous article about him - when no such article had ever been published - I can&#039;t see people shrugging it off as just one of those things. I feel there would likely have been a good deal more anger; lawyers would surely have been invoked.

(It&#039;s worth noting that, seemingly, Hattersley &lt;a href=&quot;http://en.wikipedia.org/wiki/Talk:Giles_Hattersley#A_message_from_Giles_Hattersley&quot; rel=&quot;nofollow&quot;&gt;is now claiming the error was as a result of sub-editing&lt;/a&gt;. That&#039;s certainly plausible; you can see how it could have happened, although it would be a truly dreadful bit of subbing, deserving of a full Giles Coren. Regardless, it&#039;s hardly against WP policy to assume that words published under someone&#039;s name are indeed their own words, at least until contrary evidence emerges.)

Of course, Wales has now ensured that the issue everyone will be talking about instead is his apparent belief that Wikipedia&#039;s overriding policy is the little-known &quot;WP:Make Jimmy Wales&#039; Life Easier&quot;. So, hey ho.</description>
		<content:encoded><![CDATA[<p>I&#8217;m a bit surprised at how lots of people&#8217;s reactions to the initial false claim seem to have been approximately in the &#8220;so what?&#8221; camp. It may be just weariness on the part of Wikipedia&#8217;s defenders, having seen it before, but it still feels like selling themselves a bit short &#8211; unnecessarily ceding the ground that Wikipedia will always have flatly untrue things written about it. If the claim had instead been, for example, that a rival newspaper had published an erroneous, libellous article about him &#8211; when no such article had ever been published &#8211; I can&#8217;t see people shrugging it off as just one of those things. I feel there would likely have been a good deal more anger; lawyers would surely have been invoked.</p>
<p>(It&#8217;s worth noting that, seemingly, Hattersley <a href="http://en.wikipedia.org/wiki/Talk:Giles_Hattersley#A_message_from_Giles_Hattersley" rel="nofollow">is now claiming the error was as a result of sub-editing</a>. That&#8217;s certainly plausible; you can see how it could have happened, although it would be a truly dreadful bit of subbing, deserving of a full Giles Coren. Regardless, it&#8217;s hardly against WP policy to assume that words published under someone&#8217;s name are indeed their own words, at least until contrary evidence emerges.)</p>
<p>Of course, Wales has now ensured that the issue everyone will be talking about instead is his apparent belief that Wikipedia&#8217;s overriding policy is the little-known &#8220;WP:Make Jimmy Wales&#8217; Life Easier&#8221;. So, hey ho.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
