<?xml version="1.0"?>
<rdf:RDF 
	xmlns:cc="http://web.resource.org/cc/"
	xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
	xmlns:dc="http://purl.org/dc/elements/1.1/">

<rdf:Description rdf:about="/opensource/blog/0413_thoughts_on_trackback_spam.html">

	<dc:creator>Tobias Schlitt</dc:creator>
	<dc:title>Thoughts on trackback spam</dc:title>
	<dc:date>Wed, 19 Nov 2008 23:29:46 +0100</dc:date>
	<dc:rights>CC by-nc-sa</dc:rights>
	<dc:language>en</dc:language>
	<dc:format>text/html</dc:format>

	<dc:description>It's been a long while since I worked on my PEAR package
Services_Trackback, mainly because I was much too busy with work and
university. Nevertheless I made up my mind about how to solve the problem
of the so-called trackback spam. In email environments people search for a
solution to spam since email was invented and by now, no satisfactory
solution was found (AFAIK, please correct me, if I'm wrong, I would be
thrilled). Approaches here include complicated techniques like heuristic
algorithms and easy ones like grey-listing, as well as sender
identification (which is useless by now, since no unique standard exists
and almost no program supports it).</dc:description>
</rdf:Description> 

<rdf:Description rdf:about="/opensource/blog/0413_thoughts_on_trackback_spam.txt">

	<dc:creator>Tobias Schlitt</dc:creator>
	<dc:title>Thoughts on trackback spam</dc:title>
	<dc:date>Wed, 19 Nov 2008 23:29:46 +0100</dc:date>
	<dc:rights>CC by-nc-sa</dc:rights>
	<dc:language>en</dc:language>
	<dc:format>text/plain</dc:format>

	<dc:description>It's been a long while since I worked on my PEAR package
Services_Trackback, mainly because I was much too busy with work and
university. Nevertheless I made up my mind about how to solve the problem
of the so-called trackback spam. In email environments people search for a
solution to spam since email was invented and by now, no satisfactory
solution was found (AFAIK, please correct me, if I'm wrong, I would be
thrilled). Approaches here include complicated techniques like heuristic
algorithms and easy ones like grey-listing, as well as sender
identification (which is useless by now, since no unique standard exists
and almost no program supports it).</dc:description>
</rdf:Description> 

<rdf:Description rdf:about="/opensource/blog/0413_thoughts_on_trackback_spam.rss">

	<dc:creator>Tobias Schlitt</dc:creator>
	<dc:title>Thoughts on trackback spam</dc:title>
	<dc:date>Wed, 19 Nov 2008 23:29:46 +0100</dc:date>
	<dc:rights>CC by-nc-sa</dc:rights>
	<dc:language>en</dc:language>
	<dc:format>application/rss+xml</dc:format>

	<dc:description>It's been a long while since I worked on my PEAR package
Services_Trackback, mainly because I was much too busy with work and
university. Nevertheless I made up my mind about how to solve the problem
of the so-called trackback spam. In email environments people search for a
solution to spam since email was invented and by now, no satisfactory
solution was found (AFAIK, please correct me, if I'm wrong, I would be
thrilled). Approaches here include complicated techniques like heuristic
algorithms and easy ones like grey-listing, as well as sender
identification (which is useless by now, since no unique standard exists
and almost no program supports it).</dc:description>
</rdf:Description> 

</rdf:RDF>
