-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discovery with and without the --no-cloud build flag. #12
Conversation
@@ -0,0 +1,16 @@ | |||
# Box-client discovery: two options | |||
|
|||
## Option 1: --no-cloud |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the use case/target audience of this option?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
People who don't want to leak their data to the cloud, and who don't want to rely on cloud services for the continued operation of their foxbox. In fact, if we would apply item 4 of the Mozilla manifesto, we should not even be calling this an 'option'.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So why is this a build-time option? Why not something that can be configured locally (with a big red warning somewhere, of course).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, maybe it's more correct to call it a runtime option, because as a developer, you could set it from the command line.
However, to the end-user it would be a "purchase time" option unless a hardware developer adds some UI to the box (like a big red button) that affects how cargo run
is called when you power up the box.
I'll have a stab today/tomorrow at implementing this command line option.
|
||
Note that this requires the client to support both mDNS and self-signed certificates, so it has to be a native/Cordova app. | ||
|
||
## Option 2: default build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it's the default option, it makes more sense to call it Option 1
and put at the top.
@michielbdejong: we've been discussing that many times in the past and reached an agreement. Can you highlight what new elements came into play to make us change the direction on that? |
I might be missing some context here, but I think you're referring to the agreement reached during the 'Https everywhere and discovery' meeting on 5 March, where we decided to build 3 options. The new element since then would be that I've retracted my proposal to use QR code since nobody except me liked it. :) So the new situation is that there are not three but two proposals, and the mDNS+TOFU one is slightly different than it was a month ago, because it no longer involves QR code scanning. Does that answer your question? Let's briefly discuss on irc / Vidyo if it's still unclear! :) |
It has been decided that, even though the Box may have a I moved the Cordova code (which can discover the Box over mDNS, and can trust a self-signed TLS certificate on first use) to my personal github account. |
No description provided.