marzavec

Since this is a different issue, I've opened up a different case, #28 where we can discuss it further.

Do you mean that the use Roman characters may cause issues with users who do not natively use Roman characters?

Oh, for sure. Hack.chat strives to be entirely self-hosted, which means no external calls. The current captcha system uses [ascii-captcha](https://www.npmjs.com/package/ascii-captcha) to generate a captcha.

Yep, that is exactly it- much like how this is done with the current client.

Sorry for the late reply. The `settings` route will contain the ui elements needed to alter the client UI, user data, client behavior and (possibly) network settings. ### User data...

Good idea! We can allow fine tuning of the notification settings within the settings page. I'll keep this open and reference the open issues https://github.com/hack-chat/hackchat-client/issues/12 and https://github.com/hack-chat/hackchat-client/issues/17

> same password for multiple services that password will still be stored in plain text This is true, now the attacker only needs to guess your email. . . >...

Sure, so we are trying to find a solution for the set of users who are on public computers, using the "remember my password" option, who also happen to be...

> when a user submits a password That's an easy fix then; what if we change the terminology from "password" to "trip phrase"? Technically it isn't a password, as there...

We'll have the client display the message & re-open the join modal. Will leave open until the fix is added.