At my opinion, an user-friendly interface will also attract more SNOs. Ultimately, the nodes should be accessible in one click, set and forget it (except for the monitoring look up), in the best world, even if we’re still far to this (but the Web dashboard is also there to offer more comfort and more infos and bug fixes with the updates & some Bright suggestions sometimes too hehe).
@sytnik Useless, and so needful suggestion; adding a discrete dark mode switch, like the current Web dashboard (if it can be switched or refreshed during the process?), like an “avant-goût” or “déjà vu” of the next step. Yes, I’m a Dark mode user, I like it!
If it is generating keys online but with local resources, couldn’t it be deteced as a virus because some browser thread is using 100% of the cpu?
And even though I understand the intention behind this, I think it’s not a good idea. Would be better to integrate it into the GUI installer and make it ask if you want to generate a new identity or use an existing one. Could even include receieving an auth token into the installer.
On linux that’s of course different with docker but long-term goal is to use binaries so it could be easily integrated there too.
Personally I’d prefer such a solution over creating identities on the webpage, because this makes the process only slightly easier while integrating everything into the gui installer would make the process child’s play.
That design is for the native application, rather than for web application. It will be the same process as it is now with CLI interface but with some GUI on top. Also, you are right about having computationally intensive process run in a browser thread is a bad idea.
The plan is to have a standalone app for identity generation, so identity generation can be run independently from setup process, as it can take several days for identity to be generated. However, having an option to start identity generation from the GUI installer in a non-blocking way is a good idea that we might want to add at some point.