<?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: Musing lazily about catch-and-release and its application in the digital world</title>
	<atom:link href="http://confusedofcalcutta.com/2009/01/03/musing-lazily-about-catch-and-release-and-its-application-in-the-digital-world/feed/" rel="self" type="application/rss+xml" />
	<link>http://confusedofcalcutta.com/2009/01/03/musing-lazily-about-catch-and-release-and-its-application-in-the-digital-world/</link>
	<description>a blog about information</description>
	<lastBuildDate>Mon, 06 Feb 2012 01:37:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Alexander Ainslie</title>
		<link>http://confusedofcalcutta.com/2009/01/03/musing-lazily-about-catch-and-release-and-its-application-in-the-digital-world/comment-page-1/#comment-460668</link>
		<dc:creator>Alexander Ainslie</dc:creator>
		<pubDate>Sun, 04 Jan 2009 23:32:28 +0000</pubDate>
		<guid isPermaLink="false">http://confusedofcalcutta.com/?p=1522#comment-460668</guid>
		<description>JP:  Happy New Year to your family and self from snowy Milwaukee! 

There is an ancient Brahmin saying that goes like so: &quot;When the desire to possess disappears - The joy appears&quot;

The concept of the catch-and-release model may be much older than we think!</description>
		<content:encoded><![CDATA[<p>JP:  Happy New Year to your family and self from snowy Milwaukee! </p>
<p>There is an ancient Brahmin saying that goes like so: &#8220;When the desire to possess disappears &#8211; The joy appears&#8221;</p>
<p>The concept of the catch-and-release model may be much older than we think!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JP</title>
		<link>http://confusedofcalcutta.com/2009/01/03/musing-lazily-about-catch-and-release-and-its-application-in-the-digital-world/comment-page-1/#comment-460473</link>
		<dc:creator>JP</dc:creator>
		<pubDate>Sun, 04 Jan 2009 09:54:55 +0000</pubDate>
		<guid isPermaLink="false">http://confusedofcalcutta.com/?p=1522#comment-460473</guid>
		<description>You&#039;re getting closer to what I was going for. I too am no fan of DRM because it pollutes the path, so I was looking for something like a library card, letting me use 10 books at a time, merged with the read and release model of bookcrossing, all against the backdrop of the cloud.</description>
		<content:encoded><![CDATA[<p>You&#8217;re getting closer to what I was going for. I too am no fan of DRM because it pollutes the path, so I was looking for something like a library card, letting me use 10 books at a time, merged with the read and release model of bookcrossing, all against the backdrop of the cloud.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oliver</title>
		<link>http://confusedofcalcutta.com/2009/01/03/musing-lazily-about-catch-and-release-and-its-application-in-the-digital-world/comment-page-1/#comment-460472</link>
		<dc:creator>Oliver</dc:creator>
		<pubDate>Sun, 04 Jan 2009 09:42:58 +0000</pubDate>
		<guid isPermaLink="false">http://confusedofcalcutta.com/?p=1522#comment-460472</guid>
		<description>Apologies for the serial comment, JP. I was not only musing lazily, I was also &lt;em&gt;reading&lt;/em&gt; lazily (more likely, sleepily: I haven&#039;t yet had more than three hours of sleep this weekend.)

I didn&#039;t notice that you had tagged this post with DRM and IPR. So it &lt;em&gt;is&lt;/em&gt; a particular usage of DRM you&#039;re suggesting (rather than a general idea that might require DRM). I guess, scratch the whole part where I assumed otherwise. My criticism of DRM still stands, but let&#039;s put that aside for the time being.

Interestingly, with catch-release, the issues surrounding accessibility of content you buy, when the technology changes, is less of an issue, because there is no ownership of the copies. Now I see what you were getting at (I think?)</description>
		<content:encoded><![CDATA[<p>Apologies for the serial comment, JP. I was not only musing lazily, I was also <em>reading</em> lazily (more likely, sleepily: I haven&#8217;t yet had more than three hours of sleep this weekend.)</p>
<p>I didn&#8217;t notice that you had tagged this post with DRM and IPR. So it <em>is</em> a particular usage of DRM you&#8217;re suggesting (rather than a general idea that might require DRM). I guess, scratch the whole part where I assumed otherwise. My criticism of DRM still stands, but let&#8217;s put that aside for the time being.</p>
<p>Interestingly, with catch-release, the issues surrounding accessibility of content you buy, when the technology changes, is less of an issue, because there is no ownership of the copies. Now I see what you were getting at (I think?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oliver</title>
		<link>http://confusedofcalcutta.com/2009/01/03/musing-lazily-about-catch-and-release-and-its-application-in-the-digital-world/comment-page-1/#comment-460468</link>
		<dc:creator>Oliver</dc:creator>
		<pubDate>Sun, 04 Jan 2009 09:14:47 +0000</pubDate>
		<guid isPermaLink="false">http://confusedofcalcutta.com/?p=1522#comment-460468</guid>
		<description>JP: thought provoking. I thought--oh, something like Netflix? But that is where I got stuck, because digital media and DVDs are different kinds of obejcts. This are really Lawrence Lessig&#039;s observations I&#039;m paraphrasing. 

DVDs, books, CDs are physical containers for information. We access the information through these containers. They are physical objects constrained to be in one place at one time. We can extract the information, or duplicate the container (more or less) and everything inside, but that takes extra effort, and it&#039;s more natural to move the container from one place or another.

Digital media is already pure information. We largely no longer deal with the containers&#8212;the hard drives, flash memory, volitile RAM, etc. Sure, we reference them by files or packets, but that&#039;s meta-level organization that is &lt;em&gt;also&lt;/em&gt; just pure information. The only way of taking information in one place and placing the same elsewhere is making a copy.  &quot;Moving&quot; it is another step&#8212;we copy, then delete the source.

We can see why trying to regard already pure information like physical containers feels so unnatural. And we&#039;ve heard the discussion about DRM&#8212;and the dangers it imposes.

I&#039;m guessing you&#039;re not trying to get at some specific DRM model.

Maybe the main cool thing about BookCrossing we&#039;re trying to reproduce translates to local caching of only the stuff you&#039;re using at the moment. I really respect that point. Streaming media aims to do the same, but is only useful when there is a sufficiently fast and reliable network connection, something not always possible or convenient. So having an entire working copy is often much better.

But this working copy takes up space, so when it&#039;s not being used, we get rid of it. But why impose a system that forces you to do so? (Not saying you&#039;re necessarily requiring this.) Is mainly to make the content providers happier? Automate the process as you&#039;d like, it amounts, again, to deleting a copy. Anything further, and we&#039;re back at DRM.

Using the example of music, the DRM version of this is, from what I know, the download portion of the Rhapsody music service. It seems nice until you realize that you&#039;re very limited in how you can listen to music&#8212;only through the Rhapsody program, or in approved players. It tries to reproduce the behavior of physical containers, but it doesn&#039;t map.

With Netflix, you get the DVDs, and you can play it in any DVD player you want. (Region coding and DeCSS issues aside.) With BookCrossing or even the public library, you can read the books you acquire standing up, lying down, in red light, through a magnifying glass. You can have someone else read it aloud to you.

We need to get away from confusing physical objects with the information they contain, and also recognize that digital content (below the level of the hard drive) is already free of physical constraints (in itself).

So what I can salvage is really the part about storage. I think this reduces to better stream-on-demand. This depends on a faster, more robust connection between the endpoint and the cloud, and ensuring that the content is delivered in a standard, open way (across content providers).

There&#039;s a chance I completely misunderstood this whole thing. I&#039;m also musing lazily.</description>
		<content:encoded><![CDATA[<p>JP: thought provoking. I thought&#8211;oh, something like Netflix? But that is where I got stuck, because digital media and DVDs are different kinds of obejcts. This are really Lawrence Lessig&#8217;s observations I&#8217;m paraphrasing. </p>
<p>DVDs, books, CDs are physical containers for information. We access the information through these containers. They are physical objects constrained to be in one place at one time. We can extract the information, or duplicate the container (more or less) and everything inside, but that takes extra effort, and it&#8217;s more natural to move the container from one place or another.</p>
<p>Digital media is already pure information. We largely no longer deal with the containers&mdash;the hard drives, flash memory, volitile RAM, etc. Sure, we reference them by files or packets, but that&#8217;s meta-level organization that is <em>also</em> just pure information. The only way of taking information in one place and placing the same elsewhere is making a copy.  &#8220;Moving&#8221; it is another step&mdash;we copy, then delete the source.</p>
<p>We can see why trying to regard already pure information like physical containers feels so unnatural. And we&#8217;ve heard the discussion about DRM&mdash;and the dangers it imposes.</p>
<p>I&#8217;m guessing you&#8217;re not trying to get at some specific DRM model.</p>
<p>Maybe the main cool thing about BookCrossing we&#8217;re trying to reproduce translates to local caching of only the stuff you&#8217;re using at the moment. I really respect that point. Streaming media aims to do the same, but is only useful when there is a sufficiently fast and reliable network connection, something not always possible or convenient. So having an entire working copy is often much better.</p>
<p>But this working copy takes up space, so when it&#8217;s not being used, we get rid of it. But why impose a system that forces you to do so? (Not saying you&#8217;re necessarily requiring this.) Is mainly to make the content providers happier? Automate the process as you&#8217;d like, it amounts, again, to deleting a copy. Anything further, and we&#8217;re back at DRM.</p>
<p>Using the example of music, the DRM version of this is, from what I know, the download portion of the Rhapsody music service. It seems nice until you realize that you&#8217;re very limited in how you can listen to music&mdash;only through the Rhapsody program, or in approved players. It tries to reproduce the behavior of physical containers, but it doesn&#8217;t map.</p>
<p>With Netflix, you get the DVDs, and you can play it in any DVD player you want. (Region coding and DeCSS issues aside.) With BookCrossing or even the public library, you can read the books you acquire standing up, lying down, in red light, through a magnifying glass. You can have someone else read it aloud to you.</p>
<p>We need to get away from confusing physical objects with the information they contain, and also recognize that digital content (below the level of the hard drive) is already free of physical constraints (in itself).</p>
<p>So what I can salvage is really the part about storage. I think this reduces to better stream-on-demand. This depends on a faster, more robust connection between the endpoint and the cloud, and ensuring that the content is delivered in a standard, open way (across content providers).</p>
<p>There&#8217;s a chance I completely misunderstood this whole thing. I&#8217;m also musing lazily.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

