Claire
Claire
That's what #18943 attempts to fix, but as https://github.com/mastodon/mastodon/pull/18943#pullrequestreview-1156972814 explains, this is a bit more complicated.
Off the top of my head: - Some of this is already handled with the distinction between `LOCAL_DOMAIN` and `WEB_DOMAIN`, except that you'd need to use a custom user-specific domain...
Related: #9528 #5239
> hmmm... `build-and-test` takes more than 3 hours... It's a bit scary to not have fast feedback on PRs It usually returns in under 10 minutes, but it since to...
This seems difficult to achieve, and would pose significant privacy issues. That being said, mentioning that the user might have registered on another server in the log-in failure message does...
This may be an issue with the specific Mastodon server you are attempting to register to. It may be overloaded or have other issues. You could share which server it...
> mastodonapp.uk This server seems to currently be struggling with load: https://mastodonapp.uk/@wild1145/109308376951724487 https://status.atlas-media.co.uk/incidents/42
> So, do I just wait or is there something I can do ? Just waiting should be good! But if you can't wait, you can try another server.
Oh, interesting oversight. This is not an entirely satisfying solution, but until the issue is fixed, you can work around the issue by using `ALLOWED_PRIVATE_ADDRESSES`
To clarify, Mastodon runs on many different independent servers, and what happened is you visited a different server from the one you are logged in, hence why you got the...