nitnelave

I was waiting until we have a UI for it before releasing it. Now that we have the CLI tool, it's not the best but I'll make a stable release....

Yes, it is. However, expect development to be slow in the next few months (like it has been in the past few months) due to personal circumstances.

The new versions have a different encoding of the password. This would be a pretty big breaking change, which I'll only do as part of a big release (v1.0).

It seems the OPAQUE proposal is still being worked on (version 3.0.0-rc2). The repo has also migrated to https://github.com/facebook/opaque-ke. Once the dust has settled and the version is stable (and...

New proposal, to avoid having to reset all the passwords: https://docs.google.com/document/d/1Y8rVSYyZzzzjKGJOVTYVFl38pKSnUopx-cijR24IMz4/edit?usp=sharing

Thanks for volunteering, but we're not ready to accept translations yet, the infrastructure is not there :)

Actually, I think we're not going to do this: it would be a drag on new features and overall maintenance, for little gain: most end users will only see the...

I also investigated wasm-opt, but it doesn't help at all (actually makes the gzipped version slightly bigger).

I didn't investigate this properly, but if what you say is true, then the biggest blocker I see is updating yew/yew_router. This requires a huge change in how the frontend...

@infogulch could you expand on the security risk? Or do you have documents/articles that I could read about it? I'm curious