Ban violation messaging inconsistency

[ss-gonda]

What happened?

When we enable ban violation on messaging. The messaging to end user is inconsistent and quite random.

Steps to Reproduce

When trying to validate the BAN VIOLATIONS everything works as expected but the messaging does not comes proper.
On first violation it gives : "Some thing went wrong...".
If I send again a message then we get : "Your account has been temporarily banned due to violations of our service"

I think as a user we should get that you are restricted due to message_violation for XX minutes ?

What browsers are you seeing the problem on?

No response

Relevant log output

No response

Screenshots

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

It's intended to show the ban message right away, I'll look into it. In any case, they will see the message when trying to login again.

[bittylicious]

Hello. The front end seems to present this message whenever it gets a 403 response from the login call.

This can happen when behind Cloudflare too, e.g. if a Javascript challenge pops up.

We should present an error message to the user that came from the login API call, not assume all 403 responses mean the same thing.

Above is the Cloudflare "Just a moment..." image which is a Javascript challenge, however the user gets told instantly that they have a ban violation.