<?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: First Post, Wiki-related Planets, and a new very experimental Planet</title>
	<atom:link href="http://blog.nickj.org/2007/03/09/first-post-wiki-related-planets-and-a-new-very-experimental-planet/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nickj.org/2007/03/09/first-post-wiki-related-planets-and-a-new-very-experimental-planet/</link>
	<description>Just another random blog</description>
	<lastBuildDate>Thu, 29 Sep 2011 01:44:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Nickj</title>
		<link>http://blog.nickj.org/2007/03/09/first-post-wiki-related-planets-and-a-new-very-experimental-planet/comment-page-1/#comment-3</link>
		<dc:creator>Nickj</dc:creator>
		<pubDate>Sat, 10 Mar 2007 00:58:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nickj.org/2007/03/09/first-post-wiki-related-planets-and-a-new-very-experimental-planet/#comment-3</guid>
		<description>Thank you, and completely agree it was the logical step. I&#039;m not sure it&#039;s the best way to do it (having a config file rather than some web ui), but it was the easiest and quickest way to put up the simplest idea that might possibly work, and it can be fine-tuned from there if/as needed.

The config file is on en:wp rather than meta simply because I don&#039;t have an account on meta, and I wanted to get the page semi-protected (whilst still being editable by me) straight away. At some point in the future, if there is SUL + stuff like talk message notification on sign-in for all wikis on which the account is valid (so people get notified of messages on any wiki that&#039;s under the SUL umbrella by signing into just one), then it&#039;ll probably always make sense to use your one identity and place stuff in the &quot;right&quot; place, but right now, for this it was just easiest for me to use en:wp.

-- All the best, Nick.</description>
		<content:encoded><![CDATA[<p>Thank you, and completely agree it was the logical step. I&#8217;m not sure it&#8217;s the best way to do it (having a config file rather than some web ui), but it was the easiest and quickest way to put up the simplest idea that might possibly work, and it can be fine-tuned from there if/as needed.</p>
<p>The config file is on en:wp rather than meta simply because I don&#8217;t have an account on meta, and I wanted to get the page semi-protected (whilst still being editable by me) straight away. At some point in the future, if there is SUL + stuff like talk message notification on sign-in for all wikis on which the account is valid (so people get notified of messages on any wiki that&#8217;s under the SUL umbrella by signing into just one), then it&#8217;ll probably always make sense to use your one identity and place stuff in the &#8220;right&#8221; place, but right now, for this it was just easiest for me to use en:wp.</p>
<p>&#8211; All the best, Nick.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Gerard</title>
		<link>http://blog.nickj.org/2007/03/09/first-post-wiki-related-planets-and-a-new-very-experimental-planet/comment-page-1/#comment-2</link>
		<dc:creator>David Gerard</dc:creator>
		<pubDate>Fri, 09 Mar 2007 08:07:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nickj.org/2007/03/09/first-post-wiki-related-planets-and-a-new-very-experimental-planet/#comment-2</guid>
		<description>Nice one! And, of course, the obvious step to take.

Should the config page be on meta, rather than en:wp?</description>
		<content:encoded><![CDATA[<p>Nice one! And, of course, the obvious step to take.</p>
<p>Should the config page be on meta, rather than en:wp?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
