|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #70336 Bogus/wrong error message "please don't spam our bug tracker" message
Submitted: 2015-08-23 23:44 UTC Modified: 2015-08-24 01:47 UTC
Avg. Score:1.0 ± 0.0
Reproduced:0 of 1 (0.0%)
From: teo8976 at gmail dot com Assigned:
Status: Not a bug Package: Website problem
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: teo8976 at gmail dot com
New email:
PHP Version: OS:

Further comment on this bug is unnecessary.


 [2015-08-23 23:44 UTC] teo8976 at gmail dot com
I was trying to comment on a bug and I used the expression "don't give a ****", with the actual "f word" instead of the ****.

A part from the questionable use of unelegant language, my comment was completely legitimate.

As a result, when trying to post the comment I kept getting the message "Please don't SPAM our website" (or something like that).

At first I thought it was the wrong captcha (my fault, the error message for that is different and clear enough), but then I had a hard time figuring out what the problem was.

I thought I might be being blocked because of "too many" comments from the same email address, so I tried another. Then I tried another browser.

The bottom line is that I WASTED A LOT OF TIME just because of a poorly phrased error message. The error message should say "We don't allow the word XXXX", or at least "Please don't use profanity" or the like.

And don't tell me that would help spammers to work around the antispam filter, because obviously spam comes from spambots, not human beings.

This reminds me of
Seriously, this is the only bug tracker where I haver seen this kind of stuff.

Suggestion: if users had to register and login in order to file bugs (with email verification and captcha whenever necessary, real captcha I mean), as happens in EVERY OTHER bug tracker I've ever seen, you wouldn't need stupid word-based filters with such a high rate of false positive (nor would you have to trade it off with the rate of actual spam blocking).


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2015-08-24 01:39 UTC]
-Status: Open +Status: Not a bug
 [2015-08-24 01:39 UTC]
You have to much time on your hands.
 [2015-08-24 01:47 UTC]
-Block user comment: No +Block user comment: Yes
PHP Copyright © 2001-2023 The PHP Group
All rights reserved.
Last updated: Thu Nov 30 22:01:27 2023 UTC