search

fxbox / RFC

Discussion about design decisions
1 stars 2 forks source link

Discovery with and without the --no-cloud build flag. #12

Closed michielbdejong closed 8 years ago

gmarty commented 8 years ago

@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?

michielbdejong commented 8 years ago

@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! :)

michielbdejong commented 8 years ago

It has been decided that, even though the Box may have a --no-cloud option, there are currently no plans to make the client app compatible with that (until the web platform evolves to support it, for instance with FlyWeb).

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.