Spam detection
Jacob Kaplan-Moss
<li...@informa.tiker.net> wrote:
> I tried to submit this bug, but it wouldn't let me--it thought I'm a spammer.
Quoting from the ticket submission page:
"If you're getting rejected by the spam filter, we apologize! The best
way to avoid that is to register for an account and make sure you're
logged in."
The version on that page even has links.
Help me out here: how can I make it more obvious? You missed that;
others often do to. Can you share with me some insights on how you
missed it?
Jacob
Marc Fargas
> Help me out here: how can I make it more obvious? You missed that;
> others often do to. Can you share with me some insights on how you
> missed it?
The sentence should be more prominent, I know nobody that will read that
many lines, so maybe bolding "spam" and "register for an account" would
make those a bit more visible.
Next step would be on the reject message "PLEASE, PLEASE *REGISTER* FOR
AN ACCOUNT TO AVOID BEING REJECTED BY *SPAM* FILTER". Not sure avoid the
caps...
Maybe point 1 is enough.
Regards,
Marc
--
http://www.marcfargas.com -- will be finished some day.
Waylan Limberg
> El jue, 26-06-2008 a las 13:31 -0700, Jacob Kaplan-Moss escribió:
>> Help me out here: how can I make it more obvious? You missed that;
>> others often do to. Can you share with me some insights on how you
>> missed it?
>
> The sentence should be more prominent, I know nobody that will read that
> many lines, so maybe bolding "spam" and "register for an account" would
> make those a bit more visible.
Yeah, it does kind of get lost in the text there. The first few lines
basically say "be sure you actually have an unreported bug."
Presumably, the potential reporter thinks: "Yeah, Yeah, I've been
through that before so why should I read every point in that list
carefully?"
True, first time reporters to any project probably should read that,
but obviously they don't. Personally, I alway look for a "register"
link in the menu - usually in close proximity to the "Login" link. I'd
suggest (and have in the past) that a "Register" link be added to
every Trac page right next to the "Login" and "Settings" links up in
the top right corner.
If that doesn't work - then perhaps a dancing animation across the
newticket page. Ok, maybe not. :-D
--
----
Waylan Limberg
way...@gmail.com
Mike Scott
I think its the fact that we see "internal server error" and just miss
the message which is very nicely hidden after it.
Alot of django developers know what a 500 means, but generally don't
expect to see it for a spam block.
Maybe the page after the block submission needs to be changed. And
maybe you could output a copy of the submitted text too just incase
you didn't have a copy written elsewhere.
--
Woody Allen - "I am not afraid of death, I just don't want to be
there when it happens."
Collin Grady
> Maybe the page after the block submission needs to be changed. And
> maybe you could output a copy of the submitted text too just incase
> you didn't have a copy written elsewhere.
Something wrong with your browser's back button? :)
--
Collin Grady
Stay together, drag each other down.
Steve Holden
> On Thu, Jun 26, 2008 at 1:06 PM, Andreas Klöckner
> <li...@informa.tiker.net> wrote:
>
>> I tried to submit this bug, but it wouldn't let me--it thought I'm a spammer.
>>
>
> Quoting from the ticket submission page:
>
> "If you're getting rejected by the spam filter, we apologize! The best
> way to avoid that is to register for an account and make sure you're
> logged in."
>
>
is being rejected due to lack of authentication, presumably this is
supposed to mislead spammers?
Why not begin the message with:
"Did you register an account and log in before submitting your issue?
Non-registration is the most common cause of this error. Please click
here to register an account before submitting this issue."
Or something similar.
regards
Steve
Rob van der Linde
to register for an account. I had to ask in the IRC and someone had to
point me to it, I believe this could be made easier to find.
Go to code.djangoproject.com look at the tabs:
Login | Settings
Wiki, Timeline, Browse Source, Reports, View Tickets, New Ticket,
Roadmap, Search.
Where is the register link?? I recently setup Trac on my own server, and
although I am very new to Trac, I installed the registration plugin and
my tabs say:
Login | Settings | Help/Guide | About Trac | Register
Wiki, Timeline, Roadmap, Browse Source, View Tickets, Search.
I think you need to make the registration page more obvious, people
currently have to hunt for it. I'm not sure how the link to the
registration page was even removed as my accounts plugin for Trac put it
in there automatically.
The method I use to combat spam is only allow people to file tickets and
edit the Wiki if they create an account, and the register link is easily
visible at the top of the site. Also, I used a captcha plugin on the
registration page (I had to actually patch it into the accounts plugin,
but it was very easy).
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups "Django developers" group.
> To post to this group, send email to django-d...@googlegroups.com
> To unsubscribe from this group, send email to django-develop...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/django-developers?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
Rob van der Linde
ticket, but why not put it on page where the login/settings links are
(just underneath the search box). This is where it is by default in Trac
and people might expect to see it there, like I did myself initially.
rskm1
> others often do to. Can you share with me some insights on how you
> missed it?
* If it's going to fail _ANYWAY_, just GRAY IT OUT!!
In other words, make the form-input fields of the http://code.djangoproject.com/simpleticket
page simply NOT APPEAR, or be DISABLED, if there is no user logged-in.
That would make the message about registering and being logged-in
pretty much IMPOSSIBLE to miss =). And nobody will ever again see the
error page about attempting to create a new ticket anonymously.
Tom Tobin
+1; this makes worlds of sense. :-)
Gary Wilson Jr.
> Help me out here: how can I make it more obvious?
Wow, you've certainly made it more obvious :) I pity the fool that
misses it now.
Gary
Steve Holden
... and why not have it say "Your post *will* be rejected as spam unless
you are registered and logged in"? At the moment it sounds like you
*might* get away with an unregistered posting.
regards
Steve
--
Steve Holden +1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/
Karen Tracey
... and why not have it say "Your post *will* be rejected as spam unlessRob van der Linde wrote:
> I see there is now a link to the registration page when you go to file a
> ticket, but why not put it on page where the login/settings links are
> (just underneath the search box). This is where it is by default in Trac
> and people might expect to see it there, like I did myself initially.
you are registered and logged in"? At the moment it sounds like you
*might* get away with an unregistered posting.
Because it is not true that you *will* be rejected by the spam filter if you are not registered. There are still plenty of anonymous updates to trac. I don't know what fraction of anonymous postings are rejected as spam, but it is not 100%
Karen