We would like to give some feedback concerning the SAFE Browser and its API.
We’re aware the documentation is being worked on, so currently we’d just like to mention that it’s somewhat confusing that the term “secret key” is always used in the API, whereas libsodium seems to distinguish between “secret key” and “private key”, the former being used in the context of symmetric cryptography and the latter in the context of asymmetric cryptography.
API Desired Features
The only thing we truly miss is MutableData ownership transfer support, though because this has been discussed in the past we assume MaidSafe devs are aware of this and that it’s just not ready yet.
What we’d also appreciate to see at some point is crypto functions for creating and validating public-key signatures. We currently use a library for that so we’re fine for now, but it’s safer to be handled by the authenticator/browser.
We’d like to be able to test our browser apps automatically, so we are wondering if the SAFE Browser can be run in a headless-mode (already or in the future)? It’d be convenient if it’d be possible from within tests to for example register accounts, log into and out of accounts, and accept and deny app authorisation requests. We looked but were unable to currently find such a headless-mode.
Thank you for all your hard work!