 | | Re: Enhanced verification (was: Re: What the F.......)
|
|
(...) To clarify: Yes on the cookie, no on the temporary part. Could be temporary or permanent, hence the lack of requirement on it being temporary. --Todd (27 years ago, 14-Dec-99, to lugnet.admin.general)
|
| |
 | | Re: Enhanced verification (was: Re: What the F.......)
|
|
(...) It would allow Brad to say to the system, "Hey, don't let anyone post to the system using From: Brad Justus <legodirect@lego.com> unless it was actually Brad Justus (as verified by his ID & password). (...) No. (...) No, not unless you wanted (...) (27 years ago, 14-Dec-99, to lugnet.admin.general)
|
| |
 | | Re: Enhanced verification (was: Re: What the F.......)
|
|
<snip> (...) I like this idea although I don't understand how it would help in terms of the issue we are currently discussing. Would this require someone to sign in once a day the first time they go to LUGNET? If so does that mean you would be using (...) (27 years ago, 14-Dec-99, to lugnet.admin.general)
|
| |
 | | Re: Enhanced verification (was: Re: What the F.......)
|
|
I think the voluntary passwd option is a good one. I too would like the option of only posting through the web interface after loggin in. You could even use the existing cookie system to reduce the burden on the user. KL (27 years ago, 14-Dec-99, to lugnet.admin.general)
|
| |
 | | Re: Help: Re: review: LEGO '99
|
|
(...) I'd be happy with LS#\d+ as the standard way to write the set numbers. Unlike URLs, there's not any confusion over whether a . is part of the URL or not, etc. Todd, you mentioned that lego set numbers are actually strings. Do they contain (...) (27 years ago, 14-Dec-99, to lugnet.admin.general)
|