Local UI For Provisioning

[cp1000]

From the roadmap:

Quote

The command deck will be required for certain functionality.  It will ALWAYS be required for initial system provisioning.  The main reason is that the HexOS installer does not include our UI and it never will. Instead, the local UI will be loaded via a Docker container that we will install after initial system provisioning.

I understand that this is a firm architectural decision as of now, and due to the Hexos licensing structure, likely a necessary one.

However, I would consider the phrase "lifetime license" to be philosophically incompatible with online validation.

Possibly I'm merely arguing semantics - and this is certainly not a sticking point for me - just something worth thinking about.

Excited for beta access!

[speedking456]

My thinking is, if they're going to offer a local option at all, the command deck should not be required for provisioning. My thinking for why they're doing this is because DRM will most likely be included in release versions and they don't want people stealing their secret sauce. However, they're saying it's self-hosted, and you have "Full control". In that case all components should be self-hosted, or at least give the user the option at install.

This is coming from someone who is incredibly excited, and is already very impressed with the beta. I just want to see this product develop positively and make an impact in everyone taking back control of their data.