On Fri, 24 Sep 2010, Joshua Juran wrote:
Network Solutions (and the InterNIC before it) has had the poor taste to write
domains in all uppercase, e.g. jju...@gmail.com, as if the Internet had
started on VMS rather than Unix. Except they don't upcase the local part of
email addresses, so at
This is a variation on the brain-damaged credit card number input
field (where they couldn't be bothered to add one line of code to
filter out spaces, but go to the effort to document this limitation --
or not) that you all know and hate.
This time it's a phone number. The difference is
On Thu, 23 Sep 2010, Joshua Juran wrote:
P.S. Adding '$num =~ s/[() -]//g' before the validation would be
prohibitively invasive and costly. Of course, gratuitously converting my
email address to all caps (in violation of every version of the standard) is
no problem.
I recently found that
On Fri, Sep 24, 2010 at 08:59:53AM +0100, Bob Walker wrote:
I recently found that in our work software that even though we use
email addresses as the username we dont actually check this properly
so an.exam...@example.com and an.exam...@example.com can be different
users. This has confused
On 24/09/10 04:03 AM, Roger Burton West wrote:
On Fri, Sep 24, 2010 at 08:59:53AM +0100, Bob Walker wrote:
I recently found that in our work software that even though we use
email addresses as the username we dont actually check this properly
so an.exam...@example.com and
On Fri, Sep 24, 2010 at 10:11, Numien num...@deathwyrm.com wrote:
Yes, but knowing the trend in case-sensitivity, an.exam...@example.com
is likely also not the same as an.exam...@example.com... which should be.
And it should also be the same as
an . example @ example (this is not a real
On Sep 24, 2010, at 1:11 AM, Numien wrote:
On 24/09/10 04:03 AM, Roger Burton West wrote:
On Fri, Sep 24, 2010 at 08:59:53AM +0100, Bob Walker wrote:
I recently found that in our work software that even though we use
email addresses as the username we dont actually check this
properly
so
