<?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: Permalink it</title>
	<atom:link href="http://peteashton.com/2006/02/permalink_it/feed/" rel="self" type="application/rss+xml" />
	<link>http://peteashton.com/2006/02/permalink_it/</link>
	<description>This is my blog. There are many like it, but this one is mine.</description>
	<lastBuildDate>Tue, 09 Mar 2010 14:42:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Pete Ashton</title>
		<link>http://peteashton.com/2006/02/permalink_it/comment-page-1/#comment-1623</link>
		<dc:creator>Pete Ashton</dc:creator>
		<pubDate>Wed, 22 Feb 2006 06:47:59 +0000</pubDate>
		<guid isPermaLink="false">http://peteashton.com/2006/02/permalink_it/#comment-1623</guid>
		<description>Kinda scary that you needed to do that. I thought the concept of a &quot;permalink&quot; was pretty well known. 

There&#039;s a bit of history involved. In the beginning all weblogs consisted of a main index and monthly archives which contained multiple posts in chronological order. Before Movable Type popularised the Individual archive page (such as this page here) there was a need to be able to link to a post that was part of a page and for that link to be permanent. So each post was assigned a unique ID number and the URL used to link to it took you to the monthly archive. 

For example, here&#039;s a permalink for Diamond Geezer (who is resolutely old school in this regard):

&lt;a href=&quot;http://diamondgeezer.blogspot.com/2006_02_01_diamondgeezer_archive.html#113962370568142265&quot; rel=&quot;nofollow&quot;&gt;http://diamondgeezer.blogspot.com/2006_02_01_diamondgeezer_archive.html#113962370568142265&lt;/a&gt;

It&#039;s a bit of a mess (thanks to a clunky system introduced by Blogger a long time ago) but the important bit is the #113962370568142265. This unique ID ensures that when the page is loaded the screen moves to the post in question, regardless of what has been added above or below it. This URL is appended to the end of the post so that should you need to find or link to that post you can do so with that address.

Nowadays most blogs have their posts archived on individual pages so the permalink is a basic URL, but the principle is the same.

Simple, really. 
</description>
		<content:encoded><![CDATA[<p>Kinda scary that you needed to do that. I thought the concept of a &#8220;permalink&#8221; was pretty well known. </p>
<p>There&#8217;s a bit of history involved. In the beginning all weblogs consisted of a main index and monthly archives which contained multiple posts in chronological order. Before Movable Type popularised the Individual archive page (such as this page here) there was a need to be able to link to a post that was part of a page and for that link to be permanent. So each post was assigned a unique ID number and the URL used to link to it took you to the monthly archive. </p>
<p>For example, here&#8217;s a permalink for Diamond Geezer (who is resolutely old school in this regard):</p>
<p><a href="http://diamondgeezer.blogspot.com/2006_02_01_diamondgeezer_archive.html#113962370568142265" rel="nofollow">http://diamondgeezer.blogspot.com/2006_02_01_diamondgeezer_archive.html#113962370568142265</a></p>
<p>It&#8217;s a bit of a mess (thanks to a clunky system introduced by Blogger a long time ago) but the important bit is the #113962370568142265. This unique ID ensures that when the page is loaded the screen moves to the post in question, regardless of what has been added above or below it. This URL is appended to the end of the post so that should you need to find or link to that post you can do so with that address.</p>
<p>Nowadays most blogs have their posts archived on individual pages so the permalink is a basic URL, but the principle is the same.</p>
<p>Simple, really.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: etat</title>
		<link>http://peteashton.com/2006/02/permalink_it/comment-page-1/#comment-1622</link>
		<dc:creator>etat</dc:creator>
		<pubDate>Fri, 17 Feb 2006 18:37:43 +0000</pubDate>
		<guid isPermaLink="false">http://peteashton.com/2006/02/permalink_it/#comment-1622</guid>
		<description>I&#039;ve looked into this a bit more, and have now written my own somewhat-longer-than-a-comment  findings at &lt;a href=&quot;http://e-tat.blogspot.com/2006/02/whats-permalink.html&quot; rel=&quot;nofollow&quot;&gt;
	 What&#039;s a &lt;i&gt;permalink&lt;/i&gt;?
	 &lt;/a&gt;

The upshot is that it would be nice to have a script/extension/function that produced a standard (&lt;a href=&quot;&quot; rel=&quot;nofollow&quot;&gt;via&lt;/a&gt;) link from a given webpage. Anybody seen one lying around?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve looked into this a bit more, and have now written my own somewhat-longer-than-a-comment  findings at <a href="http://e-tat.blogspot.com/2006/02/whats-permalink.html" rel="nofollow"><br />
	 What&#8217;s a <i>permalink</i>?<br />
	 </a></p>
<p>The upshot is that it would be nice to have a script/extension/function that produced a standard (<a href="" rel="nofollow">via</a>) link from a given webpage. Anybody seen one lying around?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon</title>
		<link>http://peteashton.com/2006/02/permalink_it/comment-page-1/#comment-1621</link>
		<dc:creator>Gordon</dc:creator>
		<pubDate>Thu, 16 Feb 2006 22:29:12 +0000</pubDate>
		<guid isPermaLink="false">http://peteashton.com/2006/02/permalink_it/#comment-1621</guid>
		<description>Ohh I do that too...

I guess a quick right-click, copy link location (Firefox) would do the job but.. well.. if I DO link to something I spotted on Boing Boing (which I did recently) then chances are most people will have seen it, even if not on Boing Boing but on another site that got it from them.

Yes it&#039;s lazy and presumptious. My bad.

Will try harder.

(Ya moany git)</description>
		<content:encoded><![CDATA[<p>Ohh I do that too&#8230;</p>
<p>I guess a quick right-click, copy link location (Firefox) would do the job but.. well.. if I DO link to something I spotted on Boing Boing (which I did recently) then chances are most people will have seen it, even if not on Boing Boing but on another site that got it from them.</p>
<p>Yes it&#8217;s lazy and presumptious. My bad.</p>
<p>Will try harder.</p>
<p>(Ya moany git)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: etat</title>
		<link>http://peteashton.com/2006/02/permalink_it/comment-page-1/#comment-1620</link>
		<dc:creator>etat</dc:creator>
		<pubDate>Thu, 16 Feb 2006 15:24:31 +0000</pubDate>
		<guid isPermaLink="false">http://peteashton.com/2006/02/permalink_it/#comment-1620</guid>
		<description>Oops. That would be aimed at me. 
I got the cartoon in, but forgot about the attribution. Sorry about that.

Three further comments:
1. What&#039;s a permalink?
Permalinks, trackbacks, feeds and all manner of other terms. 
All unhelpfully described by jargon-mongers at Wikipedia. 
A simple How-to would be sufficient.
A simple click and paste would be even better.

2. Why is it that comment fields and functions are small, plain text, and rarely editable after posting?
You&#039;d think that blog/CMS builders would extend htmlarea functions to the comments box, and that they&#039;d figure out how to let authors edit their comments after the fact.

3. Fashion Rule No. 4: Never reveal your sources.
If I was the scarf owner in your example I would lie through my teeth rather than let on where I&#039;d got it. 
In fact, I have a lovely cap/scarf combo from Copenhagen, but if you asked me where I got them, I&#039;d lie. 
I&#039;d say they came from Retro Bizarre in Moseley. 
No way do I want to come across anyone else wearing my signature garments!</description>
		<content:encoded><![CDATA[<p>Oops. That would be aimed at me.<br />
I got the cartoon in, but forgot about the attribution. Sorry about that.</p>
<p>Three further comments:<br />
1. What&#8217;s a permalink?<br />
Permalinks, trackbacks, feeds and all manner of other terms.<br />
All unhelpfully described by jargon-mongers at Wikipedia.<br />
A simple How-to would be sufficient.<br />
A simple click and paste would be even better.</p>
<p>2. Why is it that comment fields and functions are small, plain text, and rarely editable after posting?<br />
You&#8217;d think that blog/CMS builders would extend htmlarea functions to the comments box, and that they&#8217;d figure out how to let authors edit their comments after the fact.</p>
<p>3. Fashion Rule No. 4: Never reveal your sources.<br />
If I was the scarf owner in your example I would lie through my teeth rather than let on where I&#8217;d got it.<br />
In fact, I have a lovely cap/scarf combo from Copenhagen, but if you asked me where I got them, I&#8217;d lie.<br />
I&#8217;d say they came from Retro Bizarre in Moseley.<br />
No way do I want to come across anyone else wearing my signature garments!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
