Hello,
As part of the ongoing infrastructure migrations, this Discourse instance will become read-only for a few hours.
Thank you for you patience and understanding.
3 Likes
Okay, we should be back now.
3 Likes
Seems to work now 
3 Likes
Are there plans to restore the GitHub auth integration?
(I figured out how to log in by requesting an e-mailed link, but I’d prefer to be logged in via GitHub.)
7 Likes
(I figured out how to log in by requesting an e-mailed link, but I’d prefer to be logged in via GitHub.)
Ah thanks, didn’t know this was possible until your comment. I thought I was just out of luck.
For anyone else reading this (because it was not obvious to me):
- Go to the login page.
- Type in your username.
- The
Skip the password...link will appear; click it to receive the link at your email.
Edit: It’s also possible to add a password to an account after logging in, via preferences -> security -> Send Password Reset Email. So at least there is a “migration strategy”, for people who only ever used some third-party auth.
7 Likes
Thanks for sharing this!
The read-only, downtime, re-login, was due to our infrastructure migration. The Haskell Discourse is now hosted by the Discourse folks themselves (thanks Discourse!).
We’re unsure if gitlab/github login will work in the future. I’m trying to find that out. This was an unanticipated consequence of the migration, I take full responsibility for not anticipating it.
8 Likes
Thanks to all involved for performing the migration and keeping the forum working!
Typing in the message text box is now for me incredibly slow. It had become quite slow after the last upgrade, but now seems to be worse. Is this the same for anyone else?
It seems to send my CPU usage to 100% (according to Firefox’s about:processes). I’m on Firefox 128.9.0esr (Debian).
I don’t notice any performance issues on my devices.
1 Like
Hello!
When I try to log in via an emailed link, I don’t receive any emails. Not even in my spam folder. I’m locked out at the moment. But perhaps I still can reply messages in threads via email.
Best,
Facundo
1 Like
Maybe a notice like the one informing me about my browser becoming incompatible with Discourse could be added for people who logged in through GitHub?
My experience matches those above. Could not log in directly and no emails showed up.
Email works now and (obviously) logging in through the link too.
Another consequence of the migration is that we have been running into a daily email limit which may have caused some of the login emails not to be sent. We did not have a limit like this with our previous setup.
I only noticed that today; sorry about that! We’re looking into it now.
As a temporary workaround, if anybody has not received a login email, please try requesting another one on the next day.
3 Likes
I’m on Firefox 130 on NixOS and have not noticed any slowdown.
We had to update to the latest version of Discourse to perform the migration, which may be causing the difference in your experience. I don’t think there is anything else that we can do in the short term except for updating again once there is another Discourse release.
1 Like
Yeah, there was also a marked slowdown after the previous update a few months ago. If it’s only me who has the problem I’ll just live with it. I can always compose messages in Emacs
Please, Admin makes this topic Pinned at least for one month!
I was unlogged a week, because I didnot notice a new way to log in if I signed via GitHub.
@tbidne wrote a good instruction! Thank you.
5 Likes
Good idea!
I’ll also edit the title to hint that there’s further information that would be useful.
3 Likes
Maybe make a new post? “[and login help]” isn’t prominent and easy to miss (I came here to report that the post had been “mistakenly” repinned, because I didn’t even see that addendum).
2 Likes
For a week there, I thought the community didn’t want me. 
.
It’s good to be back and less dependent on GitHub for my login credentials.
2 Likes