> On Fri, Jun 7, 2013 at 2:31 PM, Ryan Lane wrote:
>> A very small minority of users don't have HTTPS
>> support, or their computers are so old that it makes the site unusably
>> slow. That's a *very* small percentage of users, though.
There's also the small issue of a billion people in China who
On Sat, Jun 8, 2013 at 12:01 PM, Brad Jorsch wrote:
> "Hard-enabled", on the other hand, means that anyone fetching the http
> URL would be redirected to the corresponding https URL.[2] If this
> were somehow done now, then people in China would not be able to read
> Wikipedia at all because the
On Sat, Jun 8, 2013 at 9:41 AM, Anthony wrote:
>
> What is this "hard-enabled" and "soft-enabled"?
I hope someone will correct me if I'm wrong, but...
I believe that "soft-enabled" means that https was set as the protocol
in the canonical URLs for uzwiki. So search engines should start
linking t
On Fri, Jun 7, 2013 at 6:24 PM, Matthew Roth wrote:
> We have had contact with the authors of the blog and they have said they
> will publish our response to their article, though I'm not sure when or in
> what format.
>
> This is the content of our response:
>
> "The Wikimedia Foundation doesn’t
What is this "hard-enabled" and "soft-enabled"? If the Chinese volunteer
editor community requests that HTTPS be "soft-enabled" for them, and you do
so, does that solve anything?
On Fri, Jun 7, 2013 at 12:24 PM, Matthew Roth wrote:
> We've also hard-enabled HTTPS on all of our
> private wikis a
This response seems to miss the fact that, in this particular case,
censorship is being accomplished through eavesdropping.
On Fri, Jun 7, 2013 at 6:24 PM, Matthew Roth wrote:
> Hi all,
> I wanted to share a clarifying email from Ryan Lane in WMF Ops. He's
> working through the challenges of HT
Hi all,
I wanted to share a clarifying email from Ryan Lane in WMF Ops. He's
working through the challenges of HTTPS from the Foundation's end.
Please see below for more details:
-Matthew
On Fri, Jun 7, 2013 at 2:31 PM, Ryan Lane wrote:
> How does it impact people? Short answer: it shouldn't.
On 8 Jun, 2013, at 12:24 AM, Matthew Roth wrote:
> We have had contact with the authors of the blog and they have said they
> will publish our response to their article, though I'm not sure when or in
> what format.
Great. That's really fast response.
On the issue itself, we haven't seen any la
On Fri, Jun 7, 2013 at 6:42 AM, Benjamin Chen wrote:
> Hi,
>
> Since 31 May, China's Great Firewall has blocked the HTTPS connection to all
> language versions of Wikipedia, by blocking port 443 on two of our IPs. I was
> also told that service to Wikimedia Commons may be affected. Other project
We have had contact with the authors of the blog and they have said they
will publish our response to their article, though I'm not sure when or in
what format.
This is the content of our response:
"The Wikimedia Foundation doesn’t hold any readers of our projects in any
less regard than others.
https://upload.wikimedia.org also blocked
Chinese wikipedia: http://zh.wikipedia.org/
My blog: http://shizhao.org
twitter: https://twitter.com/shizhao
[[zh:User:Shizhao]]
2013/6/7 Benjamin Chen :
> Hi,
>
> Since 31 May, China's Great Firewall has blocked the HTTPS connection to all
> language v
Wow, what a complete mis-understanding and misrepresenting of facts my that
blog author
On Friday, June 7, 2013, Benjamin Chen wrote:
> Hi,
>
> Since 31 May, China's Great Firewall has blocked the HTTPS connection to
> all language versions of Wikipedia, by blocking port 443 on two of our IPs.
>
Hi,
Since 31 May, China's Great Firewall has blocked the HTTPS connection to all
language versions of Wikipedia, by blocking port 443 on two of our IPs. I was
also told that service to Wikimedia Commons may be affected. Other projects,
such as en.wikisource are not affected by this block (but t
13 matches
Mail list logo
