<?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/"
		>
<channel>
	<title>Comments on: digging tahoe; wattage update; @fontface!</title>
	<atom:link href="http://www.oblomovka.com/wp/2008/08/12/digging-tahoe-wattage-update-fontface/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.oblomovka.com/wp/2008/08/12/digging-tahoe-wattage-update-fontface/</link>
	<description>Casual Dismissals from Danny O'Brien</description>
	<lastBuildDate>Tue, 20 Jul 2010 11:15:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Danny O'Brien</title>
		<link>http://www.oblomovka.com/wp/2008/08/12/digging-tahoe-wattage-update-fontface/comment-page-1/#comment-223</link>
		<dc:creator>Danny O'Brien</dc:creator>
		<pubDate>Thu, 14 Aug 2008 05:12:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.oblomovka.com/wp/?p=1026#comment-223</guid>
		<description>Right, Nick, that&#039;s a lot of what&#039;s interesting about Tahoe, which uses that approach: identical data is (or can be) stored in identical &quot;locations&quot;. The key is derived from the content, so if you have the content you can find where its located (and if you need it back, you know how to retrieve it).

As it turns out, there are some privacy implications to &quot;commodity data&quot;, though, and not just the ones where the RIAA (or the US government) is suddenly very interested in what particular &quot;commodity data&quot; you share with their database of copyrighted works or terrorist reading matter. 

For one thing, if I&#039;m understanding the issue correctly, you can effectively do the equivalent of dictionary attacks on particular file variants. So, for instance, lots of people store root MySQL passwords in effectively the same format in a file called .my.cnf. You generate a huge load of .my.cnfs with a dictionary of commonly used passwords, and then find out who has that file (or is asking for it).

You can read: https://zooko.com/convergent_encryption_reconsidered.html for the gory details, and some ways to mitigate.</description>
		<content:encoded><![CDATA[<p>Right, Nick, that&#8217;s a lot of what&#8217;s interesting about Tahoe, which uses that approach: identical data is (or can be) stored in identical &#8220;locations&#8221;. The key is derived from the content, so if you have the content you can find where its located (and if you need it back, you know how to retrieve it).</p>
<p>As it turns out, there are some privacy implications to &#8220;commodity data&#8221;, though, and not just the ones where the RIAA (or the US government) is suddenly very interested in what particular &#8220;commodity data&#8221; you share with their database of copyrighted works or terrorist reading matter. </p>
<p>For one thing, if I&#8217;m understanding the issue correctly, you can effectively do the equivalent of dictionary attacks on particular file variants. So, for instance, lots of people store root MySQL passwords in effectively the same format in a file called .my.cnf. You generate a huge load of .my.cnfs with a dictionary of commonly used passwords, and then find out who has that file (or is asking for it).</p>
<p>You can read: <a href="https://zooko.com/convergent_encryption_reconsidered.html" rel="nofollow">https://zooko.com/convergent_encryption_reconsidered.html</a> for the gory details, and some ways to mitigate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nick s</title>
		<link>http://www.oblomovka.com/wp/2008/08/12/digging-tahoe-wattage-update-fontface/comment-page-1/#comment-219</link>
		<dc:creator>nick s</dc:creator>
		<pubDate>Wed, 13 Aug 2008 22:16:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.oblomovka.com/wp/?p=1026#comment-219</guid>
		<description>A sporadic point I&#039;ve made &lt;a href=&quot;http://www.haloscan.com/comments/dannyobrien/DeathByBoredom/&quot; rel=&quot;nofollow&quot;&gt;at this here site&lt;/a&gt; is that a large amount of the data we have sloshing around these days is &#039;commodity data&#039;, which can be reimagined as key/value pairs, and the stuff that&#039;s &#039;personal data&#039; can be re-imagined as diffs.  As Don Marti said in that linked thread: &quot;Once you get to key/value instead of structured query, you can decentralize radically.&quot;</description>
		<content:encoded><![CDATA[<p>A sporadic point I&#8217;ve made <a href="http://www.haloscan.com/comments/dannyobrien/DeathByBoredom/" rel="nofollow">at this here site</a> is that a large amount of the data we have sloshing around these days is &#8216;commodity data&#8217;, which can be reimagined as key/value pairs, and the stuff that&#8217;s &#8216;personal data&#8217; can be re-imagined as diffs.  As Don Marti said in that linked thread: &#8220;Once you get to key/value instead of structured query, you can decentralize radically.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Fitzhardinge</title>
		<link>http://www.oblomovka.com/wp/2008/08/12/digging-tahoe-wattage-update-fontface/comment-page-1/#comment-216</link>
		<dc:creator>Jeremy Fitzhardinge</dc:creator>
		<pubDate>Wed, 13 Aug 2008 18:26:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.oblomovka.com/wp/?p=1026#comment-216</guid>
		<description>What kinds of things do you think DDDS might be useful for, even in the most handwavy terms?  A way of discovering storage grids and other services?  A way of mapping a file capability to some way to actually get the file?

I read the RFCs and my eyes glaze over before getting anywhere.  &quot;It is very important to note that it is impossible to read and understand a single document in that series without reading the related documents.&quot; Indeed.</description>
		<content:encoded><![CDATA[<p>What kinds of things do you think DDDS might be useful for, even in the most handwavy terms?  A way of discovering storage grids and other services?  A way of mapping a file capability to some way to actually get the file?</p>
<p>I read the RFCs and my eyes glaze over before getting anywhere.  &#8220;It is very important to note that it is impossible to read and understand a single document in that series without reading the related documents.&#8221; Indeed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee Maguire</title>
		<link>http://www.oblomovka.com/wp/2008/08/12/digging-tahoe-wattage-update-fontface/comment-page-1/#comment-207</link>
		<dc:creator>Lee Maguire</dc:creator>
		<pubDate>Wed, 13 Aug 2008 10:00:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.oblomovka.com/wp/?p=1026#comment-207</guid>
		<description>&quot;But then again, a stiff breeze caused Netscape 4 to crash.&quot;

I imagine there are still thousands of still personal shell aliases out there still enabled that grep for the netscape pid in ps output and &quot;kill -HUP&quot; it.</description>
		<content:encoded><![CDATA[<p>&#8220;But then again, a stiff breeze caused Netscape 4 to crash.&#8221;</p>
<p>I imagine there are still thousands of still personal shell aliases out there still enabled that grep for the netscape pid in ps output and &#8220;kill -HUP&#8221; it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee Maguire</title>
		<link>http://www.oblomovka.com/wp/2008/08/12/digging-tahoe-wattage-update-fontface/comment-page-1/#comment-206</link>
		<dc:creator>Lee Maguire</dc:creator>
		<pubDate>Wed, 13 Aug 2008 09:56:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.oblomovka.com/wp/?p=1026#comment-206</guid>
		<description>I love getting unexpected updates on really old bugs.  A debian bug I filed in 2002 got resolved a couple of weeks ago and while I remember filing it, it definitely feels like a different person that did so.  Like receiving a message from your younger self.</description>
		<content:encoded><![CDATA[<p>I love getting unexpected updates on really old bugs.  A debian bug I filed in 2002 got resolved a couple of weeks ago and while I remember filing it, it definitely feels like a different person that did so.  Like receiving a message from your younger self.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rod Begbie</title>
		<link>http://www.oblomovka.com/wp/2008/08/12/digging-tahoe-wattage-update-fontface/comment-page-1/#comment-203</link>
		<dc:creator>Rod Begbie</dc:creator>
		<pubDate>Wed, 13 Aug 2008 07:36:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.oblomovka.com/wp/?p=1026#comment-203</guid>
		<description>Re: @fontface. I have this open in a tab, no idea how I found it: http://opentype.info/demo/webfontdemo.html

I still have some .pfr files kicking around on my personal server from experimenting with this stuff ten years ago.  I seem to recall it crashing Netscape 4 pretty hard on the SGI Indys at Uni.  But then again, a stiff breeze caused Netscape 4 to crash…</description>
		<content:encoded><![CDATA[<p>Re: @fontface. I have this open in a tab, no idea how I found it: <a href="http://opentype.info/demo/webfontdemo.html" rel="nofollow">http://opentype.info/demo/webfontdemo.html</a></p>
<p>I still have some .pfr files kicking around on my personal server from experimenting with this stuff ten years ago.  I seem to recall it crashing Netscape 4 pretty hard on the SGI Indys at Uni.  But then again, a stiff breeze caused Netscape 4 to crash…</p>
]]></content:encoded>
	</item>
</channel>
</rss>
