Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: Broken? http://www.postgresql.org/about/
Date: Thu, 17 Nov 2005 16:18:37 -0000
Message-ID: 
 <E7F85A1B5FF8D44C8A1AF6885BC9A0E4E7E10C@ratbert.vale-housing.co.uk>
Thread-Topic: [pgsql-www] Broken? http://www.postgresql.org/about/
Thread-Index: AcXrkb8HQAt79i5KSyywOmN/jtAXlgAAEegA
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "Robert Treat" <xzilla@users.sourceforge.net>
Cc: <gevik@xs4all.nl>,
	<pgsql-www@postgresql.org>

=20

> -----Original Message-----
> From: Robert Treat [mailto:xzilla@users.sourceforge.net]=20
> Sent: 17 November 2005 16:12
> To: Dave Page
> Cc: gevik@xs4all.nl; pgsql-www@postgresql.org
> Subject: Re: [pgsql-www] Broken? http://www.postgresql.org/about/
>=20
> On Thu, 2005-11-17 at 05:28, Dave Page wrote:
> > BTW, how goes the form submission verification?
> >=20
>=20
> I heard an interesting twist on this... rather than doing image
> verification, you instead reject submissions that come from page that
> don't contain a postgresql.org refferrer on the submission page. The
> idea being the spam bots post directly to the submission=20
> page, but users
> navigate thier way into the page. simple (and transparent to the user)
> but apparently very effective for some folks that have=20
> implemented it.=20

Sounds like a good idea, except legitimate clients might not send it (I
don't know off-hand if any do offer a way to stop it, but it seems like
a sensible privacy option). Also I imagine it would be really easy to
add it to the spam bots, so I doubt it'll be long before it stops
working for them as well.

Regards, Dave.