Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

(Yes, a very excellent response, Haj ... thanks for sharing.)

Another strategy that I have used with good success is to fairly-quickly kick users who have had too many unsuccessful login attempts over to an alternative login-screen same URL, different content which requires a "captcha."   (Although Mother Google is probably the easiest source of captchas, I doubt it really matters much.)   It’s fine to add some text explaining to the human user why you are doing this ... robots will never read it anyway.)   Of course, thanks to CPAN, the actual implementation requires no thought.

Having forced them over to this alternative login screen, I would make them successfully complete it two or three times before relenting and letting them go back to the old way.

I frankly think that this will ultimately be more effective, and considerably easier to implement, than the strategy you are now contemplating.   (I generally think of these to be better reserved for denial-of-service attacks.)

I would also counsel making "captchas" a mandatory feature of your "sign up for an account" screens, if you allow arbitrary users to do so.   I have about 9,000(!) "junk" user-ids dating from before I did this.   (How they all managed to respond to the mandatory account-validation emails, I have no idea ...)

In reply to Re: RFC / Audit: Mojo Login Example by sundialsvc4
in thread RFC / Audit: Mojo Login Example by haukex

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others imbibing at the Monastery: (3)
As of 2021-10-27 17:20 GMT
Find Nodes?
    Voting Booth?
    My first memorable Perl project was:

    Results (94 votes). Check out past polls.