How do I get past this? > Your password is not unsafe
There's nothing to get past. Your password is not unsafe, which is what you want, you're good. Just click next.
User Inyerface – A worst-practice UI experiment
111–120 of 222 posts
Re: User Inyerface – A worst-practice UI experiment
#112Only thing missing is deleting everything you entered into the entire form any time there is an error message
And an obnoxious GDPR message with intentionally confusing sliders (am i disabling all tracking or enabling all tracking? Why is the ‘accept all’ button in the placement of the ‘accept’ button, why can I not just hide this form and not complete it at all)
Re: User Inyerface – A worst-practice UI experiment
#113Only thing missing is deleting everything you entered into the entire form any time there is an error message
[deleted]
Re: User Inyerface – A worst-practice UI experiment
#11403:51 I laughed out loud when I got to the bottom of the last page and didn't see checkboxes and realized the checkboxes were above the pictures and not below and had to scroll to the top.
I noticed that after a few seconds, but I had to go though like 8 screens and it took 3+ minutes.... Did I just keep getting the Captcha choices wrong?
For all the captchas on this site you have to check every box, IIRC.
Re: User Inyerface – A worst-practice UI experiment
#115Missed one worst-practice: I was able to paste a password
Re: User Inyerface – A worst-practice UI experiment
#116Earlier quoted context omitted.
My email address has a dash in the domain and it's remarkable how many sites (and big ones, too!) reject it as an invalid domain. Discover.com, for example, rejected it when I did a card application, but disabling JavaScript let it go through on the server-side validation. Bloody weird.
Lots of websites reject email addresses at entirely valid domain names as invalid, too, such as any at some of the new TLDs like .email.
Yep. One of our salespeople had a fit because a prospect couldn't get emails from him. The return message said "we do not accept email from the .io top level domain".
Re: User Inyerface – A worst-practice UI experiment
#117I rage-quit when I couldn't scroll the T&C fast enough. I guess my patience has gotten a lot worse as I have gotten older.
Re: User Inyerface – A worst-practice UI experiment
#118Nice touch pre-scrolling the terms, and making it scroll up quickly but down slowly
Re: User Inyerface – A worst-practice UI experiment
#119Couldn't do it. Burn everything that does this.
Re: User Inyerface – A worst-practice UI experiment
#120Earlier quoted context omitted.
Really the entire idea of client/server-side email "validation" kind of seems like an ancient, cockroach-like anti-pattern that is impossible to stamp out. Like, what is the problem they're even solving? One validates email addresses by sending an email with a token the user then acts on. There are useful things to do with emails, like checking against already registered ones (including any blacklists), but I can't t…
> what is the problem they're even solving? The problem they're solving is that a lot of people just enter their email wrong and then wonder why they didn't get the signup email. > Like if someone tries to register an already registered email, send an email about it don't leak that it's registered. This is something that's cargo-culted far too often. Maybe for some services it's worth keeping secret which emails are…
I'd prefer to just have it. Seems decently important for me privacy wise. I as a customer don't want others to be able to test whether I have signed up somewhere and also it is much better security wise and not leaking business data.
And most times, it is standard practice to hide sign ups, luckily.