<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>Qatano Website Development - Articles</title>
	<atom:link href="http://qatano.com/articles/feed/" rel="self" type="application/rss+xml" />
	<link>http://qatano.com/articles</link>
	<description>Qatano</description>
	<pubDate>Thu, 03 Aug 2006 21:30:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
	<language>en</language>
			<item>
		<title>Preventing Email Harvesting</title>
		<link>http://eoghan.qatano.org/2006/08/03/preventing-email-harvesting/</link>
		<comments>http://eoghan.qatano.org/2006/08/03/preventing-email-harvesting/#comments</comments>
		<pubDate>Thu, 03 Aug 2006 21:30:06 +0000</pubDate>
		<dc:creator>Eoghan</dc:creator>
		
		<category><![CDATA[Article]]></category>

		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://eoghan.qatano.org/2006/08/03/preventing-email-harvesting/</guid>
		<description><![CDATA[An accessible method with MochiKit
When you include a href=&#8221;mailto:name@example.com&#8221; link on your page you are publishing a sure fire way of attracting spam.  The usual way around this is to mangle the email address, the typical example being href=&#8221;mailto:name [at] example [dot] com&#8221;. Unfortunately this relies on your user being savvy enough to edit [...]]]></description>
		<wfw:commentRss>http://eoghan.qatano.org/2006/08/03/preventing-email-harvesting/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
