Opened 18 years ago
Closed 18 years ago
#3629 closed defect (worksforme)
Akismet filter is much too restrictive
Reported by: | Christian Boos | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | general | Version: | devel |
Severity: | major | Keywords: | akismet |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Well, I tried to do the following change on TracChangeset, from:
The last possibility for examining changes is to have a use the ''Last Change'' link provided by the TracBrowser.
to:
The last possibility for examining changes is to use the ''Last Change'' link provided by the TracBrowser.
but forgot to login… then I got the "Akismet rejected change" error message.
If this happens for such minor changes, I wonder how much contributions we still can get from our users…
Compared this with spam which still gets in despite the filter (comment:ticket:1459:28), and I wonder how effective the Akismet filter really is…
So maybe we should try to find a better anti-spam system, and quickly disable Akismet which prevents valid contributions.
Attachments (0)
Change History (7)
comment:1 by , 18 years ago
comment:3 by , 18 years ago
I just experienced the same issue: unable to comment until I've logged in (original comment:ticket:3327:10)
comment:7 by , 18 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Well, seems to work again for me too ;)
False alarm, due to a temporary issue on the Akismet side (http://article.gmane.org/gmane.comp.version-control.subversion.trac.devel/868)
— Christian
The change in question: http://trac.edgewall.org/wiki/TracChangeset?action=diff&version=13
(same thing for this comment: I first tried as anonymous, and bam, "Akismet rejected spam" again…)