<?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: Not ALL Wikipedia Links NoFollow</title>
	<atom:link href="http://www.seorefugee.com/seoblog/2007/01/23/not-all-wikipedia-links-nofollow/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.seorefugee.com/seoblog/2007/01/23/not-all-wikipedia-links-nofollow/</link>
	<description>search engine optimization information from our seo blog and seo forum</description>
	<pubDate>Sun, 12 Feb 2012 09:12:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Skitzzo</title>
		<link>http://www.seorefugee.com/seoblog/2007/01/23/not-all-wikipedia-links-nofollow/#comment-207</link>
		<dc:creator>Skitzzo</dc:creator>
		<pubDate>Wed, 24 Jan 2007 23:42:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.seorefugee.com/seoblog/2007/01/23/not-all-wikipedia-links-nofollow/#comment-207</guid>
		<description>Sorv, the links of your name are not nofollowed, only links entered in the comments and to be honest, I'm not sure where that's set up. I'll try and track it down though.

If anyone knows where to look please feel free to share.</description>
		<content:encoded><![CDATA[<p>Sorv, the links of your name are not nofollowed, only links entered in the comments and to be honest, I&#8217;m not sure where that&#8217;s set up. I&#8217;ll try and track it down though.</p>
<p>If anyone knows where to look please feel free to share.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AG</title>
		<link>http://www.seorefugee.com/seoblog/2007/01/23/not-all-wikipedia-links-nofollow/#comment-201</link>
		<dc:creator>AG</dc:creator>
		<pubDate>Wed, 24 Jan 2007 18:59:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.seorefugee.com/seoblog/2007/01/23/not-all-wikipedia-links-nofollow/#comment-201</guid>
		<description>Lea: Many wikis probably do; I'm not that well versed in the details. However, en.WP is the single most heavily used wiki around, by some sizable margin, and one of the ways to cope with the traffic is a very heavy layer of caching - it simplifies matters enormously if only a small proportion of pageviews require a database query, rather than them all.

Basically, the HTML rendering is done a stage earlier than you think it is. My understanding is that almost all pages the casual reader sees* are lumps of pre-generated HTML stored in the cache servers and sent out to readers; whenever the page is edited, or any "component" (templates, images) included into the page is itself altered, the HTML is regenerated from the source by a central server and sent to the caches.

But if you change the way the HTML parser renders the source, it doesn't know to invalidate the existing HTML - it's all been done, after all, and nothing has changed in the source. So old things like this can persist for a short while even when most pages have changed over, simply because the system hasn't needed to regenerate them.

If you want to force the change, to see if it's working okay, use http://en.wikipedia.org/w/index.php?title=PAGENAME&#38;action=purge - this forces a purge of the cache - and reload.

As to untouched older pages periodically regenerating - I think they are, but I don't know for sure. This would presumably stop it persisting *too* long, but cache servers can do strange things.

*logged-in users may be handled differently, I vaguely recall.</description>
		<content:encoded><![CDATA[<p>Lea: Many wikis probably do; I&#8217;m not that well versed in the details. However, en.WP is the single most heavily used wiki around, by some sizable margin, and one of the ways to cope with the traffic is a very heavy layer of caching - it simplifies matters enormously if only a small proportion of pageviews require a database query, rather than them all.</p>
<p>Basically, the HTML rendering is done a stage earlier than you think it is. My understanding is that almost all pages the casual reader sees* are lumps of pre-generated HTML stored in the cache servers and sent out to readers; whenever the page is edited, or any &#8220;component&#8221; (templates, images) included into the page is itself altered, the HTML is regenerated from the source by a central server and sent to the caches.</p>
<p>But if you change the way the HTML parser renders the source, it doesn&#8217;t know to invalidate the existing HTML - it&#8217;s all been done, after all, and nothing has changed in the source. So old things like this can persist for a short while even when most pages have changed over, simply because the system hasn&#8217;t needed to regenerate them.</p>
<p>If you want to force the change, to see if it&#8217;s working okay, use <a href="http://en.wikipedia.org/w/index.php?title=PAGENAME&amp;action=purge" rel="nofollow">http://en.wikipedia.org/w/index.php?title=PAGENAME&amp;action=purge</a> - this forces a purge of the cache - and reload.</p>
<p>As to untouched older pages periodically regenerating - I think they are, but I don&#8217;t know for sure. This would presumably stop it persisting *too* long, but cache servers can do strange things.</p>
<p>*logged-in users may be handled differently, I vaguely recall.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trond Sorvoja</title>
		<link>http://www.seorefugee.com/seoblog/2007/01/23/not-all-wikipedia-links-nofollow/#comment-191</link>
		<dc:creator>Trond Sorvoja</dc:creator>
		<pubDate>Wed, 24 Jan 2007 10:17:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.seorefugee.com/seoblog/2007/01/23/not-all-wikipedia-links-nofollow/#comment-191</guid>
		<description>It is a server side cache issue, all exernal links has the fraking nofollow attribute. That being said, when are you going to remove the nofollow on the comments in this blog?</description>
		<content:encoded><![CDATA[<p>It is a server side cache issue, all exernal links has the fraking nofollow attribute. That being said, when are you going to remove the nofollow on the comments in this blog?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lea</title>
		<link>http://www.seorefugee.com/seoblog/2007/01/23/not-all-wikipedia-links-nofollow/#comment-185</link>
		<dc:creator>Lea</dc:creator>
		<pubDate>Wed, 24 Jan 2007 05:35:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.seorefugee.com/seoblog/2007/01/23/not-all-wikipedia-links-nofollow/#comment-185</guid>
		<description>Not a cache issue?
I thought I saw the same thing on some pages, but when I checked again the next day they were nofollowed. I assumed it was my cache clearing, but who knows?

AG: I would have thought the point of a wiki was that every page was generated on the fly from the db?
Remember the editor does NOT enter anchor tags, but wiki markup, so all that needs to be done is alter the way the anchor element is generated from the wiki markup</description>
		<content:encoded><![CDATA[<p>Not a cache issue?<br />
I thought I saw the same thing on some pages, but when I checked again the next day they were nofollowed. I assumed it was my cache clearing, but who knows?</p>
<p>AG: I would have thought the point of a wiki was that every page was generated on the fly from the db?<br />
Remember the editor does NOT enter anchor tags, but wiki markup, so all that needs to be done is alter the way the anchor element is generated from the wiki markup</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AG</title>
		<link>http://www.seorefugee.com/seoblog/2007/01/23/not-all-wikipedia-links-nofollow/#comment-182</link>
		<dc:creator>AG</dc:creator>
		<pubDate>Wed, 24 Jan 2007 01:10:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.seorefugee.com/seoblog/2007/01/23/not-all-wikipedia-links-nofollow/#comment-182</guid>
		<description>To modify every "a href..." to include nofollow tags, Wikipedia needs to effectively regenerate the code for anywhere from one point six to three million pages. (Figures are a bit vague because I can't recall if nofollow was already enabled on non-article pages). As that'd put undue strain on the system, it doesn't do it at once; it does it when the cached copy of any given page is cleared out and refreshed. So if the page you're looking at hasn't been altered since the change - "sabotage" was last edited on Jan 12th - chances are it hasn't been recached yet, and so the links haven't been "nofollowed".

Wikipedia (and MediaWiki generally) would indeed *like* to have some kind of selective enabling/disabling/whitelisting/whatever for nofollow tags and URLs; please send them any suggestions which can easily scale up to an active community of fifty thousand people and three million pages...</description>
		<content:encoded><![CDATA[<p>To modify every &#8220;a href&#8230;&#8221; to include nofollow tags, Wikipedia needs to effectively regenerate the code for anywhere from one point six to three million pages. (Figures are a bit vague because I can&#8217;t recall if nofollow was already enabled on non-article pages). As that&#8217;d put undue strain on the system, it doesn&#8217;t do it at once; it does it when the cached copy of any given page is cleared out and refreshed. So if the page you&#8217;re looking at hasn&#8217;t been altered since the change - &#8220;sabotage&#8221; was last edited on Jan 12th - chances are it hasn&#8217;t been recached yet, and so the links haven&#8217;t been &#8220;nofollowed&#8221;.</p>
<p>Wikipedia (and MediaWiki generally) would indeed *like* to have some kind of selective enabling/disabling/whitelisting/whatever for nofollow tags and URLs; please send them any suggestions which can easily scale up to an active community of fifty thousand people and three million pages&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

