Slick. Anyone interested in including this in contrib?
On Mar 23, 6:35 pm, "SmileyChris" <[EMAIL PROTECTED]> wrote:
> On Mar 24, 7:37 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> wrote:
>
> > Just an idea, but maybe someone could make a new field class that
> > encapsulates a hidden HTML input
On Mar 23, 10:46 pm, "Amit Upadhyay" <[EMAIL PROTECTED]> wrote:
> But the original poster gave me this idea: would it be useful to have a
> field which specifically disallows auto-complete. May be an optional
> argument for CharField? [HTML allows to do a autocomplete=off in input
> fields].
You
On Mar 24, 7:37 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> Just an idea, but maybe someone could make a new field class that
> encapsulates a hidden HTML input element (hidden by style) that has no
> label, and the developer can name it something conspicuous (like
> `email`). The end re
Just an idea, but maybe someone could make a new field class that
encapsulates a hidden HTML input element (hidden by style) that has no
label, and the developer can name it something conspicuous (like
`email`). The end result of this field could be that if any content
gets put into it, the form
On Mar 23, 8:08 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Fri, 2007-03-23 at 06:48 +, Baptiste wrote:
> > That feature would be unable by default, and the user could use it
> > just for forms which didn't need to be autocompleted, eg. a comment
> > form (which can use cookies to
I tried hacking around with newforms, to implement part of my Stopping
Spambots with Hashes and Honeypots
(http://www.nedbatchelder.com/text/stopbots.html). My approach was to
create a BotProofForm class which would wrap an instance of an ordinary
form. This let me rename fields without chan
On 3/22/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
>
> On Fri, 2007-03-23 at 06:48 +, Baptiste wrote:
> > That feature would be unable by default, and the user could use it
> > just for forms which didn't need to be autocompleted, eg. a comment
> > form (which can use cookies to rememb
On Fri, 2007-03-23 at 06:48 +, Baptiste wrote:
> That feature would be unable by default, and the user could use it
> just for forms which didn't need to be autocompleted, eg. a comment
> form (which can use cookies to remember the user, it is really more
> powerful).
Autocomplete isn't just
That feature would be unable by default, and the user could use it
just for forms which didn't need to be autocompleted, eg. a comment
form (which can use cookies to remember the user, it is really more
powerful). For the form which need it, like search forms, just no
parameter scramble, and all w
On Thu, 2007-03-22 at 23:05 -0400, Jeremy Bowers wrote:
> Malcolm Tredinnick wrote:
> > I really don't like this approach to spam prevention as a general
> > measure.
> I would suggest a better approach would be to make it easier to include
> a single randomized/hashed hidden input in the form, a
Malcolm Tredinnick wrote:
> I really don't like this approach to spam prevention as a general
> measure.
I would suggest a better approach would be to make it easier to include
a single randomized/hashed hidden input in the form, and make it easy to
verify the return of that input through middle
On Thu, 2007-03-22 at 21:06 +, Baptiste wrote:
> Hello all,
>
> (Please apologize my bad English, don't mind about it and try to
> understand... I'll do my best !)
>
> First, have a quick look on the spammer main method - I am talking
> about bots, not human spammers that can't be filtered -
In fact, after thinking more about it, I believe that it would be
better to add the salt to BoundField, not to the form.
That would be easier to use and to implement and would imply a method,
called in the BaseForm before the conversion of data in BoundFields,
which would "desalt" each key in the
Hello all,
(Please apologize my bad English, don't mind about it and try to
understand... I'll do my best !)
First, have a quick look on the spammer main method - I am talking
about bots, not human spammers that can't be filtered - : POST data
are sent to the server with classical names of field
14 matches
Mail list logo
