News for hackers. Stuff that matters.
Re:Gail.com by amursft on Sunday December 22, 2019 @12:01AM (#21855302)
When your blog is getting beat by a typo website to the tune of thousands of visitors a day...

I love old-style internet websites like this. It makes me happy they haven't sold it and share some of the numbers.

Re:Gail.com by Operyl on Sunday December 22, 2019 @12:27AM (#21855381)
I found the 1.2 million bounces per week from typos even more amazing.
Re:Gail.com by paranoidrobot on Sunday December 22, 2019 @01:32AM (#21855623)
I helped run the infrastructure for a reasonably large site. Occasionally while debugging an issue I'd be looking through our outbound delay queue -- sure enough, there'd be at least a dozen typo variations of gmail, yahoo, hotmail sitting there waiting to time out. And these were for customers who'd made an actual purchase and entered their email address twice.

Definitively proving that 'please confirm your email address' fields are not nearly as effective as the designers thought it would be.

Re:Gail.com by boring_twenties on Sunday December 22, 2019 @01:36AM (#21855634)
On an unrelated note, fuck those fields. That is all.

edit: OK that's not all. Anyone else who's sick of websites interfering with your copy/paste operations, find dom.event.clipboardevents.enabled in about:config and set it to false. HTH.

Re:Gail.com by kohtatsu on Sunday December 22, 2019 @01:54AM (#21855688)
I imagine GP was not specifically talking about paste-disabled confirm-email fields, rather just confirm email fields in general.
Re:Gail.com by boring_twenties on Sunday December 22, 2019 @02:03AM (#21855718)
I don't think I've ever seen one that wasn't paste-disabled, though my knowledge is way out of date since I found out about the aforementioned config setting.
Re:Gail.com by paranoidrobot on Sunday December 22, 2019 @04:32AM (#21856152)
Well in our case paste wasn't disabled.

It was definitely a case of a PM coming up with a quick and cheap 'fix' to the problem of getting so many people typing their email address wrong the first time.

We (from the tech side) put together a bunch of options, including validating the domain and giving the user feedback if delivery doesn't succeed immediately. But it was put on a backlog of 'nice things to implement' and never delivered.