Given the huge privacy implications alone, I would say that either: - the protocols need to be standardised - or the cloud part of the browser needs to be downloadable and deployable by the user and third-party cloud providers. A data center implementing the proprietary cloud part of the browser will be an excellent information source for organizations doing pervasive monitoring. Just being transparent and letting the user (whether it is an person or an enterprise) be able to turn off the feature is not enough. Just as the user of the browser can choose which device to run the browser on, the user must be able to choose which cloud to run the browser in. Cheers John Mattsson On 23/06/14 15:45, "Nicolas Mailhot" <nicolas.mailhot@laposte.net> wrote: > >Le Lun 23 juin 2014 15:04, Julian Reschke a écrit : > >> - think about why browser developers deploy non-standards-based proxies. >> >> Some obvious reasons are: >> >> 1) so that they can optimize the protocol (performance, security), >> >> 2) to simplify configuration (a check box is simpler to explain than a >> proper proxy config UI). > >3. they found like everyone else the current standard does not permit >deployment of effective proxies without cheating (lack of reliable way to >express trust, lack of reliable way to convey errors, lack of any decent >browser UI, browser refusal of TLS termination) > >4. it's easier not to ask permission of anyone least of all the user > >5. natural developer bias for internal coding instead of something else > >-- >Nicolas Mailhot > >
Received on Wednesday, 25 June 2014 10:49:13 UTC