<div style><font face="Helvetica"><span style="white-space:nowrap">In general, steps to protect readers and editors from surveillance and </span></font></div><div style><font face="Helvetica"><span style="white-space:nowrap">interruption in internet service because of the content they select is </span></font></div>
<div style><font face="Helvetica"><span style="white-space:nowrap">probably not advocacy, but when the cause is deliberate government </span></font></div><div style><font face="Helvetica"><span style="white-space:nowrap">intrusion, there certainly is an advocacy element. And in this instance </span></font></div>
<div style><font face="Helvetica"><span style="white-space:nowrap">it absolutely is, because there are Chinese civil liberties groups which </span></font></div><div style><span style="white-space:nowrap;font-family:Helvetica">have been stridently demanding a much more drastic approach:</span></div>
<div style><span style="font-family:Helvetica;white-space:nowrap"><a href="https://en.greatfire.org/blog/2013/jun/wikimedia-foundation-says-it-doesnt-hold-chinese-readers-any-less-regard-we-disagree">https://en.greatfire.org/blog/2013/jun/wikimedia-foundation-says-it-doesnt-hold-chinese-readers-any-less-regard-we-disagree</a></span></div>
<div style><span style="font-family:Helvetica;white-space:nowrap"><br></span></div><span style="font-family:Helvetica;white-space:nowrap">But </span><span style="font-family:Helvetica;white-space:nowrap">I will also take this to bugzilla and try to submit a proposed patch.</span><div>
Per <span style="font-family:Helvetica;white-space:nowrap"><a href="https://queue.acm.org/detail.cfm?id=2405036" target="_blank">https://queue.acm.org/detail.cfm?id=2405036</a> which Leslie Carr </span><div><span style="font-family:Helvetica;white-space:nowrap">posted to wikimedia-l </span><span style="font-family:Helvetica;white-space:nowrap">concerning the https filtering problem in PRC, </span></div>
<div><span style="font-family:Helvetica;white-space:nowrap">the Great Firewall has TCP packet text "deep" inspection which is </span></div><div><span style="font-family:Helvetica;white-space:nowrap">limited in certain ways because of high volume processing requirements. </span></div>
<div><span style="font-family:Helvetica;white-space:nowrap">I'm certain that general HTML to text parsing would be a huge and </span></div><div><span style="font-family:Helvetica;white-space:nowrap">difficult enhancement for it. I was recently in Shanghai and able to </span></div>
<div><span style="font-family:Helvetica;white-space:nowrap">confirm that it couldn't respond to strings with null <span> tags, or </span></div><div><span style="font-family:Helvetica;white-space:nowrap">hexideximal entity codes, although it does sense<span></span> each type of UTF-8, </span></div>
<div><span style="font-family:Helvetica;white-space:nowrap">-16, and -32 encodings.</span><div>
<div><font face="Helvetica"><span style="white-space:nowrap"><br></span></font></div><div><font face="Helvetica"><span style="white-space:nowrap">But having said that, I hope people will consider the public messaging </span></font></div>
<div><font face="Helvetica"><span style="white-space:nowrap">implications of openly automatically </span></font><span style="white-space:nowrap;font-family:Helvetica">protecting over a billion Internet </span></div><div>
<span style="white-space:nowrap;font-family:Helvetica">users from surveillance in the context of the PRISM questions. It would </span></div>
<div><span style="white-space:nowrap;font-family:Helvetica">set a great example and perhaps inspire people to look for many <span></span>simple </span></div><div><span style="white-space:nowrap;font-family:Helvetica">work-arounds able to be deployed nimbly instead of hand-wringing over</span></div>
<div><span style="white-space:nowrap;font-family:Helvetica">"the" best solution when a series of seperate approaches might better </span></div><div><span style="white-space:nowrap;font-family:Helvetica">serve to protect readers from surveilance trigger </span><span style="white-space:nowrap;font-family:Helvetica"></span><span style="white-space:nowrap;font-family:Helvetica">keywords.</span></div>
<div><span style="white-space:nowrap;font-family:Helvetica"><br></span></div>
<div><br>On Thursday, June 20, 2013, Amgine wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
On 19/06/13 05:16 PM, James Salsman wrote:<br>
> How do people feel about inserting null <span> tags in between the<br>
> characters of the strings triggering surveillance and censorship<br>
> listed on <a href="http://cs.unm.edu/~jeffk/tom-skype/" target="_blank">http://cs.unm.edu/~jeffk/tom-skype/</a> ?<br>
><br>
> This could most easily be accomplished during page rendering, and<br>
> would require a code change. I think it would be an easy code<br>
> change which most PHP programmers experienced with Mediawiki could<br>
> accomplish in less than a week, but.... let's just say some of my<br>
> estimates haven't always been in the ballpark.<br>
<br>
<br>
I don't have any strong feelings one way or another, although it would<br>
be exceptionally simple to work around this proposed method.<br>
<br>
On the other hand, it isn't an Advocacy Advisor's topic imo. That<br>
would be a MediaWiki enhancement, which can be submitted at the<br>
bugzilla.[1]<br>
<br>
Amgine<br>
<br>
[1] <a href="https://bugzilla.wikimedia.org/" target="_blank">https://bugzilla.wikimedia.org/<span></span></a><br>
</blockquote></div>
</div></div>
</div>