W3C home > Mailing lists > Public > www-tag@w3.org > January 2015

Re: Draft finding - "Transitioning the Web to HTTPS"

From: <chaals@yandex-team.ru>
Date: Tue, 20 Jan 2015 16:18:41 +0300
To: Philip Jägenstedt <philipj@opera.com>
Cc: Anne van Kesteren <annevk@annevk.nl>, Paul Libbrecht <paul@hoplahup.net>, Henry S. Thompson <ht@inf.ed.ac.uk>, Mark Nottingham <mnot@mnot.net>, Henri Sivonen <hsivonen@hsivonen.fi>, Chris Palmer <palmer@google.com>, Noah Mendelsohn <nrm@arcanedomain.com>, "Michael[tm] Smith" <mike@w3.org>, Tim Berners-Lee <timbl@w3.org>, Public TAG List <www-tag@w3.org>
Message-Id: <49701421759921@webcorp01h.yandex-team.ru>
20.01.2015, 15:44, "Philip Jägenstedt" <philipj@opera.com>:
> On Tue, Jan 20, 2015 at 1:28 PM,  <chaals@yandex-team.ru> wrote:
>>  19.01.2015, 15:01, "Anne van Kesteren" <annevk@annevk.nl>:
>>>  and if anything we should move towards making it impossible to connect to such sites.
>>  I'd prefer you don't interfere with my decisions about what I want to look at and read. That is a whole step beyond suggesting to me that I might not be getting what I asked for.
>>
>>  The latter is, when done right, a useful service. The former is censorship, and while I support the right of the society I live in to decide that some things should not be made available, I find it highly inappropriate that a browser vendor would take it into their hands to make such decisions.
>
> Do you find it inappropriate that the Yandex Browser is currently
> unable to connect to https://crypto.cat/ and https://tv.eurosport.com/
> (demo site) with no apparent option for ignoring the problem?

Yes, of course, Did you file a bug, or should I?

cheers

--
Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com
Received on Tuesday, 20 January 2015 13:19:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:57:09 UTC