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.
Correct. It’s a Lemmy-wide issue. Whether the instance is large or small, if it’s on Lemmy it’s getting the spins.
This was not happening before the wave of Reddit users. I never had to deal with it before the Reddit blackout. Hence, my assumption that the issue is the overload.
that’s interesting - I came with the wave and it has been happening since I first set up the instance. I am also seeing it on a local dev system that isn’t even accesssible from the internet - not a UI developer, but will have a crack at trying to figure out what’s going on here. It’s a very frustrating issue.
There are a lot of issues. Like, I’m seeing four identical copies of your reply. I’m pretty sure there aren’t actually four copies in the thread, and they are only on my message screen. Lots of little things like that. I figure they are just growing pains, and I’ll wait them out.
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
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.
Looking at the recent changes over the past few days to the current codebase (not yet released) I expect this issue should be resolved in the next Lemmy release and you should stop seeing it once your instance admin upgrades the current version - I don’t know the new release timeframe but the previous release was last week, so hopefully quite soon.
Excellent, thanks so much for the legwork while I caffeinate and chat with my friend. I owe you one!