Show blocked by bruteforce

[tobiasKaminsky]

Users are sometimes confused why the login times out. This is often due to bruteforce blocking/delaying the login to 30s.

How can we get a better user experience for this?

[AndyScherzinger]

Yes, please! This might prevent some recurring questions coming in via the forum, tracker, etc. due to the lack of given information by the app.

[AndyScherzinger]

Would help with #433 for example

[tobiasKaminsky]

As a small brainstorm with Lukas:

• https://github.com/nextcloud/server/issues/4510 will implement an endpoint to see how long the password timeout is
• if > 10s then show a small "warning: timeout is due to BF adjusted. Please wait" (or similar) and then adjust the timeout to 1.5 mins or such.

[mario]

Sure, this was discussed at the last hack week.

[tobiasKaminsky]

Sure, this was discussed at the last hack week.

Then an issue with such an info and roadmap would have been nice to not redo the work ;-)

[mario]

I would have expected my friend @LukasReschke has done it already :P

[tobiasKaminsky]

At least not here in android repo ;-)

[LukasReschke]

Evil evil Lukas 😉

[tobiasKaminsky]

As the real solution via a proper server timeout will take some time (NC 13, https://github.com/nextcloud/server/issues/4510#issuecomment-301591234) I suggest to just enhance the timeout to > 30s, probably 45s. This way all "blocked" users will connect again and the other have to wait just a little bit longer to get the "connection timed out" message. @mario @AndyScherzinger

[AndyScherzinger]

Sounds good to me 👍