<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 18 Jun 2013 01:48:51 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Tobias Schlitt's Blog: Thoughts on trackback spam]]></title>
      <guid>http://www.phpdeveloper.org/news/4805</guid>
      <link>http://www.phpdeveloper.org/news/4805</link>
      <description><![CDATA[Related to his work on the <a href="http://pear.php.net/package/Services_Trackback">Services_Trackback</a> PEAR Package he worked on, <i>Tobias Schlitt</i> looks today in <a href="http://www.schlitt.info/applications/blog/index.php?/archives/413-Thoughts-on-trackback-spam.html">this new blog post</a> at some of his more recent thoughts on trackback spam.
<p>
<quote>
<i>
It's been a long while since I worked on my PEAR package <a href="http://pear.php.net/package/Services_Trackback">Services_Trackback</a>, 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.
<p>
Taking for granted, that the idea should work, there are 2 main questions to answer: "How can a sender of a trackback be identified?" and "If and how must the trackback standard be changed to support the identification?" For question #1 there is a simple answer (IMHO): <a href="http://www.pgpi.org/">PGP</a>/<a href="http://www.gnupg.org/">GPG</a> (further on referred to as GPG, for simplicity). 
</i>
</quote>
<p>
<a href="http://www.schlitt.info/applications/blog/index.php?/archives/413-Thoughts-on-trackback-spam.html">He suggests</a> that since there is already a "trust relationship" inherent in the system, a PGP/GPG setup might be the most flexible, easy-to-use, constantly adapting method for preventing one of the banes of bloggers' existences...]]></description>
      <pubDate>Tue, 07 Feb 2006 06:53:10 -0600</pubDate>
    </item>
  </channel>
</rss>
