Thread: Replacing @ with " at "
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I edited buildnews.php and buildevents.php to replace @ signs with " at "
(omitting the quotes) to avoid spam, as proposed by Christopher
Kings-Lynne. Dave, should it be committed to CVS?
I saw something on index.php; but I'm not sure that it works:
ereg_replace("@", "@", pg_result($rs, $x, "posted_by"))
Regards,
- --
Devrim GUNDUZ
devrim@gunduz.org devrim.gunduz@linux.org.tr
http://www.TDMSoft.com
http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE/0E+Ctl86P3SPfQ4RAgKmAJ9g7xESeD1/u5EIH6zhX1jOHiWRkgCfQ5jS
YX3Q7MTsBolZezdOFs6IBH0=
=EkoJ
-----END PGP SIGNATURE-----
> -----Original Message-----
> From: Devrim GUNDUZ [mailto:devrim@gunduz.org]
> Sent: 05 December 2003 09:27
> To: PostgreSQL WWW Mailing List
> Subject: [pgsql-www] Replacing @ with " at "
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Hi,
>
> I edited buildnews.php and buildevents.php to replace @ signs
> with " at "
> (omitting the quotes) to avoid spam, as proposed by
> Christopher Kings-Lynne. Dave, should it be committed to CVS?
Thanks Devrim, commited.
> I saw something on index.php; but I'm not sure that it works:
>
> ereg_replace("@", "@", pg_result($rs, $x, "posted_by"))
That was done by Greg Sabino Mullane
Regards, Dave.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On Fri, 5 Dec 2003, Dave Page wrote:
> > I saw something on index.php; but I'm not sure that it works:
> >
> > ereg_replace("@", "@", pg_result($rs, $x, "posted_by"))
>
> That was done by Greg Sabino Mullane
hmm. I've edited index.php, and it seems ok now.
http://www.postgresql.org/index.php
I've also edited news.php and event.php. Dave, could you please commit all
three files to CVS?
BTW: index.php and index.html are not in sync for hours. IS there a
problem?
Regards,
- --
Devrim GUNDUZ
devrim@gunduz.org devrim.gunduz@linux.org.tr
http://www.TDMSoft.com
http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE/0GoPtl86P3SPfQ4RAj1/AKC0lpJe7vT9hmRtuLXluei23TtaEQCfV4Fj
Sh0tVjCxumH3RiEa3zKgKPc=
=lmav
-----END PGP SIGNATURE-----
> -----Original Message-----
> From: Devrim GUNDUZ [mailto:devrim@gunduz.org]
> Sent: 05 December 2003 11:21
> To: Dave Page
> Cc: PostgreSQL WWW Mailing List
> Subject: Re: [pgsql-www] Replacing @ with " at "
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Hi,
>
> On Fri, 5 Dec 2003, Dave Page wrote:
>
> > > I saw something on index.php; but I'm not sure that it works:
> > >
> > > ereg_replace("@", "@", pg_result($rs, $x, "posted_by"))
> >
> > That was done by Greg Sabino Mullane
>
> hmm. I've edited index.php, and it seems ok now.
>
> http://www.postgresql.org/index.php
>
> I've also edited news.php and event.php. Dave, could you
> please commit all three files to CVS?
Thanks, committed.
> BTW: index.php and index.html are not in sync for hours. IS
> there a problem?
I just ran it manually and it went OK.
BTW; I have now added a build/buildpage script to rebuild just a single
page.
Usage:
$ build/buildpage /index
Unless you are root it'll fail to do the chown at the end, but it should
build OK.
Regards, Dave.
On Friday 05 December 2003 06:20, Devrim GUNDUZ wrote:
> On Fri, 5 Dec 2003, Dave Page wrote:
> > > I saw something on index.php; but I'm not sure that it works:
> > >
> > > ereg_replace("@", "@", pg_result($rs, $x, "posted_by"))
> >
> > That was done by Greg Sabino Mullane
>
> hmm. I've edited index.php, and it seems ok now.
>
> http://www.postgresql.org/index.php
>
> I've also edited news.php and event.php. Dave, could you please commit all
> three files to CVS?
>
I have an issue with the way this was done. The email addresses were left as
links, but the links aren't valid (pops up in your email as foo at bar.com.
Theres a couple solutions to this:
1) Don't make the email address a link
2) make the mailto be a valid link, but the words on the page not
3) add a checkbox to the submit page to "obfuscate email", so that s/@/at, and
not a link, or we'll leave in @ and make it a link.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On Fri, 5 Dec 2003, Robert Treat wrote:
> I have an issue with the way this was done. The email addresses were left as
> links, but the links aren't valid (pops up in your email as foo at bar.com.
> Theres a couple solutions to this:
>
> 1) Don't make the email address a link
This was what I was thinking now :) I vote for this one.
What do the other guys think? BTW, mailto links in event/news details does
not work.
Regards,
- --
Devrim GUNDUZ
devrim@gunduz.org devrim.gunduz@linux.org.tr
http://www.TDMSoft.com
http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE/0H2Dtl86P3SPfQ4RAhj2AKCbJwqrHtAPTVfg/3Urisnb8KPfxQCeNBnI
+MWmZbejdwbCt1Lqkk6VhJI=
=TxsJ
-----END PGP SIGNATURE-----
On Friday, December 5, 2003, at 09:34 PM, Robert Treat wrote: > Theres a couple solutions to this: > > 1) Don't make the email address a link > 2) make the mailto be a valid link, but the words on the page not > 3) add a checkbox to the submit page to "obfuscate email", so that > s/@/at, and > not a link, or we'll leave in @ and make it a link. As for 2, if the mailto is literal text in the html, a spambot is going to pick it up regardless—my guess is it's even more likely to pick up a mailto: link than just a address elsewhere on the page. I know there are ways of obfuscating the email address using Javascript (such as Hiveware's Enkoder http://www.hiveware.com/enkoder.php for Mac OS X. Pretty cool, as it even varies the Javascript so bots have more trouble learning it. I know someone a lot smarter than me can figure out how to turn this into a server-side solution, and I'm sure someone probably already has.) 1 & 3 seem fine, though it would be nice of the mailto: worked as a link. Michael Glaesemann grzm myrealbox com
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > As for 2, if the mailto is literal text in the html, a spambot is going > to pick it up regardless�my guess is it's even more likely to pick up a > mailto: link than just a address elsewhere on the page. I know there > are ways of obfuscating the email address using Javascript Indeed: http://www.turnstep.com/Spambot/avoidance.html Almost any change has an amazing rate of return: while a spambot can be simply changed to pick up things like greg "at" turnstep.com, there is so much low-hanging fruit around that few if any bother. Glad to see this is finally being changed. But we need to remove the mailto link and make it a simple text. I will propose one final thing: changing press at postgresql.org to something else, as that email is likely to get lots of spam for many years to come at this point. :( - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200312051936 -----BEGIN PGP SIGNATURE----- iD8DBQE/0SUTvJuQZxSWSsgRAq/bAKDtoQACEHU3W/ljgG9LAhPO+Bj47QCfQdH0 Idtv09t5QMx8RVt3py4453Q= =9GIw -----END PGP SIGNATURE-----
On Sat, 6 Dec 2003 greg@turnstep.com wrote: > I will propose one final thing: changing press at postgresql.org to > something else, as that email is likely to get lots of spam for many > years to come at this point. :( all the mailing lists are run through Spamassassin, which seems to trap most of the garbage ... press@ doesn't get much dump'd into the moderators mailbox ... 20 a week, maybe ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
----- Original-Nachricht -----
Von: "Robert Treat" <xzilla@users.sourceforge.net>
An: Devrim GUNDUZ <devrim@gunduz.org>, Dave Page <dpage@vale-housing.co.uk>
CC: PostgreSQL WWW Mailing List <pgsql-www@postgresql.org>
Datum: Friday, December 05, 2003 01:37 PM
Betreff: [pgsql-www] Replacing @ with " at "
> I have an issue with the way this was done. The email addresses were left as
> links, but the links aren't valid (pops up in your email as foo at bar.com.
> Theres a couple solutions to this:
>
> 1) Don't make the email address a link
> 2) make the mailto be a valid link, but the words on the page not
> 3) add a checkbox to the submit page to "obfuscate email", so that s/@/at, and
> not a link, or we'll leave in @ and make it a link.
Is there any reason why we must show the email address? Of course, we need that adresses in our database to manage the
news,but do we have to show it to the visitors? Why not simply let the submitters input their name and then show this?
If we want the visitors to be able to send mails to the submitter, we can provide a simple email form
(sendmail.php?to=newsposter&id=123or something like this) so nobody will ever see the mail address...
> Robert Treat
> --
> Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
Mit freundlichen Grüßen
Andreas Grabmüller
--
LetzPlay.de
| Freemail: http://www.letzplay.de/mail
| Forenhosting: http://www.letzplay.de/foren
On Saturday 06 December 2003 05:06, Andreas Grabmller wrote:
> ----- Original-Nachricht -----
> Von: "Robert Treat" <xzilla@users.sourceforge.net>
> An: Devrim GUNDUZ <devrim@gunduz.org>, Dave Page <dpage@vale-housing.co.uk>
> CC: PostgreSQL WWW Mailing List <pgsql-www@postgresql.org>
> Datum: Friday, December 05, 2003 01:37 PM
> Betreff: [pgsql-www] Replacing @ with " at "
>
> > I have an issue with the way this was done. The email addresses were
> > left as links, but the links aren't valid (pops up in your email as foo
> > at bar.com. Theres a couple solutions to this:
> >
> > 1) Don't make the email address a link
> > 2) make the mailto be a valid link, but the words on the page not
> > 3) add a checkbox to the submit page to "obfuscate email", so that
> > s/@/at, and not a link, or we'll leave in @ and make it a link.
>
> Is there any reason why we must show the email address? Of course, we need
> that adresses in our database to manage the news, but do we have to show it
> to the visitors? Why not simply let the submitters input their name and
> then show this?
>
as long as we allow news items for all kinds of sub/side projects related to
postgresql, i think we ought to have some kind of distinction that these
items are not coming from the core project itself.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> I will propose one final thing: changing press at postgresql.org to >> something else, as that email is likely to get lots of spam for many >> years to come at this point. :( > all the mailing lists are run through Spamassassin, which seems to trap > most of the garbage ... press@ doesn't get much dump'd into the moderators > mailbox ... 20 a week, maybe ... I am not sure I understand the point here. Are you saying that all those posts to the press email are ones that have slipped through the spamassassin filter? Whatever the system that is in place, the press list is currently overrun with spam - I did a quick count and got a ratio of about 100 spams for every couple of real messages. If we were to change the email address to "contact" and not publish that on the main web page, I am sure that ratio would decrease dramatically. - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200312072218 -----BEGIN PGP SIGNATURE----- iD8DBQE/0+4kvJuQZxSWSsgRArYQAKD2M/CBUQ8+oKbzFZZ4X4MS/gqmBwCfdVI+ FOpYVM15bhgxLuIJ3Foks/A= =/8Kn -----END PGP SIGNATURE-----
On Mon, 8 Dec 2003 greg@turnstep.com wrote: > I am not sure I understand the point here. Are you saying that all those > posts to the press email are ones that have slipped through the > spamassassin filter? Whatever the system that is in place, the press > list is currently overrun with spam - I did a quick count and got a > ratio of about 100 spams for every couple of real messages. If we were > to change the email address to "contact" and not publish that on the > main web page, I am sure that ratio would decrease dramatically. Huh? I'm on the press@ mailing list, and I see an occasional posting to it, but that is it ... ah, shit, that would explain it ... My anti-spam filter is cleaning them out ... will take a look at why the ones "pre-list" aren't picking it out this week ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664