I tried to submit a registration request four days ago. After clicking the submit button, I got a spinning wheel. This went on for several minutes. Thinking it might have been the Safari browser, I tried it again in Chrome and got the same thing. After a couple of days, I tried to log in and also got the spinning wheel. I left that page open for a couple of hours with no response. Is this and issue with running on MacOS? Could the request have gone through and response didn’t get back to me? I can try again on iOS or iPadOS.
yes, most of the quirks can be overlooked but the registration process is pretty critical to encouraging signups and participation. We’re never going to become bigger than reddit at this rate /s
Having the registration process hang will discourage the non-technical user. Maybe some mention of the issue on the registration page might be useful. If there had been an explanation and said to do what was brought up in this thread, I certainly would have followed the instructions and felt better about the issue.
I agree wholeheartedly. Since this is “Beehaw Support” maybe the admins here will take your suggestion - I am not with Beehaw, just happened to see this post. I can see fairly certainly that the registration hangs and the submit button spins when the masked password fields don’t match. Given the number of complaints I’ve seen - and also what I’ve experienced myself, this very likely also occurs sometimes when they do match. The user interface should say “passwords don’t match” instead of spinning like that. It provides feedback when the password is too short, but not when they don’t match. Also once it hangs, it doesn’t matter what you do with the password fields, or even refreshing sometimes - the same behavior continues, matching passwords or not.
Hopefully the coders working on Lemmy can take care of this relatively soon because it’s not the greatest first impression for users.
500,000,000 users vs. 150,000 users? We can do it! <waves pom-poms in air, does cheerleader kicks>
that’s the spirit! To be fair, the fediverse is a great deal bigger than lemmy. Lemmy is just the closest thing to reddit on it, so a considerable number of folks who don’t like the way reddit inevitably goes will land on lemmy (if it works properly). Lemmy has similar properties (and probably people) as reddit did early on.
I spent some time trying to replicate this spinning thing with matching passwords but was unable to do so. However, what I see is that the UI does not provide feedback when the passwords don’t match - instead, the submit button icon spins. This suggests a defect in the UI, for which alas, I have neither time or skills to address - BTW I’m not affiliated with any support group, Beehaw or otherwise.
I’m not able to pursue this with Lemmy’s developers myself, but it would be worth making sure that it is understood (I can’t imagine it hasn’t already been reported, it’s an obvious issue - the UI should tell you when the passwords don’t match, not spin). There’s an issue log at github but I’m not sure what beehaw is doing as far as this forum goes or who would be interested in pursuing this, assuming that I’m correct.
You can see this issue for yourself by going to any lemmy instance and attempting to join with mismatching passwords - I just did so at lemmy.ml
The weird thing is that it tells you when the password is too short, but it doesn’t when they don’t match. I am using browser ad and popup blocker but that shouldn’t be an issue.
I don’t believe that this is the extent of the issue because what I’ve seen suggests that it has occurred sometimes when the passwords are matching, but I daresay all the submit button spinning stuff is related to password validation somehow - because I haven’t heard of it happening once the user is authenticated.
Idk if this is helpful to you, but matching passwords still gives me the infinite wheel.
for what it’s worth, I updated the local dev system with the latest code and I see this is resolved - a message appears when the passwords don’t match and the button no longer spins. git logs show quite a lot of fixes to the UI since the release last week, so the UI should be significantly better on next release.
