
Robert Guthrie Tue 10 Sep 2024 12:25AM
@Graham - you can still set a password and use that instead. See the button here:
We default to no password because creating and remembering a secure password without a password manger is a very challenging problem - we have the numbers to show this is a better approach.
With this flow, you can set a password as soon as you have confirmed your email address, and never use a login email again.

Graham Tue 10 Sep 2024 8:29AM
@Robert Guthrie The UI doesn't make it clear that if I choose to set password (despite me already having one that I appear unable to use) I can then override the 'email a code' thing. Thanks for clarifying - I'll do that.

Graham Tue 10 Sep 2024 8:53AM
Logged out, so I could log in again, and this time set a password (is there a mechanism to set a password after I've already logged in?) Asked for the code to be sent. Waited form 09:30 to 09:47 - nothing arrived. Started again, asked for the code again, code arrive at 09:49 (a mere 19 minutes after the first request was placed). Set a new password to replace my old password.

Graham Tue 10 Sep 2024 8:56AM
I can now log in once again with a password. Thanks for the help. no idea why I was stopped form logging in with my old password - must have missed that memo - but after just 30 minutes or I'm back where I was. (Update: 09:55 and the second sing in code has just arrived in my inbox!).

Robert Guthrie Tue 10 Sep 2024 9:11AM
@Graham - you're right - if emails are slow to arrive then the whole experience falls apart. Sorry about this. I'm hearing a few reports today that emails are slow. We're sending them immediately, so there isn't much we can do to improve delivery.
However, I could add a little more help to the "set password" offer on the enter code form. Explain it more clearly and give it more visibility.
As a footnote, we also support sign in via Google. We did have multiple services (facebook, github etc) but actually that generated more support requests because people forgot which option they used last time.

Graham Tue 10 Sep 2024 9:19AM
Thanks for taking it on board. And the prompt response is greatly appreciated. All the best.
Graham · Mon 9 Sep 2024 10:25AM
I've just spent a good 5 - 10 minutes that I'll never get back, logging in to Loomio. I remember now with some fondness the days when all I needed was my username and password and could quickly log in. Now I have to wait for an email to arrive with a code. In my experience this emails always takes a good while to turn up: just now for instance I uselessly spent those minutes checking to make sure that I'd entered the correct email address, and going through the sign-in process three times, in case the previous attempts had somehow failed to trigger the all-important email.
Eventually an email did arrive, and it did take several minutes to arrive. (The 2nd and 3rd email also turned up 3 and 6 minutes later, respectively).
No doubt there are sound technical reasons why the good people at Loomio chose to get rid of the password-based log in process and replace it with this. However this is not a user-centric approach, and I would urge that other options be made available. Having to sit and wait - in my case for several minutes - for a code to arrive by email takes agency away from users and wastes their time.