<?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: WordPress: Secure &amp; Accessible PHP Contact Form SPAMs Blogs</title>
	<atom:link href="http://onemansblog.com/2007/03/21/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/feed/" rel="self" type="application/rss+xml" />
	<link>http://onemansblog.com/2007/03/21/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/</link>
	<description>Specialization is for Insects.</description>
	<lastBuildDate>Tue, 14 Feb 2012 05:44:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mike Cherim</title>
		<link>http://onemansblog.com/2007/03/21/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/comment-page-1/#comment-2480</link>
		<dc:creator>Mike Cherim</dc:creator>
		<pubDate>Sun, 15 Apr 2007 21:53:57 +0000</pubDate>
		<guid isPermaLink="false">http://onemansblog.com/2007/03/30/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/#comment-2480</guid>
		<description>Thanks for that, John. The whole thing that bothered me was that I hate spam and the miscreants that play the spam game, and I work hard against it, so to be accused of &quot;spamdexing&quot; didn&#039;t sit well with me (and your original email to me had sort of a threatening tone). I felt as if I had my back to a wall and in front of me was a firing squad. 

I never had any ill-intentions. I do like and really appreciate link-backs, but based on past experiences, I saw a lot of people removing link-backs on my themes and whatnot. The reason I felt is that they didn&#039;t want to advertise me since a lot of users are web developers themselves --- competition et. al., and I understand that. Thus, when I created this form I decided I&#039;d make easy for people to remove the visible link without wiping it out entirely. I did think the terms were clear but apparently not everyone did. Moreover, I never considered that it would put anyone at risk because lots of accessibility practices utilize that type technique, what I call &quot;offset&quot; positioning, to cater to the needs of screen reader users and the like.

Re-reading my comments, my apologies to you for my seeming belligerence during this process of your simply trying to affect a change, and apologies to anyone who felt I had acted in a deceitful or underhanded way by setting this up the way I did. I swear that was never my intention.

I did see that post, and form, at HTMLHelp (thanks, I like the fact you&#039;re using it). I noted it when I got the trackback. I don&#039;t publish comments on my &quot;pages,&quot; but I do see them when they come in.

No hard feelings.

Mike</description>
		<content:encoded><![CDATA[<p>Thanks for that, John. The whole thing that bothered me was that I hate spam and the miscreants that play the spam game, and I work hard against it, so to be accused of &#8220;spamdexing&#8221; didn&#8217;t sit well with me (and your original email to me had sort of a threatening tone). I felt as if I had my back to a wall and in front of me was a firing squad. </p>
<p>I never had any ill-intentions. I do like and really appreciate link-backs, but based on past experiences, I saw a lot of people removing link-backs on my themes and whatnot. The reason I felt is that they didn&#8217;t want to advertise me since a lot of users are web developers themselves &#8212; competition et. al., and I understand that. Thus, when I created this form I decided I&#8217;d make easy for people to remove the visible link without wiping it out entirely. I did think the terms were clear but apparently not everyone did. Moreover, I never considered that it would put anyone at risk because lots of accessibility practices utilize that type technique, what I call &#8220;offset&#8221; positioning, to cater to the needs of screen reader users and the like.</p>
<p>Re-reading my comments, my apologies to you for my seeming belligerence during this process of your simply trying to affect a change, and apologies to anyone who felt I had acted in a deceitful or underhanded way by setting this up the way I did. I swear that was never my intention.</p>
<p>I did see that post, and form, at HTMLHelp (thanks, I like the fact you&#8217;re using it). I noted it when I got the trackback. I don&#8217;t publish comments on my &#8220;pages,&#8221; but I do see them when they come in.</p>
<p>No hard feelings.</p>
<p>Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Man</title>
		<link>http://onemansblog.com/2007/03/21/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/comment-page-1/#comment-2478</link>
		<dc:creator>The Man</dc:creator>
		<pubDate>Sun, 15 Apr 2007 21:02:15 +0000</pubDate>
		<guid isPermaLink="false">http://onemansblog.com/2007/03/30/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/#comment-2478</guid>
		<description>Mike,

I am &lt;em&gt;extremely&lt;/em&gt; pleased (and actually surprised) by your decision.

I always assumed from day one that you &lt;strong&gt;must&lt;/strong&gt; be a good guy given your attention to accessibility, standards compliance, and the free distribution of your work (not only this plugin).  In fact, if I hadn&#039;t assumed you were a nice guy this whole thing would have gone very, very differently.  I regret that we both had to go through so much aggravation over this one issue.  Clearly, the problem exists because of our different interpretations of it&#039;s severity as well as differences in our perception of the language involved.

I appreciate the fact that you chose not only to remove the hidden links, but even to allow removal of the attribution altogether!  I did not expect that, although I do honestly believe that in the end you will be benefited from this choice more than simply requiring the attribution.

As a peace offering, I have installed the plugin on the soon to launch &lt;a href=&quot;http://blog.htmlhelp.com&quot; rel=&quot;nofollow&quot;&gt;HTMLHelp.blog&lt;/a&gt;.  You will find the contact link at the very bottom of the page, and I also created an attribution page which you&#039;ll find &lt;a href=&quot;http://blog.htmlhelp.com/2007/04/15/the-htmlhelpblog-theme-and-plugin-page/&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.  If this whole process has left you wishing I would not use the plugin I&#039;ll understand and you can let me know publicly or privately and I&#039;ll remove the form and we&#039;ll go our separate ways.

Take care,

John

PS - In a few days I&#039;ll close comments and trackbacks on this thread.</description>
		<content:encoded><![CDATA[<p>Mike,</p>
<p>I am <em>extremely</em> pleased (and actually surprised) by your decision.</p>
<p>I always assumed from day one that you <strong>must</strong> be a good guy given your attention to accessibility, standards compliance, and the free distribution of your work (not only this plugin).  In fact, if I hadn&#8217;t assumed you were a nice guy this whole thing would have gone very, very differently.  I regret that we both had to go through so much aggravation over this one issue.  Clearly, the problem exists because of our different interpretations of it&#8217;s severity as well as differences in our perception of the language involved.</p>
<p>I appreciate the fact that you chose not only to remove the hidden links, but even to allow removal of the attribution altogether!  I did not expect that, although I do honestly believe that in the end you will be benefited from this choice more than simply requiring the attribution.</p>
<p>As a peace offering, I have installed the plugin on the soon to launch <a href="http://blog.htmlhelp.com" rel="nofollow">HTMLHelp.blog</a>.  You will find the contact link at the very bottom of the page, and I also created an attribution page which you&#8217;ll find <a href="http://blog.htmlhelp.com/2007/04/15/the-htmlhelpblog-theme-and-plugin-page/" rel="nofollow">here</a>.  If this whole process has left you wishing I would not use the plugin I&#8217;ll understand and you can let me know publicly or privately and I&#8217;ll remove the form and we&#8217;ll go our separate ways.</p>
<p>Take care,</p>
<p>John</p>
<p>PS &#8211; In a few days I&#8217;ll close comments and trackbacks on this thread.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cherim</title>
		<link>http://onemansblog.com/2007/03/21/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/comment-page-1/#comment-2433</link>
		<dc:creator>Mike Cherim</dc:creator>
		<pubDate>Sat, 14 Apr 2007 17:12:09 +0000</pubDate>
		<guid isPermaLink="false">http://onemansblog.com/2007/03/30/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/#comment-2433</guid>
		<description>I give up -- you win! I changed all the downloads (both WP and non-WP) and removed the hidden link-back, email link-backs, and the success result link-back. I also changed the WP documentation file to read that the link is &quot;removed&quot; instead of &quot;hidden&quot; and the terms of use have been changed to reflect this.

Please tell users to change line 1320 to this:
&lt;code&gt;    $forms.=(&#039;          &lt;!&#045;&#045;&#039;.$build.&#039;&#045;&#045;&gt;&#039;.&quot;\n&quot;);&lt;/code&gt;

This helps with support. Since I get about three support emails per day it&#039;s very helpful to know what build number the user has.

For the record, my intention was &lt;strong&gt;never&lt;/strong&gt; to dupe, spam, or trick anyone and I don&#039;t appreciate your accusation. The terms and documentation said that the link would be &quot;hidden&quot; not removed. I thought I was being up-front about it, despite what you may think. I&#039;ve always had high moral standards despite what your opinion of me may be.</description>
		<content:encoded><![CDATA[<p>I give up &#8212; you win! I changed all the downloads (both WP and non-WP) and removed the hidden link-back, email link-backs, and the success result link-back. I also changed the WP documentation file to read that the link is &#8220;removed&#8221; instead of &#8220;hidden&#8221; and the terms of use have been changed to reflect this.</p>
<p>Please tell users to change line 1320 to this:<br />
<code>    $forms.=(&#39;          &lt;!&#45;&#45;&#39;.$build.&#39;&#45;&#45;&gt;&#39;.&quot;\n&quot;);</code></p>
<p>This helps with support. Since I get about three support emails per day it&#8217;s very helpful to know what build number the user has.</p>
<p>For the record, my intention was <strong>never</strong> to dupe, spam, or trick anyone and I don&#8217;t appreciate your accusation. The terms and documentation said that the link would be &#8220;hidden&#8221; not removed. I thought I was being up-front about it, despite what you may think. I&#8217;ve always had high moral standards despite what your opinion of me may be.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cherim</title>
		<link>http://onemansblog.com/2007/03/21/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/comment-page-1/#comment-2421</link>
		<dc:creator>Mike Cherim</dc:creator>
		<pubDate>Sat, 14 Apr 2007 06:42:46 +0000</pubDate>
		<guid isPermaLink="false">http://onemansblog.com/2007/03/30/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/#comment-2421</guid>
		<description>What can I say? I have a family to feed so I have to think of *some* ROI. I spend a lot of time keeping up with this. I&#039;ve run a business for a long time so I do see both sides to the free software debate. I&#039;ve made three themes for WordPress and only one has a link-back requirement in its terms. The other two I just ask (and I ask that they keep the link to WP as well).

Regarding the form, it wasn&#039;t even a WordPress plugin originally, it&#039;s just build upon the original script that I&#039;ve been working with for two years or so. The terms have always been the same.

Anyway, like I wrote, Mike and I have been discussing this and might change it with the next micro build, possibly move it to a small license-based program. I spend about 8-10 hours a week on form related stuff so I have to consider that. Donations are few and far between.

I already know you&#039;re with HTMLhelp. It&#039;s a good resource. I link to it from Accessites I think, and maybe my hosting site.</description>
		<content:encoded><![CDATA[<p>What can I say? I have a family to feed so I have to think of *some* ROI. I spend a lot of time keeping up with this. I&#8217;ve run a business for a long time so I do see both sides to the free software debate. I&#8217;ve made three themes for WordPress and only one has a link-back requirement in its terms. The other two I just ask (and I ask that they keep the link to WP as well).</p>
<p>Regarding the form, it wasn&#8217;t even a WordPress plugin originally, it&#8217;s just build upon the original script that I&#8217;ve been working with for two years or so. The terms have always been the same.</p>
<p>Anyway, like I wrote, Mike and I have been discussing this and might change it with the next micro build, possibly move it to a small license-based program. I spend about 8-10 hours a week on form related stuff so I have to consider that. Donations are few and far between.</p>
<p>I already know you&#8217;re with HTMLhelp. It&#8217;s a good resource. I link to it from Accessites I think, and maybe my hosting site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Man</title>
		<link>http://onemansblog.com/2007/03/21/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/comment-page-1/#comment-2419</link>
		<dc:creator>The Man</dc:creator>
		<pubDate>Sat, 14 Apr 2007 06:12:18 +0000</pubDate>
		<guid isPermaLink="false">http://onemansblog.com/2007/03/30/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/#comment-2419</guid>
		<description>Mike, 

For the record, because you initially labeled the software as Open Source, every download up to the point that you changed your license was made in good faith under those terms.  So I think the use of the word &quot;illegal&quot; is not appropriate.

With regards to ethics, neither you, nor I, nor anyone else gets to judge whether our own actions are ethical.  All we can do is lay out the facts that helped us arrive at a given action.  With regards to these hidden back-links I believe you chose your wording and designed your plugin purposely to maintain back-links under all conditions. While I believe you did this thinking it would cause no harm I find it hard to believe you sought certainty on this subject before making your decision. Without exception, every search engine has always maintained that hidden text and links are unacceptable.  I&#039;m guessing it has been this way since before you were authoring for the Web.  Therefore at best you are ethically neutral, and only if ignorance of this fact is working in your favor.  

Your continuous talk of all your hard work warranting payback really bothers me.  The people that developed Wordpress have donated so much more time and energy than you will ever spend in 100 lifetimes without the need to extract a cost from every single user.  At HTMLHelp.com we have spent 10&#039;s of thousands of man hours voluntarily helping people, without ever asking anything in return.  So, please stop bringing that up.  It is rapidly changing my opinion of your charity and skewing my responses.

Moving on to the issue regarding the hidden links.  What I cannot understand is why you unflinchingly cling to your views, and tell people there is no problem, despite the council of someone who runs a Web authoring reference site which literally tens of millions of authors rely on annually.

I mean, you wrote a CSS tutorial and you don&#039;t even realize that I was one of the people who helped define CSS with Hakon Lie and others?  &lt;a href=&quot;http://lists.w3.org/Archives/Public/www-style/1997Jan/&quot; rel=&quot;nofollow&quot;&gt;Look it up&lt;/a&gt;.  The WC3 also lists my reference in their &quot;&lt;a href=&quot;http://www.w3.org/Style/CSS10/hall-of-fame.html&quot; rel=&quot;nofollow&quot;&gt;Hall of Fame&lt;/a&gt;&quot;.  In addition to that, I wrote the &lt;a href=&quot;http://htmlhelp.com/faq/html/preamble.html#credits&quot; rel=&quot;nofollow&quot;&gt;Web Authoring FAQ&lt;/a&gt; and helped with input on web standards from HTML 1.0 on up to what we use today.  Furthermore, the Web accessibility you like to preach is partially based on work I did as a member of the &lt;a href=&quot;http://www.w3.org/WAI/&quot; rel=&quot;nofollow&quot;&gt;Web Accessibility Initiative&lt;/a&gt;.

I&#039;m further amazed that, although even people at Google used HTMLHelp.com to help build their site, you are willing to assert the certainty of your opinion on this matter over my own.  That is &lt;em&gt;awesome&lt;/em&gt; confidence.

You keep saying that your hidden links are &quot;not a big deal&quot;, and I keep telling you that they are worse than you understand.  I have been exceedingly polite and provided you with every opportunity to do the right thing hoping that peer pressure alone would help you make your decision.  And up until this point I have never mentioned my qualifications to critique this matter, instead attempting to rely on pure logical argument.  Obviously that is not going to work.  Clearly you and your friends have rationalized the fact that you are personally to blame for God only knows how many hidden links floating around the net.

So let me be clear.  I do not care if you risk your own domains, but I care very much about unsuspecting Wordpress authors who don&#039;t know enough to understand the risk.  The hidden links should be removed because they pose an &lt;em&gt;unnecessary risk&lt;/em&gt;.  For example, I&#039;ll be in San Francisco meeting with Google in 12 days.  Are you confident enough of your opinion that you would have me run it by them?  In other words, are you willing to bet your domains on it?  I wouldn&#039;t be.

My free and expert advice to you is now, and has been since my first communique, simply to allow users the opportunity to disable and delete the back-links.  I advise this because:
&lt;ul&gt;
&lt;li&gt;If you do a simple Google search you&#039;ll find that the vast majority of your users leave the links in place anyway!  That is what makes your stance so unbelievable. Your attitude appears to be &quot;Not good enough, I want them ALL!&quot;.&lt;/li&gt;
&lt;li&gt;If you allow users to remove it, &lt;u&gt;it doesn&#039;t cost you a thing&lt;/u&gt;, it builds good will, and you might retain users who otherwise will forgo your software but who might have given you donations or links back from their &quot;Plugins I Use&quot; page - which would convey more PR value anyway!  The more exposure you have, the more likely you are to reap some benefit from it over time.  TRUST ME ON THIS!&lt;/li&gt;
&lt;li&gt;For example, I was originally considering using your form on a soon to be launched HTMLHelp.com blog, not my personal blog.  The PR benefit from our attribution would eventually likely have exceeded hundreds of other sites combined.&lt;/li&gt;
&lt;/ul&gt;
Finally, there is a huge movement right now in the Wordpress community which you are probably not aware of regarding hidden and sponsored links in themes and plugins.  It starts at the top.  Matt M. wants to ban sponsored link themes from Wordpress.org, and I and others are arguing merely for full disclosure.  However, I am advocating an outright ban on all themes and plugins with hidden links - with a 0 tolerance policy.

John

PS- I will not dedicate another moment of my time to this issue.  I do indeed have &quot;bigger fish to fry.&quot;  It&#039;s your software, it&#039;s your decision, I believe I am absolved of my duty to provide any further guidance.  Good luck.</description>
		<content:encoded><![CDATA[<p>Mike, </p>
<p>For the record, because you initially labeled the software as Open Source, every download up to the point that you changed your license was made in good faith under those terms.  So I think the use of the word &#8220;illegal&#8221; is not appropriate.</p>
<p>With regards to ethics, neither you, nor I, nor anyone else gets to judge whether our own actions are ethical.  All we can do is lay out the facts that helped us arrive at a given action.  With regards to these hidden back-links I believe you chose your wording and designed your plugin purposely to maintain back-links under all conditions. While I believe you did this thinking it would cause no harm I find it hard to believe you sought certainty on this subject before making your decision. Without exception, every search engine has always maintained that hidden text and links are unacceptable.  I&#8217;m guessing it has been this way since before you were authoring for the Web.  Therefore at best you are ethically neutral, and only if ignorance of this fact is working in your favor.  </p>
<p>Your continuous talk of all your hard work warranting payback really bothers me.  The people that developed WordPress have donated so much more time and energy than you will ever spend in 100 lifetimes without the need to extract a cost from every single user.  At HTMLHelp.com we have spent 10&#8242;s of thousands of man hours voluntarily helping people, without ever asking anything in return.  So, please stop bringing that up.  It is rapidly changing my opinion of your charity and skewing my responses.</p>
<p>Moving on to the issue regarding the hidden links.  What I cannot understand is why you unflinchingly cling to your views, and tell people there is no problem, despite the council of someone who runs a Web authoring reference site which literally tens of millions of authors rely on annually.</p>
<p>I mean, you wrote a CSS tutorial and you don&#8217;t even realize that I was one of the people who helped define CSS with Hakon Lie and others?  <a href="http://lists.w3.org/Archives/Public/www-style/1997Jan/" rel="nofollow">Look it up</a>.  The WC3 also lists my reference in their &#8220;<a href="http://www.w3.org/Style/CSS10/hall-of-fame.html" rel="nofollow">Hall of Fame</a>&#8220;.  In addition to that, I wrote the <a href="http://htmlhelp.com/faq/html/preamble.html#credits" rel="nofollow">Web Authoring FAQ</a> and helped with input on web standards from HTML 1.0 on up to what we use today.  Furthermore, the Web accessibility you like to preach is partially based on work I did as a member of the <a href="http://www.w3.org/WAI/" rel="nofollow">Web Accessibility Initiative</a>.</p>
<p>I&#8217;m further amazed that, although even people at Google used HTMLHelp.com to help build their site, you are willing to assert the certainty of your opinion on this matter over my own.  That is <em>awesome</em> confidence.</p>
<p>You keep saying that your hidden links are &#8220;not a big deal&#8221;, and I keep telling you that they are worse than you understand.  I have been exceedingly polite and provided you with every opportunity to do the right thing hoping that peer pressure alone would help you make your decision.  And up until this point I have never mentioned my qualifications to critique this matter, instead attempting to rely on pure logical argument.  Obviously that is not going to work.  Clearly you and your friends have rationalized the fact that you are personally to blame for God only knows how many hidden links floating around the net.</p>
<p>So let me be clear.  I do not care if you risk your own domains, but I care very much about unsuspecting WordPress authors who don&#8217;t know enough to understand the risk.  The hidden links should be removed because they pose an <em>unnecessary risk</em>.  For example, I&#8217;ll be in San Francisco meeting with Google in 12 days.  Are you confident enough of your opinion that you would have me run it by them?  In other words, are you willing to bet your domains on it?  I wouldn&#8217;t be.</p>
<p>My free and expert advice to you is now, and has been since my first communique, simply to allow users the opportunity to disable and delete the back-links.  I advise this because:</p>
<ul>
<li>If you do a simple Google search you&#8217;ll find that the vast majority of your users leave the links in place anyway!  That is what makes your stance so unbelievable. Your attitude appears to be &#8220;Not good enough, I want them ALL!&#8221;.</li>
<li>If you allow users to remove it, <u>it doesn&#8217;t cost you a thing</u>, it builds good will, and you might retain users who otherwise will forgo your software but who might have given you donations or links back from their &#8220;Plugins I Use&#8221; page &#8211; which would convey more PR value anyway!  The more exposure you have, the more likely you are to reap some benefit from it over time.  TRUST ME ON THIS!</li>
<li>For example, I was originally considering using your form on a soon to be launched HTMLHelp.com blog, not my personal blog.  The PR benefit from our attribution would eventually likely have exceeded hundreds of other sites combined.</li>
</ul>
<p>Finally, there is a huge movement right now in the WordPress community which you are probably not aware of regarding hidden and sponsored links in themes and plugins.  It starts at the top.  Matt M. wants to ban sponsored link themes from WordPress.org, and I and others are arguing merely for full disclosure.  However, I am advocating an outright ban on all themes and plugins with hidden links &#8211; with a 0 tolerance policy.</p>
<p>John</p>
<p>PS- I will not dedicate another moment of my time to this issue.  I do indeed have &#8220;bigger fish to fry.&#8221;  It&#8217;s your software, it&#8217;s your decision, I believe I am absolved of my duty to provide any further guidance.  Good luck.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cherim</title>
		<link>http://onemansblog.com/2007/03/21/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/comment-page-1/#comment-2402</link>
		<dc:creator>Mike Cherim</dc:creator>
		<pubDate>Fri, 13 Apr 2007 20:18:01 +0000</pubDate>
		<guid isPermaLink="false">http://onemansblog.com/2007/03/30/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/#comment-2402</guid>
		<description>Hi Andrew, there will be no problem with that, the author link, or offset jump links and image replacement text for that matter. I have a whole paragraph of offset text for users that don&#039;t support style sheets in my &quot;&lt;a href=&quot;http://green-beast.com/build-css/&quot; rel=&quot;nofollow&quot;&gt;How to Build a CSS Web Site&lt;/a&gt;&quot; tutorial. This is an accessibility feature. Currently Google doesn&#039;t flag off-screen positioned text. What Google does do if something abusive is reported is not to deal with it on a one-on-one basis (they don&#039;t have the time), but rather to tweak their algorithms to deal with widespread use of such in future revisions of their search tool, and that&#039;s if it&#039;s deemed abusive. What&#039;s considered abusive as a practice is determined by a real person prior to such revisions, not a robot. Google would have no problem with any of my practices. The whole thing here is being blown way out of proportion. What Mike and I did is not unethical (not our intention at all), nor does it put blog owners at risk. We didn&#039;t have to add such a feature, but realized some people would have a hard time delving into the code to illegally remove the link when all they really want is to not show it on their contact page. (I don&#039;t have it showing on my own &lt;a href=&quot;http://green-beast.com/contact/&quot; rel=&quot;nofollow&quot;&gt;contact page&lt;/a&gt; as it looked out of place.) Doing this satisfies our requirements and that of the user. 

Thanks to this post, Mike and I have been discussing this between us, and with other people (the general consensus is that this is sort of melodramatic). What we&#039;re thinking of doing as a result of this whole mess is removing the link removal feature altogether, clamping down harder on our terms, and making users purchase a license to get an credit-free version. We worked, and still work, damn hard on this form and feel we&#039;re providing a decent service to people. Moreover, we provide exemplary support for our free script (better support than some commercial script providers offer actually). Thus, for all this work we want to get something out of it.

Andrew, I appreciate the fact that you&#039;ve provide links anyway. Thank you very much. That&#039;s why we do this (it certainly isn&#039;t the money). I would advise you not to remove the position-hidden input as that one in particular is a highly effective anti-spam tool.</description>
		<content:encoded><![CDATA[<p>Hi Andrew, there will be no problem with that, the author link, or offset jump links and image replacement text for that matter. I have a whole paragraph of offset text for users that don&#8217;t support style sheets in my &#8220;<a href="http://green-beast.com/build-css/" rel="nofollow">How to Build a CSS Web Site</a>&#8221; tutorial. This is an accessibility feature. Currently Google doesn&#8217;t flag off-screen positioned text. What Google does do if something abusive is reported is not to deal with it on a one-on-one basis (they don&#8217;t have the time), but rather to tweak their algorithms to deal with widespread use of such in future revisions of their search tool, and that&#8217;s if it&#8217;s deemed abusive. What&#8217;s considered abusive as a practice is determined by a real person prior to such revisions, not a robot. Google would have no problem with any of my practices. The whole thing here is being blown way out of proportion. What Mike and I did is not unethical (not our intention at all), nor does it put blog owners at risk. We didn&#8217;t have to add such a feature, but realized some people would have a hard time delving into the code to illegally remove the link when all they really want is to not show it on their contact page. (I don&#8217;t have it showing on my own <a href="http://green-beast.com/contact/" rel="nofollow">contact page</a> as it looked out of place.) Doing this satisfies our requirements and that of the user. </p>
<p>Thanks to this post, Mike and I have been discussing this between us, and with other people (the general consensus is that this is sort of melodramatic). What we&#8217;re thinking of doing as a result of this whole mess is removing the link removal feature altogether, clamping down harder on our terms, and making users purchase a license to get an credit-free version. We worked, and still work, damn hard on this form and feel we&#8217;re providing a decent service to people. Moreover, we provide exemplary support for our free script (better support than some commercial script providers offer actually). Thus, for all this work we want to get something out of it.</p>
<p>Andrew, I appreciate the fact that you&#8217;ve provide links anyway. Thank you very much. That&#8217;s why we do this (it certainly isn&#8217;t the money). I would advise you not to remove the position-hidden input as that one in particular is a highly effective anti-spam tool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Man</title>
		<link>http://onemansblog.com/2007/03/21/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/comment-page-1/#comment-2401</link>
		<dc:creator>The Man</dc:creator>
		<pubDate>Fri, 13 Apr 2007 20:12:20 +0000</pubDate>
		<guid isPermaLink="false">http://onemansblog.com/2007/03/30/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/#comment-2401</guid>
		<description>Thanks Andrew.  I didn&#039;t notice that, perhaps because I was so shocked by the other.</description>
		<content:encoded><![CDATA[<p>Thanks Andrew.  I didn&#8217;t notice that, perhaps because I was so shocked by the other.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://onemansblog.com/2007/03/21/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/comment-page-1/#comment-2398</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Fri, 13 Apr 2007 19:04:58 +0000</pubDate>
		<guid isPermaLink="false">http://onemansblog.com/2007/03/30/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/#comment-2398</guid>
		<description>I&#039;ve used this form on a couple of sites recently, albeit modified fairly extensively (once as I wanted to add people to a database rather than sending email, once because I didn&#039;t like the presentation).  I wasn&#039;t too happy when I discovered the hidden text either (though I have linked back separately in both cases).  

However, it&#039;s worth noting that one of the anti-spam features used by this form is a hidden text box, shunted off screen in a similar manner to the author link.  If you believe there could be real problems with Google for &quot;â€¦writing text in such a way that it can be seen by search engines but not by usersâ€¦&quot; - and I&#039;m no expert on this - then you should probably advise people to remove that too.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve used this form on a couple of sites recently, albeit modified fairly extensively (once as I wanted to add people to a database rather than sending email, once because I didn&#8217;t like the presentation).  I wasn&#8217;t too happy when I discovered the hidden text either (though I have linked back separately in both cases).  </p>
<p>However, it&#8217;s worth noting that one of the anti-spam features used by this form is a hidden text box, shunted off screen in a similar manner to the author link.  If you believe there could be real problems with Google for &#8220;â€¦writing text in such a way that it can be seen by search engines but not by usersâ€¦&#8221; &#8211; and I&#8217;m no expert on this &#8211; then you should probably advise people to remove that too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ttancm</title>
		<link>http://onemansblog.com/2007/03/21/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/comment-page-1/#comment-2314</link>
		<dc:creator>ttancm</dc:creator>
		<pubDate>Thu, 12 Apr 2007 07:39:12 +0000</pubDate>
		<guid isPermaLink="false">http://onemansblog.com/2007/03/30/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/#comment-2314</guid>
		<description>@TheMan,
Thanks for the heads up. Now to remove it from the several sites I had it on...

@Mike, the terms on your site were not and are not clear that clicking that option will not remove the link entirely. If you really wanted to be clear you would write exactly what it is that occurs when that option is used (e.g., not just that the &quot;visible link&quot; is removed, but EXPLICITLY state that a hidden link will remain), and honestly anything else is just trying to be sneaky but cover your ass at the same time.

Also the GPL does not allow you to require an attribution link remain in place for end users, only for redistributions, and adding any such requirement makes any license associated with it non-GPL compatible:

The GPL allows the end user to modify things any which way they want, so long as they are not repackaging and redistributing it. That&#039;s kind of the whole point of the license. 

&lt;blockquote&gt;
You may not impose any further restrictions on the recipients&#039; exercise of the rights granted herein.
&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>@TheMan,<br />
Thanks for the heads up. Now to remove it from the several sites I had it on&#8230;</p>
<p>@Mike, the terms on your site were not and are not clear that clicking that option will not remove the link entirely. If you really wanted to be clear you would write exactly what it is that occurs when that option is used (e.g., not just that the &#8220;visible link&#8221; is removed, but EXPLICITLY state that a hidden link will remain), and honestly anything else is just trying to be sneaky but cover your ass at the same time.</p>
<p>Also the GPL does not allow you to require an attribution link remain in place for end users, only for redistributions, and adding any such requirement makes any license associated with it non-GPL compatible:</p>
<p>The GPL allows the end user to modify things any which way they want, so long as they are not repackaging and redistributing it. That&#8217;s kind of the whole point of the license. </p>
<blockquote><p>
You may not impose any further restrictions on the recipients&#8217; exercise of the rights granted herein.
</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cherim</title>
		<link>http://onemansblog.com/2007/03/21/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/comment-page-1/#comment-1952</link>
		<dc:creator>Mike Cherim</dc:creator>
		<pubDate>Sat, 07 Apr 2007 14:26:09 +0000</pubDate>
		<guid isPermaLink="false">http://onemansblog.com/2007/03/30/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/#comment-1952</guid>
		<description>Okay, you got me there, I never looked up the term, and I have removed &quot;open source.&quot; I have never had a problem if people wanted modify the form to suit their needs, and I&#039;ve helped a lot of people do just that, without compensation. 

The copyright&#039;s terms of use restricts two activities by users: re-distribution without permission (for version control more than anything else) and link-back removal without a license. I reserve all other rights. Other than those two activities they are welcome to work with the script to improve it, modify it, change it, etc., and they can even submit it back for adoption and credit in some cases, but I do warn them they may be making it difficult to apply upgrades which I provide regularly. They can even use it on client sites they are getting paid for as long as they are charging for their time and not the script itself -- I&#039;ve been asked this several times.

I didn&#039;t go for a strong copyleft GPL license since in my other business life, a mail order company founded in 1992, I&#039;m used to applying for copyrights, but I am offering a GPL-compatible copyright very similar to some of the CC licences (the WordPress staff agrees with this since they have officially accepted it and they require GPL-compatible terms).

I ask two things. That&#039;s it.</description>
		<content:encoded><![CDATA[<p>Okay, you got me there, I never looked up the term, and I have removed &#8220;open source.&#8221; I have never had a problem if people wanted modify the form to suit their needs, and I&#8217;ve helped a lot of people do just that, without compensation. </p>
<p>The copyright&#8217;s terms of use restricts two activities by users: re-distribution without permission (for version control more than anything else) and link-back removal without a license. I reserve all other rights. Other than those two activities they are welcome to work with the script to improve it, modify it, change it, etc., and they can even submit it back for adoption and credit in some cases, but I do warn them they may be making it difficult to apply upgrades which I provide regularly. They can even use it on client sites they are getting paid for as long as they are charging for their time and not the script itself &#8212; I&#8217;ve been asked this several times.</p>
<p>I didn&#8217;t go for a strong copyleft GPL license since in my other business life, a mail order company founded in 1992, I&#8217;m used to applying for copyrights, but I am offering a GPL-compatible copyright very similar to some of the CC licences (the WordPress staff agrees with this since they have officially accepted it and they require GPL-compatible terms).</p>
<p>I ask two things. That&#8217;s it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Man</title>
		<link>http://onemansblog.com/2007/03/21/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/comment-page-1/#comment-1944</link>
		<dc:creator>The Man</dc:creator>
		<pubDate>Sat, 07 Apr 2007 09:47:30 +0000</pubDate>
		<guid isPermaLink="false">http://onemansblog.com/2007/03/30/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/#comment-1944</guid>
		<description>Mike,

I&#039;m glad you stopped by, and I welcome your comments and opinions.  You may feel free to write anything you like here and I&#039;ll approve it, unaltered.

I&#039;m confused by your assertion that the form is not open source.  The exact words I see on your page are &quot;...no payment is required to use this &lt;em&gt;open source&lt;/em&gt; script...&quot;  Open Source software as defined by &lt;a href=&quot;http://www.opensource.org/docs/definition.php&quot; rel=&quot;nofollow&quot;&gt;OpenSource.org&lt;/a&gt; does not have restrictions against modification, re-distribution, or even resale.

Perhaps you meant something else?  But I can&#039;t come up with any other words that could be accidentally confused with &quot;open source&quot;.  I can only take your words at face value, and I&#039;m confident that any court would do the same.  If, &lt;em&gt;and only if&lt;/em&gt;, my argument is correct, users would indeed be allowed by law to modify the script.  

I cannot in good conscience remove the fix I provided for the following reasons:
&lt;ul&gt;
	&lt;li&gt;I believe your license is unclear at best.&lt;/li&gt;
    &lt;li&gt;Removal of the fix benefits you at the possible expense of thousands of other people.&lt;/li&gt;
	&lt;li&gt;Even if I removed the text, previous versions of this page will still be archived somewhere forever.&lt;/li&gt;
&lt;/ul&gt; 
What I will say however is that &lt;strong&gt;I strongly recommend removing the script per the author&#039;s wishes as opposed to modifying the code&lt;/strong&gt;.  I would further assume that this applies to &lt;b&gt;all of the code&lt;/b&gt;, so users cannot make any changes to it whatsoever.

With regard to your opinion about Google&#039;s perception of the hidden link I&#039;m afraid you are incorrect.  You did not choose to believe my rational argument before you knew my identity and I&#039;m actually surprised that now you know who I am you still fail to acknowledge my expertise in this matter.  Nonetheless, Google&#039;s language on this point is undeniable.  They do not give exceptions such as &quot;only if you use a &#039;none&#039; display property&quot;.  On the &lt;a href=&quot;http://www.google.com/support/webmasters/bin/answer.py?answer=40052&quot; rel=&quot;nofollow&quot;&gt;reasons to ban a site page&lt;/a&gt; they simply state, &quot;...writing text in such a way that it can be seen by search engines but not by users...&quot;.  Your hidden links do not in any way assist with usability issues, or have any positive benefit except to convey search benefits to your own site.  If Larry or Sergey were here they would ask &quot;what part of that did you not understand?&quot;

The difference here is that you only &quot;&lt;em&gt;think&lt;/em&gt; Google wouldn&#039;t persecute anyone&quot;, whereas I &lt;em&gt;know&lt;/em&gt; this is a real risk.  And it only takes a &lt;em&gt;single instance&lt;/em&gt; of a violation to cause this.  &lt;i&gt;I have seen it happen, more than once.&lt;/i&gt;

What bothers me so much about this particular issue:
&lt;ul&gt;
&lt;li&gt;You have, &lt;strong&gt;UN-knowingly&lt;/strong&gt; I&#039;m certain, put the blogs of a lot of people at risk.&lt;/li&gt;
&lt;li&gt;You have no moral high ground since you are extracting something in return for every install.  Your refusal to remove the hidden links demonstrates that you are unwilling to simply be charitable.&lt;/li&gt;
&lt;li&gt;At this point there is nothing you can personally do to &quot;fix&quot; that issue.  You couldn&#039;t possibly track down everyone and let them know of the potential risk.&lt;/li&gt;
&lt;li&gt;You fail to acknowledge the problem and have not yet volunteered to remove hidden linking from the plugin going forward.&lt;/li&gt;
&lt;li&gt;I have never seen this type of violation in any other plugin.  For any platform. Ever.&lt;/li&gt;
&lt;/ul&gt;
All of this is very unfortunate.  And I&#039;m sad to have been the one to notice the problem.  I don&#039;t want to be in the middle of this.  And what bothers me most is that you seem like a nice guy and I really appreciate the fact that you take pains to write accessible, valid code.  I bet we have far more in common than either of us realize.  But sadly Google doesn&#039;t give credit for being a nice guy.  

Finally, am I correct in assuming the reason you now care about my opinion is that Google lists this page immediately after yours in any search related to this form?

Sincerely,

John

PS - If you agree to permanently remove all hidden links from the plugin I&#039;ll clearly edit the very top of this post to note that going forward from a certain date the issue has been resolved.  I could also then advise people to update to the latest version rather than hacking the code.</description>
		<content:encoded><![CDATA[<p>Mike,</p>
<p>I&#8217;m glad you stopped by, and I welcome your comments and opinions.  You may feel free to write anything you like here and I&#8217;ll approve it, unaltered.</p>
<p>I&#8217;m confused by your assertion that the form is not open source.  The exact words I see on your page are &#8220;&#8230;no payment is required to use this <em>open source</em> script&#8230;&#8221;  Open Source software as defined by <a href="http://www.opensource.org/docs/definition.php" rel="nofollow">OpenSource.org</a> does not have restrictions against modification, re-distribution, or even resale.</p>
<p>Perhaps you meant something else?  But I can&#8217;t come up with any other words that could be accidentally confused with &#8220;open source&#8221;.  I can only take your words at face value, and I&#8217;m confident that any court would do the same.  If, <em>and only if</em>, my argument is correct, users would indeed be allowed by law to modify the script.  </p>
<p>I cannot in good conscience remove the fix I provided for the following reasons:</p>
<ul>
<li>I believe your license is unclear at best.</li>
<li>Removal of the fix benefits you at the possible expense of thousands of other people.</li>
<li>Even if I removed the text, previous versions of this page will still be archived somewhere forever.</li>
</ul>
<p>What I will say however is that <strong>I strongly recommend removing the script per the author&#8217;s wishes as opposed to modifying the code</strong>.  I would further assume that this applies to <b>all of the code</b>, so users cannot make any changes to it whatsoever.</p>
<p>With regard to your opinion about Google&#8217;s perception of the hidden link I&#8217;m afraid you are incorrect.  You did not choose to believe my rational argument before you knew my identity and I&#8217;m actually surprised that now you know who I am you still fail to acknowledge my expertise in this matter.  Nonetheless, Google&#8217;s language on this point is undeniable.  They do not give exceptions such as &#8220;only if you use a &#8216;none&#8217; display property&#8221;.  On the <a href="http://www.google.com/support/webmasters/bin/answer.py?answer=40052" rel="nofollow">reasons to ban a site page</a> they simply state, &#8220;&#8230;writing text in such a way that it can be seen by search engines but not by users&#8230;&#8221;.  Your hidden links do not in any way assist with usability issues, or have any positive benefit except to convey search benefits to your own site.  If Larry or Sergey were here they would ask &#8220;what part of that did you not understand?&#8221;</p>
<p>The difference here is that you only &#8220;<em>think</em> Google wouldn&#8217;t persecute anyone&#8221;, whereas I <em>know</em> this is a real risk.  And it only takes a <em>single instance</em> of a violation to cause this.  <i>I have seen it happen, more than once.</i></p>
<p>What bothers me so much about this particular issue:</p>
<ul>
<li>You have, <strong>UN-knowingly</strong> I&#8217;m certain, put the blogs of a lot of people at risk.</li>
<li>You have no moral high ground since you are extracting something in return for every install.  Your refusal to remove the hidden links demonstrates that you are unwilling to simply be charitable.</li>
<li>At this point there is nothing you can personally do to &#8220;fix&#8221; that issue.  You couldn&#8217;t possibly track down everyone and let them know of the potential risk.</li>
<li>You fail to acknowledge the problem and have not yet volunteered to remove hidden linking from the plugin going forward.</li>
<li>I have never seen this type of violation in any other plugin.  For any platform. Ever.</li>
</ul>
<p>All of this is very unfortunate.  And I&#8217;m sad to have been the one to notice the problem.  I don&#8217;t want to be in the middle of this.  And what bothers me most is that you seem like a nice guy and I really appreciate the fact that you take pains to write accessible, valid code.  I bet we have far more in common than either of us realize.  But sadly Google doesn&#8217;t give credit for being a nice guy.  </p>
<p>Finally, am I correct in assuming the reason you now care about my opinion is that Google lists this page immediately after yours in any search related to this form?</p>
<p>Sincerely,</p>
<p>John</p>
<p>PS &#8211; If you agree to permanently remove all hidden links from the plugin I&#8217;ll clearly edit the very top of this post to note that going forward from a certain date the issue has been resolved.  I could also then advise people to update to the latest version rather than hacking the code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cherim</title>
		<link>http://onemansblog.com/2007/03/21/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/comment-page-1/#comment-1930</link>
		<dc:creator>Mike Cherim</dc:creator>
		<pubDate>Sat, 07 Apr 2007 07:04:03 +0000</pubDate>
		<guid isPermaLink="false">http://onemansblog.com/2007/03/30/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/#comment-1930</guid>
		<description>Actually the form is &lt;strong&gt;not&lt;/strong&gt; open source, it is protected by copyright law in the US and abroad. If anyone follows your tutorial and removes the visually hidden back-links they are in violation of the law and if caught will be asked to discontinue the use of the form for starters. You should remove that as you really have no right to do that and if people do this they are hampering their ability to perform darg-and-drop updates. In fact I am formally asking you to remove that. 

If someone wants to, they can purchase a license to have those and all instances removed. This isn&#039;t spamdexing and I think Google wouldn&#039;t persecute anyone for using the form -- they&#039;re smart enough to know the difference. Moreover, the CSS display property &quot;none&quot; isn&#039;t being used which is what a Googlebot would focus on. 

We provide excellent support, the form is free, and it is a helluva lot of work keeping it up (we do lots of tweaks and improvements on a regular basis), and we&#039;re really providing a secure and accessible (to the disabled) contact solution for a lot of people. I don&#039;t why you&#039;re busting my chops over this. There &lt;em&gt;must&lt;/em&gt; be bigger fish to fry.</description>
		<content:encoded><![CDATA[<p>Actually the form is <strong>not</strong> open source, it is protected by copyright law in the US and abroad. If anyone follows your tutorial and removes the visually hidden back-links they are in violation of the law and if caught will be asked to discontinue the use of the form for starters. You should remove that as you really have no right to do that and if people do this they are hampering their ability to perform darg-and-drop updates. In fact I am formally asking you to remove that. </p>
<p>If someone wants to, they can purchase a license to have those and all instances removed. This isn&#8217;t spamdexing and I think Google wouldn&#8217;t persecute anyone for using the form &#8212; they&#8217;re smart enough to know the difference. Moreover, the CSS display property &#8220;none&#8221; isn&#8217;t being used which is what a Googlebot would focus on. </p>
<p>We provide excellent support, the form is free, and it is a helluva lot of work keeping it up (we do lots of tweaks and improvements on a regular basis), and we&#8217;re really providing a secure and accessible (to the disabled) contact solution for a lot of people. I don&#8217;t why you&#8217;re busting my chops over this. There <em>must</em> be bigger fish to fry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Man</title>
		<link>http://onemansblog.com/2007/03/21/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/comment-page-1/#comment-1138</link>
		<dc:creator>The Man</dc:creator>
		<pubDate>Mon, 26 Mar 2007 23:07:56 +0000</pubDate>
		<guid isPermaLink="false">http://onemansblog.com/2007/03/30/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/#comment-1138</guid>
		<description>Incidentally, someone e-mailed me and told me that I sound like a broken record.  :-)

There is an article archived at the W3C from over a decade ago in which I pointed out that Web browsers should have warning systems in them to notify when there is hidden text on a page.
http://lists.w3.org/Archives/Public/www-style/1997Jan/0077.html</description>
		<content:encoded><![CDATA[<p>Incidentally, someone e-mailed me and told me that I sound like a broken record.  :-)</p>
<p>There is an article archived at the W3C from over a decade ago in which I pointed out that Web browsers should have warning systems in them to notify when there is hidden text on a page.<br />
<a href="http://lists.w3.org/Archives/Public/www-style/1997Jan/0077.html" rel="nofollow">http://lists.w3.org/Archives/Public/www-style/1997Jan/0077.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Man</title>
		<link>http://onemansblog.com/2007/03/21/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/comment-page-1/#comment-972</link>
		<dc:creator>The Man</dc:creator>
		<pubDate>Thu, 22 Mar 2007 04:14:59 +0000</pubDate>
		<guid isPermaLink="false">http://onemansblog.com/2007/03/30/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/#comment-972</guid>
		<description>No problem Eric.  I thought this was important enough to let people know about.  I am worried however that not enough of the people that actually have it installed will learn about this.

Anyway, I&#039;ve changed my personal contact form over from the &lt;a href=&quot;http://ryanduff.net/&quot; rel=&quot;nofollow&quot;&gt;WP-Contact&lt;/a&gt; to a modified version of it called &lt;a href=&quot;http://kzkw.net/blog/2007/02/12/wp-contact-form-part-iii/&quot; rel=&quot;nofollow&quot;&gt;WP Contact Form III&lt;/a&gt;.

You might also look at the &lt;a href=&quot;http://www.joostdevalk.nl/code/wordpress/enhanced-contact-form/&quot; rel=&quot;nofollow&quot;&gt;Enhanced Contact Form&lt;/a&gt;, the &lt;a href=&quot;http://www.zirona.com/software/contact-form-encryption-wordpress/&quot; rel=&quot;nofollow&quot;&gt;Subrosa&lt;/a&gt; add on if you want encryption, and &lt;a href=&quot;http://adahas.com/work/intouch/&quot; rel=&quot;nofollow&quot;&gt;Intouch&lt;/a&gt; which offers the most customization.

If you find something else cool drop me a note and let me know!

Oh yeah, and if you needed two different forms to go to two different addresses keep in mind that you could just use a couple of these in combination.  :-)

John</description>
		<content:encoded><![CDATA[<p>No problem Eric.  I thought this was important enough to let people know about.  I am worried however that not enough of the people that actually have it installed will learn about this.</p>
<p>Anyway, I&#8217;ve changed my personal contact form over from the <a href="http://ryanduff.net/" rel="nofollow">WP-Contact</a> to a modified version of it called <a href="http://kzkw.net/blog/2007/02/12/wp-contact-form-part-iii/" rel="nofollow">WP Contact Form III</a>.</p>
<p>You might also look at the <a href="http://www.joostdevalk.nl/code/wordpress/enhanced-contact-form/" rel="nofollow">Enhanced Contact Form</a>, the <a href="http://www.zirona.com/software/contact-form-encryption-wordpress/" rel="nofollow">Subrosa</a> add on if you want encryption, and <a href="http://adahas.com/work/intouch/" rel="nofollow">Intouch</a> which offers the most customization.</p>
<p>If you find something else cool drop me a note and let me know!</p>
<p>Oh yeah, and if you needed two different forms to go to two different addresses keep in mind that you could just use a couple of these in combination.  :-)</p>
<p>John</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://onemansblog.com/2007/03/21/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/comment-page-1/#comment-969</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Thu, 22 Mar 2007 02:56:53 +0000</pubDate>
		<guid isPermaLink="false">http://onemansblog.com/2007/03/30/wordpress-secure-accessible-php-contact-form-v2-guilty-of-spamdexing/#comment-969</guid>
		<description>Thanks for the heads up.  I&#039;ve been checking out contact forms for Wordpress lately and will be careful to check the code twice before using this one.</description>
		<content:encoded><![CDATA[<p>Thanks for the heads up.  I&#8217;ve been checking out contact forms for WordPress lately and will be careful to check the code twice before using this one.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

