<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Is Making Public Data &#8220;More Public&#8221; a Privacy Violation?</title>
	<atom:link href="http://33bits.org/2010/04/05/is-making-public-data-more-public-a-privacy-violation/feed/" rel="self" type="application/rss+xml" />
	<link>http://33bits.org/2010/04/05/is-making-public-data-more-public-a-privacy-violation/</link>
	<description>The End of Anonymized Data and What to Do About It</description>
	<lastBuildDate>Tue, 06 Dec 2011 23:45:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: What every developer needs to know about &#8220;public&#8221; data and privacy &#171; 33 Bits of Entropy</title>
		<link>http://33bits.org/2010/04/05/is-making-public-data-more-public-a-privacy-violation/#comment-1540</link>
		<dc:creator><![CDATA[What every developer needs to know about &#8220;public&#8221; data and privacy &#171; 33 Bits of Entropy]]></dc:creator>
		<pubDate>Tue, 06 Jul 2010 19:43:22 +0000</pubDate>
		<guid isPermaLink="false">http://33bits.org/?p=460#comment-1540</guid>
		<description><![CDATA[[...] a piece of data public, then they&#8217;ve given up any privacy expectation. But as we saw in a previous article, users often expect more subtle distinctions, and many unfortunate privacy blunders have resulted. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] a piece of data public, then they&#8217;ve given up any privacy expectation. But as we saw in a previous article, users often expect more subtle distinctions, and many unfortunate privacy blunders have resulted. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arvind</title>
		<link>http://33bits.org/2010/04/05/is-making-public-data-more-public-a-privacy-violation/#comment-1449</link>
		<dc:creator><![CDATA[Arvind]]></dc:creator>
		<pubDate>Sun, 30 May 2010 18:03:25 +0000</pubDate>
		<guid isPermaLink="false">http://33bits.org/?p=460#comment-1449</guid>
		<description><![CDATA[No worries. Looks like we’re talking about different things and aren’t really contradicting each other.

“the publicness of any particular information does not in and of itself mean that it escapes information privacy law.”

Yes, I’m not disputing that.

Thank you for your comments. No offense taken.]]></description>
		<content:encoded><![CDATA[<p>No worries. Looks like we’re talking about different things and aren’t really contradicting each other.</p>
<p>“the publicness of any particular information does not in and of itself mean that it escapes information privacy law.”</p>
<p>Yes, I’m not disputing that.</p>
<p>Thank you for your comments. No offense taken.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Wilson</title>
		<link>http://33bits.org/2010/04/05/is-making-public-data-more-public-a-privacy-violation/#comment-1446</link>
		<dc:creator><![CDATA[Stephen Wilson]]></dc:creator>
		<pubDate>Sun, 30 May 2010 01:09:37 +0000</pubDate>
		<guid isPermaLink="false">http://33bits.org/?p=460#comment-1446</guid>
		<description><![CDATA[Hi Arvind. 

I should explain that I&#039;ve been engaged in a lot of dialogues lately which I think expose a systemic misunderstanding of privacy *law* by technologists.  The Google wifi example is obviously front and centre there.  So I took some of the points in your blog and without knowing if you were supporting the views or just mentioning them, I used the points to advance my thesis. I only mentioned Google to sharpen my point, not to join you to that issue in any way.  No offence intended! 

I don&#039;t think secondary usage should be prohibited. I just want technologists to recognise that privacy law is actually very clear on Collection and on Use &amp; Disclosure.  You might not be saying otherwise ... but the publicness of any particular information does not in and of itself mean that it escapes information privacy law.  

Your blog opened with a line about technologsts seeing a simple distinction, and I merely used that as a jumping off point for my argument that that particular distinction is unhelpful.  In fact, it betrays a category error that makes it difficult for technologists to engage in the privacy debate.  My thesis is that technologists and privacy policy wonks have very different frames of reference. 

Again, sorry to have used your blog as a platform! 

Cheers, 

Stephen.]]></description>
		<content:encoded><![CDATA[<p>Hi Arvind. </p>
<p>I should explain that I&#8217;ve been engaged in a lot of dialogues lately which I think expose a systemic misunderstanding of privacy *law* by technologists.  The Google wifi example is obviously front and centre there.  So I took some of the points in your blog and without knowing if you were supporting the views or just mentioning them, I used the points to advance my thesis. I only mentioned Google to sharpen my point, not to join you to that issue in any way.  No offence intended! </p>
<p>I don&#8217;t think secondary usage should be prohibited. I just want technologists to recognise that privacy law is actually very clear on Collection and on Use &amp; Disclosure.  You might not be saying otherwise &#8230; but the publicness of any particular information does not in and of itself mean that it escapes information privacy law.  </p>
<p>Your blog opened with a line about technologsts seeing a simple distinction, and I merely used that as a jumping off point for my argument that that particular distinction is unhelpful.  In fact, it betrays a category error that makes it difficult for technologists to engage in the privacy debate.  My thesis is that technologists and privacy policy wonks have very different frames of reference. </p>
<p>Again, sorry to have used your blog as a platform! </p>
<p>Cheers, </p>
<p>Stephen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arvind</title>
		<link>http://33bits.org/2010/04/05/is-making-public-data-more-public-a-privacy-violation/#comment-1445</link>
		<dc:creator><![CDATA[Arvind]]></dc:creator>
		<pubDate>Sun, 30 May 2010 00:30:11 +0000</pubDate>
		<guid isPermaLink="false">http://33bits.org/?p=460#comment-1445</guid>
		<description><![CDATA[Stephen,

You make some good points, but let me clarify a couple of things.

Firstly, my article is absolutely not about whether or not making data more public is a violation of the law. Rather, it is about whether or not it is a violation of users’ expectations. You can have a privacy disaster even if you are perfectly compliant with information privacy law. That is largely the setting that I’m concerned with.

You say,

“The public-private dichotomy is intractable, and technologists should learn to avoid it altogether.” You also say that all secondary uses of data are, or should be, prohibited.

I think that is just silly. Today’s web would simply cease to exist without the secondary usage of data. (If the law prohibits it, then it will be worked around.) Far from avoiding the public-private distinction, it is crucial for technologists to learn to navigate it.

Finally, nobody is arguing that it was OK for Google to collect WiFi data. Bringing that up is a red herring and is counterproductive.]]></description>
		<content:encoded><![CDATA[<p>Stephen,</p>
<p>You make some good points, but let me clarify a couple of things.</p>
<p>Firstly, my article is absolutely not about whether or not making data more public is a violation of the law. Rather, it is about whether or not it is a violation of users’ expectations. You can have a privacy disaster even if you are perfectly compliant with information privacy law. That is largely the setting that I’m concerned with.</p>
<p>You say,</p>
<p>“The public-private dichotomy is intractable, and technologists should learn to avoid it altogether.” You also say that all secondary uses of data are, or should be, prohibited.</p>
<p>I think that is just silly. Today’s web would simply cease to exist without the secondary usage of data. (If the law prohibits it, then it will be worked around.) Far from avoiding the public-private distinction, it is crucial for technologists to learn to navigate it.</p>
<p>Finally, nobody is arguing that it was OK for Google to collect WiFi data. Bringing that up is a red herring and is counterproductive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Wilson</title>
		<link>http://33bits.org/2010/04/05/is-making-public-data-more-public-a-privacy-violation/#comment-1443</link>
		<dc:creator><![CDATA[Stephen Wilson]]></dc:creator>
		<pubDate>Sat, 29 May 2010 23:16:54 +0000</pubDate>
		<guid isPermaLink="false">http://33bits.org/?p=460#comment-1443</guid>
		<description><![CDATA[&quot;Technologists draw a simple distinction between data that is public and data that is not&quot;.  This is a great example of where technologists as a class tend not to understand privacy protection, because the public-private distinction is not important at law.  In information privacy law, the terms&quot;public&quot; and &quot;private&quot; are generally avoided, and instead what matters is whether or not information is personally identifiable. 

Obviously there are shades of grey in gauging identifiability, but it&#039;s a much more tangible and measureable quality than &#039;publicness&#039;.  As you say there are &quot;entire philosophical theories devoted to understanding what one can and cannot do with public data in different contexts&quot;.  That is, the public-private dichotomy is intractable, and technologists should learn to avoid it altogether. 

Technologists need to understand this: Most information privacy law prohibits the collection of personal information without a good reason or consent, and the arbitrary secondary use of information collected for an original purpose.  These principles are basically blind to whether the source data is &quot;public&quot; or &quot;private&quot;.  So a whole lot of personal information might be available in &quot;public&quot; over open wifi networks, but it does not follow that Google and others may collect that information and do with it as they like. 

The fact that information privacy law doesn&#039;t care if information is &quot;public&quot; might be counterintuitive to many technologists, but that&#039;s they way the law is.  And ignorance of the law is no excuse! 

Stephen Wilson, Lockstep, Australia.]]></description>
		<content:encoded><![CDATA[<p>&#8220;Technologists draw a simple distinction between data that is public and data that is not&#8221;.  This is a great example of where technologists as a class tend not to understand privacy protection, because the public-private distinction is not important at law.  In information privacy law, the terms&#8221;public&#8221; and &#8220;private&#8221; are generally avoided, and instead what matters is whether or not information is personally identifiable. </p>
<p>Obviously there are shades of grey in gauging identifiability, but it&#8217;s a much more tangible and measureable quality than &#8216;publicness&#8217;.  As you say there are &#8220;entire philosophical theories devoted to understanding what one can and cannot do with public data in different contexts&#8221;.  That is, the public-private dichotomy is intractable, and technologists should learn to avoid it altogether. </p>
<p>Technologists need to understand this: Most information privacy law prohibits the collection of personal information without a good reason or consent, and the arbitrary secondary use of information collected for an original purpose.  These principles are basically blind to whether the source data is &#8220;public&#8221; or &#8220;private&#8221;.  So a whole lot of personal information might be available in &#8220;public&#8221; over open wifi networks, but it does not follow that Google and others may collect that information and do with it as they like. </p>
<p>The fact that information privacy law doesn&#8217;t care if information is &#8220;public&#8221; might be counterintuitive to many technologists, but that&#8217;s they way the law is.  And ignorance of the law is no excuse! </p>
<p>Stephen Wilson, Lockstep, Australia.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arvind</title>
		<link>http://33bits.org/2010/04/05/is-making-public-data-more-public-a-privacy-violation/#comment-1398</link>
		<dc:creator><![CDATA[Arvind]]></dc:creator>
		<pubDate>Fri, 14 May 2010 19:00:02 +0000</pubDate>
		<guid isPermaLink="false">http://33bits.org/?p=460#comment-1398</guid>
		<description><![CDATA[One can hope so. Some people I know are working on just that. It is one thing for (say) a civil liberties organization to publicize data to raise awareness, and quite another for someone with a commercial motive to do so. I&#039;m analyzing the latter in this article.]]></description>
		<content:encoded><![CDATA[<p>One can hope so. Some people I know are working on just that. It is one thing for (say) a civil liberties organization to publicize data to raise awareness, and quite another for someone with a commercial motive to do so. I&#8217;m analyzing the latter in this article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: R. Sinohara</title>
		<link>http://33bits.org/2010/04/05/is-making-public-data-more-public-a-privacy-violation/#comment-1397</link>
		<dc:creator><![CDATA[R. Sinohara]]></dc:creator>
		<pubDate>Fri, 14 May 2010 13:10:10 +0000</pubDate>
		<guid isPermaLink="false">http://33bits.org/?p=460#comment-1397</guid>
		<description><![CDATA[Really, this binary distinction between public and non-public is really the best way to go? That kinda seems to be the problem.

I really believe there is a difference between some data being available and somebody go around publishing it.

Doesn&#039;t &#039;publish&#039; originally mean actively go around distributing information (witch is quantifiable)? That seems different than passively giving access to data.]]></description>
		<content:encoded><![CDATA[<p>Really, this binary distinction between public and non-public is really the best way to go? That kinda seems to be the problem.</p>
<p>I really believe there is a difference between some data being available and somebody go around publishing it.</p>
<p>Doesn&#8217;t &#8216;publish&#8217; originally mean actively go around distributing information (witch is quantifiable)? That seems different than passively giving access to data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: R. Sinohara</title>
		<link>http://33bits.org/2010/04/05/is-making-public-data-more-public-a-privacy-violation/#comment-1396</link>
		<dc:creator><![CDATA[R. Sinohara]]></dc:creator>
		<pubDate>Fri, 14 May 2010 13:06:07 +0000</pubDate>
		<guid isPermaLink="false">http://33bits.org/?p=460#comment-1396</guid>
		<description><![CDATA[About identity thievery, isn’t making hard-to-find but still available information easier to find going to make people more aware of how public such information is and thus get them to be more careful, and make authentication methods better?]]></description>
		<content:encoded><![CDATA[<p>About identity thievery, isn’t making hard-to-find but still available information easier to find going to make people more aware of how public such information is and thus get them to be more careful, and make authentication methods better?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luc</title>
		<link>http://33bits.org/2010/04/05/is-making-public-data-more-public-a-privacy-violation/#comment-1343</link>
		<dc:creator><![CDATA[Luc]]></dc:creator>
		<pubDate>Wed, 14 Apr 2010 20:29:41 +0000</pubDate>
		<guid isPermaLink="false">http://33bits.org/?p=460#comment-1343</guid>
		<description><![CDATA[Considering that you do your purchases in public, is it hard to argue that credit card companies could publicly give access to your purchase history (date and items)?  

Is a conversation between two people at the shopping mall, public or private?

In life, we develop a construct of privacy. We create our expectations and we adjust ourselves to situations by lowering our voice or raising the music.  Technology, on the other hand, evolves more rapidly than our ability to change our behavior.  We still &quot;expect&quot; an email to be private. We &quot;expect&quot; that our IRC conversations are not &quot;overheard&quot;.  

I don&#039;t deny that our &quot;public&quot; information can be useful for commercial or scientific purposes. What is often lacking is the knowledge that our information in a certain situation CAN be &quot;searched, archived, and distributed beyond the expected audience&quot; before we expose the information.  

As information sharing is linked to many revenue models, it is often protected (poor Pete), not clearly stated and often hidden in the fine prints of a ten-page policy. 

Good luck with the model.]]></description>
		<content:encoded><![CDATA[<p>Considering that you do your purchases in public, is it hard to argue that credit card companies could publicly give access to your purchase history (date and items)?  </p>
<p>Is a conversation between two people at the shopping mall, public or private?</p>
<p>In life, we develop a construct of privacy. We create our expectations and we adjust ourselves to situations by lowering our voice or raising the music.  Technology, on the other hand, evolves more rapidly than our ability to change our behavior.  We still &#8220;expect&#8221; an email to be private. We &#8220;expect&#8221; that our IRC conversations are not &#8220;overheard&#8221;.  </p>
<p>I don&#8217;t deny that our &#8220;public&#8221; information can be useful for commercial or scientific purposes. What is often lacking is the knowledge that our information in a certain situation CAN be &#8220;searched, archived, and distributed beyond the expected audience&#8221; before we expose the information.  </p>
<p>As information sharing is linked to many revenue models, it is often protected (poor Pete), not clearly stated and often hidden in the fine prints of a ten-page policy. </p>
<p>Good luck with the model.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arvind</title>
		<link>http://33bits.org/2010/04/05/is-making-public-data-more-public-a-privacy-violation/#comment-1329</link>
		<dc:creator><![CDATA[Arvind]]></dc:creator>
		<pubDate>Tue, 06 Apr 2010 03:00:55 +0000</pubDate>
		<guid isPermaLink="false">http://33bits.org/?p=460#comment-1329</guid>
		<description><![CDATA[Thanks for that link. As for boyd&#039;s claim, I think her meaning is clear enough: people often post things publicly that they intend only their friends to read. In fact the majority of online posts probably fall into this category. One can argue whether or not technologists have a duty to respect that, but I don&#039;t think there&#039;s anything made-up here.]]></description>
		<content:encoded><![CDATA[<p>Thanks for that link. As for boyd&#8217;s claim, I think her meaning is clear enough: people often post things publicly that they intend only their friends to read. In fact the majority of online posts probably fall into this category. One can argue whether or not technologists have a duty to respect that, but I don&#8217;t think there&#8217;s anything made-up here.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

