14
Seems like it's an issue for potential new joiners
this post was submitted on 09 Apr 2025
14 points (93.8% liked)
Fedibridge
563 readers
118 users here now
A community to organize and discuss the growth of the fediverse as a whole
Related communities
Megathreads
founded 2 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Tbh I kinda agree with this comment:
I've said it before, we need the lowest possible barrier to entry possible if we are to be successful at attracting users in greater numbers, especially casual ones (which are desperately needed here).
I was surprised by the comment about contrast, knowing that the /r/blind community switched to Lemmy.
Just had a look at what https://rblind.com/ looks like. Hm, yeah, definitely different.
About the double input for password, Google still uses it, so it seems to still be an industry standard
Confirm password fields reduces conversion rates. Google has such a chokehold on the market that I doubt they care about that and might be more interested in potentially reducing password reset traffic after miss typed password inputs. Though in fairness I think it's doubtful if there is even a benefit in that area from having confirm password fields. At least if you have a proper unmasking or "show password" option while registering.
I just tried on both Voyager and Photon, and indeed none of them have an "unmask" button for the passwords. @aeharding@lemmy.world and @Xylight@lemdro.id, do you think it would be possible to add that?
Ironically, the default Lemmy UI does:
Argh I wish browsers handled that themselves for password inputs
If a website doesn't let me view a password, I use the inspect element to change the input type.
I have always done copy/paste for password confirmations. "Yes" and "confirm" is new for me, I haven't heard of such inputs. 🤣🥃
The comment seems a bit far-fetched as the screenshot literally has "Confirm password"in the field