<?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: O&#8217;Reilly the victim of a Google security hole? And what about millions of other books?</title>
	<atom:link href="http://www.teleread.com/2005/12/28/oreilly-the-victim-of-a-google-security-hole-and-what-about-millions-of-other-books/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.teleread.com/uncategorized/oreilly-the-victim-of-a-google-security-hole-and-what-about-millions-of-other-books/</link>
	<description>News &#38; views on e-books, libraries, publishing and related topics</description>
	<lastBuildDate>Wed, 15 Feb 2012 17:02:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: bowerbird</title>
		<link>http://www.teleread.com/uncategorized/oreilly-the-victim-of-a-google-security-hole-and-what-about-millions-of-other-books/comment-page-1/#comment-39596</link>
		<dc:creator>bowerbird</dc:creator>
		<pubDate>Thu, 29 Dec 2005 07:30:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/?p=4049#comment-39596</guid>
		<description>i really don&#039;t understand why you give
any credence at all to this whole matter.

there&#039;s nothing new in this &quot;revelation&quot;.

and there&#039;s no need to &quot;keep it secret&quot;;
a bloody idiot can figure out how to do it.
cheapskates i know realized this option
right off the bat.  it&#039;s not rocket science.

and if the people over at o&#039;reilly didn&#039;t
see this supposed &quot;hole&quot; before, then
maybe they ain&#039;t that smart after all.
(andy oram, are you listening?)

but i assure you the cookbook people
and the travel-guide people, and most
publishers that put out books that are
purchased on the basis of &quot;a few pages&quot;
sprinkled thoughout are well-acquainted
with the need to &quot;restrict&quot; those pages.

of course, such books are the ones that
have always exploited this &quot;necessity&quot;
for buying the whole book when all you
_really_ wanted was those few pages, so
maybe it&#039;s time to cut off those publishers.

(in the same way that itunes has helped to
hobble the record companies that put out
&quot;albums&quot; with just one or two good songs,
knowing we&#039;d have to buy the whole thing.)

it&#039;s not up to google to &quot;plug&quot; this &quot;leak&quot;.
the publisher just needs to specify that
all these &quot;special&quot; pages be &quot;restricted&quot;,
up to and even including the whole book.

hiding the totality of your content online
is like shrinkwrapping your paper-books --
it&#039;s a strategy that is doomed to failure...

so i _encourage_ all publishers to opt-out!
it&#039;s an excellent i.q. test for the new world,
and the fastest/best way to thin the herd.

-bowerbird</description>
		<content:encoded><![CDATA[<p>i really don&#8217;t understand why you give<br />
any credence at all to this whole matter.</p>
<p>there&#8217;s nothing new in this &#8220;revelation&#8221;.</p>
<p>and there&#8217;s no need to &#8220;keep it secret&#8221;;<br />
a bloody idiot can figure out how to do it.<br />
cheapskates i know realized this option<br />
right off the bat.  it&#8217;s not rocket science.</p>
<p>and if the people over at o&#8217;reilly didn&#8217;t<br />
see this supposed &#8220;hole&#8221; before, then<br />
maybe they ain&#8217;t that smart after all.<br />
(andy oram, are you listening?)</p>
<p>but i assure you the cookbook people<br />
and the travel-guide people, and most<br />
publishers that put out books that are<br />
purchased on the basis of &#8220;a few pages&#8221;<br />
sprinkled thoughout are well-acquainted<br />
with the need to &#8220;restrict&#8221; those pages.</p>
<p>of course, such books are the ones that<br />
have always exploited this &#8220;necessity&#8221;<br />
for buying the whole book when all you<br />
_really_ wanted was those few pages, so<br />
maybe it&#8217;s time to cut off those publishers.</p>
<p>(in the same way that itunes has helped to<br />
hobble the record companies that put out<br />
&#8220;albums&#8221; with just one or two good songs,<br />
knowing we&#8217;d have to buy the whole thing.)</p>
<p>it&#8217;s not up to google to &#8220;plug&#8221; this &#8220;leak&#8221;.<br />
the publisher just needs to specify that<br />
all these &#8220;special&#8221; pages be &#8220;restricted&#8221;,<br />
up to and even including the whole book.</p>
<p>hiding the totality of your content online<br />
is like shrinkwrapping your paper-books &#8211;<br />
it&#8217;s a strategy that is doomed to failure&#8230;</p>
<p>so i _encourage_ all publishers to opt-out!<br />
it&#8217;s an excellent i.q. test for the new world,<br />
and the fastest/best way to thin the herd.</p>
<p>-bowerbird</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Albrecht</title>
		<link>http://www.teleread.com/uncategorized/oreilly-the-victim-of-a-google-security-hole-and-what-about-millions-of-other-books/comment-page-1/#comment-39592</link>
		<dc:creator>Bruce Albrecht</dc:creator>
		<pubDate>Thu, 29 Dec 2005 07:13:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/?p=4049#comment-39592</guid>
		<description>Within the first six months after Google Print (Publisher) was launched, there were web discussions on how Google Print could be gamed to display entire books depending on the percent of the book the publisher allowed to be displayed.  If I recall correctly, some of the hacks may have allowed one to read the entire book even if the publisher had set the limit to less than 100%.  I thought perhaps this was a resurgence of one of these discussions, but in reality this is merely someone rediscovering the complaint that many authors have about Google Book Search (Publishers), which is that the publishers set the percentage of the book that may be viewed high enough that entire chapters may be read. In some cases, this means that instead of buying a book, the searchers will read the one chapter they really wanted out of a book at Google Book Search instead of buying it.  So if publishers consider this to be a problem, they&#039;ll either decrease the percentage of the books available for viewing, or try lobby Google to modify the book search on the publisher side to be more like the library side when a book is not in the public domain.</description>
		<content:encoded><![CDATA[<p>Within the first six months after Google Print (Publisher) was launched, there were web discussions on how Google Print could be gamed to display entire books depending on the percent of the book the publisher allowed to be displayed.  If I recall correctly, some of the hacks may have allowed one to read the entire book even if the publisher had set the limit to less than 100%.  I thought perhaps this was a resurgence of one of these discussions, but in reality this is merely someone rediscovering the complaint that many authors have about Google Book Search (Publishers), which is that the publishers set the percentage of the book that may be viewed high enough that entire chapters may be read. In some cases, this means that instead of buying a book, the searchers will read the one chapter they really wanted out of a book at Google Book Search instead of buying it.  So if publishers consider this to be a problem, they&#8217;ll either decrease the percentage of the books available for viewing, or try lobby Google to modify the book search on the publisher side to be more like the library side when a book is not in the public domain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Rothman</title>
		<link>http://www.teleread.com/uncategorized/oreilly-the-victim-of-a-google-security-hole-and-what-about-millions-of-other-books/comment-page-1/#comment-39577</link>
		<dc:creator>David Rothman</dc:creator>
		<pubDate>Thu, 29 Dec 2005 05:14:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/?p=4049#comment-39577</guid>
		<description>Bowerbird, I may be POed about Draconian copyright, but I&#039;m gonna run this blog as best I can with &lt;em&gt;both&lt;/em&gt; legal and ethical concerns in mind. In O&#039;Reilly&#039;s case, folks have treated Net folks well over the years. Maybe by now this thing has been Slashdotted, but until something like that happens--and I trust you won&#039;t be the one doing it--I&#039;ll withhold info that people could use to rip off  O&#039;Reilly. That is why I&#039;ve been so gung ho on not providing links to the offending blog or clues to its identity.

As for your concern with the new lead, what a hoot! Does this mean you&#039;ll go after PG in a big way for not disclosing trifles like the origins of their electronic editions? OK. Happy holidays and don&#039;t overdo the recreational drugs.

David

P.S. Later today I&#039;ll post O&#039;Reilly editor Andy Oram&#039;s comments, and people can see that O&#039;Reilly may indeed want to make things tougher for mouchers. May. Tim O. himself was out of town. Andy&#039;s just speculating.</description>
		<content:encoded><![CDATA[<p>Bowerbird, I may be POed about Draconian copyright, but I&#8217;m gonna run this blog as best I can with <em>both</em> legal and ethical concerns in mind. In O&#8217;Reilly&#8217;s case, folks have treated Net folks well over the years. Maybe by now this thing has been Slashdotted, but until something like that happens&#8211;and I trust you won&#8217;t be the one doing it&#8211;I&#8217;ll withhold info that people could use to rip off  O&#8217;Reilly. That is why I&#8217;ve been so gung ho on not providing links to the offending blog or clues to its identity.</p>
<p>As for your concern with the new lead, what a hoot! Does this mean you&#8217;ll go after PG in a big way for not disclosing trifles like the origins of their electronic editions? OK. Happy holidays and don&#8217;t overdo the recreational drugs.</p>
<p>David</p>
<p>P.S. Later today I&#8217;ll post O&#8217;Reilly editor Andy Oram&#8217;s comments, and people can see that O&#8217;Reilly may indeed want to make things tougher for mouchers. May. Tim O. himself was out of town. Andy&#8217;s just speculating.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bowerbird</title>
		<link>http://www.teleread.com/uncategorized/oreilly-the-victim-of-a-google-security-hole-and-what-about-millions-of-other-books/comment-page-1/#comment-39524</link>
		<dc:creator>bowerbird</dc:creator>
		<pubDate>Wed, 28 Dec 2005 20:32:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/?p=4049#comment-39524</guid>
		<description>by the way, david, it&#039;s kind of _unsettling_
-- to me anyway -- the way you so casually
rewrite history and call it &quot;tweaking the lead&quot;.

it seems it would be easy enough to instead
append updates in a clearly-marked section,
thus leaving the dialog-trail free of distortion.
it&#039;s only fair to own up to what you really said.

your blog, your call, but that&#039;s my opinion...

-bowerbird</description>
		<content:encoded><![CDATA[<p>by the way, david, it&#8217;s kind of _unsettling_<br />
&#8211; to me anyway &#8212; the way you so casually<br />
rewrite history and call it &#8220;tweaking the lead&#8221;.</p>
<p>it seems it would be easy enough to instead<br />
append updates in a clearly-marked section,<br />
thus leaving the dialog-trail free of distortion.<br />
it&#8217;s only fair to own up to what you really said.</p>
<p>your blog, your call, but that&#8217;s my opinion&#8230;</p>
<p>-bowerbird</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bowerbird</title>
		<link>http://www.teleread.com/uncategorized/oreilly-the-victim-of-a-google-security-hole-and-what-about-millions-of-other-books/comment-page-1/#comment-39522</link>
		<dc:creator>bowerbird</dc:creator>
		<pubDate>Wed, 28 Dec 2005 20:25:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/?p=4049#comment-39522</guid>
		<description>geez, david, why all the secrecy?
it&#039;s not like a determined person
can&#039;t easily find this themelves...

and your cutting of my quote of
what that blogger actually said
makes my comment unintelligble.
(he thought he had uncovered a
&quot;hole&quot; that was &quot;significant&quot; and
thus had &quot;beat&quot; google&#039;s system.)

for anyone who wants to know
the u.r.l. of this silly blog post,
e-mail me at bowerbird at aol dot com
or -- since the blogger _did_ post
my comments, you can probably
just google them.  (ironic, isn&#039;t it?)

by the way, a whole flock of people
have now commented that this &quot;bug&quot;
is actually the way the system works,
with &quot;protection&quot; against a person who
tries to read the whole book this way
in the form of &quot;restricted pages&quot;...

-bowerbird</description>
		<content:encoded><![CDATA[<p>geez, david, why all the secrecy?<br />
it&#8217;s not like a determined person<br />
can&#8217;t easily find this themelves&#8230;</p>
<p>and your cutting of my quote of<br />
what that blogger actually said<br />
makes my comment unintelligble.<br />
(he thought he had uncovered a<br />
&#8220;hole&#8221; that was &#8220;significant&#8221; and<br />
thus had &#8220;beat&#8221; google&#8217;s system.)</p>
<p>for anyone who wants to know<br />
the u.r.l. of this silly blog post,<br />
e-mail me at bowerbird at aol dot com<br />
or &#8212; since the blogger _did_ post<br />
my comments, you can probably<br />
just google them.  (ironic, isn&#8217;t it?)</p>
<p>by the way, a whole flock of people<br />
have now commented that this &#8220;bug&#8221;<br />
is actually the way the system works,<br />
with &#8220;protection&#8221; against a person who<br />
tries to read the whole book this way<br />
in the form of &#8220;restricted pages&#8221;&#8230;</p>
<p>-bowerbird</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://www.teleread.com/uncategorized/oreilly-the-victim-of-a-google-security-hole-and-what-about-millions-of-other-books/comment-page-1/#comment-39506</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Wed, 28 Dec 2005 18:39:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/?p=4049#comment-39506</guid>
		<description>It appears that the author of the &quot;hack&quot; has updated his post. A number of readers have commented that this really isn&#039;t a hack per se, but a function of how Google Book Search works. It should also be pointed out that O&#039;Reilly is a partner in the Google Book Search program (which is opt-in by the way) and provides the books to Google while controlling how much of the book can be displayed http://books.google.com/googlebooks/author_faq.html#4

It sounds to me that if O&#039;Reilly was really concerned about this, they&#039;d limit the number of page views available, which is pretty liberal. While the author of the &quot;hack&quot; implies that entire books can be read using his technique, based on the viewing restrictions (again, controlled by the publishers who opt-in) this is very unlikely or easily remedied while maintaining the value of the service so that this becomes a non-issue.</description>
		<content:encoded><![CDATA[<p>It appears that the author of the &#8220;hack&#8221; has updated his post. A number of readers have commented that this really isn&#8217;t a hack per se, but a function of how Google Book Search works. It should also be pointed out that O&#8217;Reilly is a partner in the Google Book Search program (which is opt-in by the way) and provides the books to Google while controlling how much of the book can be displayed <a href="http://books.google.com/googlebooks/author_faq.html#4" rel="nofollow">http://books.google.com/googlebooks/author_faq.html#4</a></p>
<p>It sounds to me that if O&#8217;Reilly was really concerned about this, they&#8217;d limit the number of page views available, which is pretty liberal. While the author of the &#8220;hack&#8221; implies that entire books can be read using his technique, based on the viewing restrictions (again, controlled by the publishers who opt-in) this is very unlikely or easily remedied while maintaining the value of the service so that this becomes a non-issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Rothman</title>
		<link>http://www.teleread.com/uncategorized/oreilly-the-victim-of-a-google-security-hole-and-what-about-millions-of-other-books/comment-page-1/#comment-39498</link>
		<dc:creator>David Rothman</dc:creator>
		<pubDate>Wed, 28 Dec 2005 17:44:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/?p=4049#comment-39498</guid>
		<description>Thanks for your thoughts, Brian. I myself hope there&#039;ll be a way to maintain the search service and allow for options such as viewing of &lt;em&gt;some&lt;/em&gt; of the short sections. Of course, if a publisher feels that all sections should be viewable, then so much the better!</description>
		<content:encoded><![CDATA[<p>Thanks for your thoughts, Brian. I myself hope there&#8217;ll be a way to maintain the search service and allow for options such as viewing of <em>some</em> of the short sections. Of course, if a publisher feels that all sections should be viewable, then so much the better!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://www.teleread.com/uncategorized/oreilly-the-victim-of-a-google-security-hole-and-what-about-millions-of-other-books/comment-page-1/#comment-39482</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Wed, 28 Dec 2005 16:28:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/?p=4049#comment-39482</guid>
		<description>[First name deleted] (the author of the blog where this hack is discussed) mentions spending a lot of time reading different O&#039;Reilly books in bookstores without making a purchase, and example of &quot;real world&quot; behavior that really can&#039;t be prevented but pretty much accomplishes the same thing as this hack. Are bookstore browsing and the Google book search hack examples of behavior most likely engaged in by individuals who don&#039;t have any intention of buying books in the first place?

Google&#039;s stated purpose of Google book search is to help people find books, not to circumvent the process of obtaining a legitimate copy (real or electronic). 

&quot;What is Google Book Search?
Search the full text of books to find ones that interest you and learn where to buy or borrow them.&quot;

Simply put, Google book search makes books findable. Are the benefits of making books findable outweighed by a small number of people who are going to take advantage of the system to browse without buying? To use the bookstore browsing analogy: Should brick and mortar retailers put all of their books &quot;behind the counter&quot; to foil the browsers who don&#039;t buy? 

On the other hand, does indexing the complete text of published works to make them more findable on the web necessarily have to include making excepts visible in the search results? Is this what the Authors Guild objects to the most, or is it the possibility of Google somehow monetizing content without compensating authors and publishers?

Synchronicity and/or irony: I&#039;m currently reading the O&#039;Reilly title Ambient Findability by Peter Morville where he discusses the importance of findability on the web, and I&#039;d be interested to hear the author&#039;s thoughts on this hack so I&#039;ll send him an email.</description>
		<content:encoded><![CDATA[<p>[First name deleted] (the author of the blog where this hack is discussed) mentions spending a lot of time reading different O&#8217;Reilly books in bookstores without making a purchase, and example of &#8220;real world&#8221; behavior that really can&#8217;t be prevented but pretty much accomplishes the same thing as this hack. Are bookstore browsing and the Google book search hack examples of behavior most likely engaged in by individuals who don&#8217;t have any intention of buying books in the first place?</p>
<p>Google&#8217;s stated purpose of Google book search is to help people find books, not to circumvent the process of obtaining a legitimate copy (real or electronic). </p>
<p>&#8220;What is Google Book Search?<br />
Search the full text of books to find ones that interest you and learn where to buy or borrow them.&#8221;</p>
<p>Simply put, Google book search makes books findable. Are the benefits of making books findable outweighed by a small number of people who are going to take advantage of the system to browse without buying? To use the bookstore browsing analogy: Should brick and mortar retailers put all of their books &#8220;behind the counter&#8221; to foil the browsers who don&#8217;t buy? </p>
<p>On the other hand, does indexing the complete text of published works to make them more findable on the web necessarily have to include making excepts visible in the search results? Is this what the Authors Guild objects to the most, or is it the possibility of Google somehow monetizing content without compensating authors and publishers?</p>
<p>Synchronicity and/or irony: I&#8217;m currently reading the O&#8217;Reilly title Ambient Findability by Peter Morville where he discusses the importance of findability on the web, and I&#8217;d be interested to hear the author&#8217;s thoughts on this hack so I&#8217;ll send him an email.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://www.teleread.com/uncategorized/oreilly-the-victim-of-a-google-security-hole-and-what-about-millions-of-other-books/comment-page-1/#comment-39467</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Wed, 28 Dec 2005 15:19:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/?p=4049#comment-39467</guid>
		<description>There is a difference between modifying a piece of hardware that you have *bought and paid for* (emphasis important) to put it to other uses, and engaging in copyright infringement. One is legal, the other is not.</description>
		<content:encoded><![CDATA[<p>There is a difference between modifying a piece of hardware that you have *bought and paid for* (emphasis important) to put it to other uses, and engaging in copyright infringement. One is legal, the other is not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Rothman</title>
		<link>http://www.teleread.com/uncategorized/oreilly-the-victim-of-a-google-security-hole-and-what-about-millions-of-other-books/comment-page-1/#comment-39437</link>
		<dc:creator>David Rothman</dc:creator>
		<pubDate>Wed, 28 Dec 2005 10:09:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/?p=4049#comment-39437</guid>
		<description>For the most part, I agree with Bowerbird. My original post raised the issue of whether the hack was really new, and I&#039;ve tweaked the lead of the post to emphasize this. As for how much money is at stake, in the case of O&#039;Reilly and other publishers as a percentage of total revenue, I don&#039;t know. Hopefully not much, if such mouchers wouldn&#039;t buy the books anyway. Still, I&#039;d feel uncomfortable spreading around the how-to, so I don&#039;t.

What&#039;s interesting is that O&#039;Relly itself has published tips that interfere with others&#039; business models. Not much--but &lt;a href=&quot;http://www.makezine.com/blog/archive/2005/08/how_to_cvs_vide_1.html&quot;&gt;some&lt;/a&gt;. I&#039;d side with O&#039;Reilly here, but I can appreciate the complexities. What happens if you tell how to turn a disposable video recorder into a reusble one, for example? Are you playing &lt;a href=&quot;http://en.wikipedia.org/wiki/Fagin&quot;&gt;Fagin&lt;/a&gt;?</description>
		<content:encoded><![CDATA[<p>For the most part, I agree with Bowerbird. My original post raised the issue of whether the hack was really new, and I&#8217;ve tweaked the lead of the post to emphasize this. As for how much money is at stake, in the case of O&#8217;Reilly and other publishers as a percentage of total revenue, I don&#8217;t know. Hopefully not much, if such mouchers wouldn&#8217;t buy the books anyway. Still, I&#8217;d feel uncomfortable spreading around the how-to, so I don&#8217;t.</p>
<p>What&#8217;s interesting is that O&#8217;Relly itself has published tips that interfere with others&#8217; business models. Not much&#8211;but <a href="http://www.makezine.com/blog/archive/2005/08/how_to_cvs_vide_1.html">some</a>. I&#8217;d side with O&#8217;Reilly here, but I can appreciate the complexities. What happens if you tell how to turn a disposable video recorder into a reusble one, for example? Are you playing <a href="http://en.wikipedia.org/wiki/Fagin">Fagin</a>?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bowerbird</title>
		<link>http://www.teleread.com/uncategorized/oreilly-the-victim-of-a-google-security-hole-and-what-about-millions-of-other-books/comment-page-1/#comment-39436</link>
		<dc:creator>bowerbird</dc:creator>
		<pubDate>Wed, 28 Dec 2005 09:55:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/?p=4049#comment-39436</guid>
		<description>this &quot;significant flaw&quot; is that you can
read a few pages consecutively, which
might be &quot;enough&quot; in some situations,
such as in a cookbook or a travel-guide,
or (in this case) to learn a computer hack.

big deal!  here&#039;s the comment i left
at the blog, which probably will _not_
be allowed, because the blogger has to
&quot;approve all comments before posting&quot;.

[deleted first name] said:

[I deleted the quote to prevent cheapsakes from tracking down the blog via Feedster, in case the blogger does let Bowerbird&#039;s comments get through. - David.]

um, no.  are you joking?

i know lots of idiots who
figured this out long ago.

if you&#039;re too cheap to buy
the book in the first place,
as you [the blogger with the how-to - D.R.]
 freely admit, then
o&#039;reilly lost no money off
your tactic, so you &quot;beat&quot;
nobody, you little worm.

enjoy the free hacks!
and spread the word,
because you&#039;re helping
tim escape obscurity...

my goodness, the things
that can pass for &quot;clever&quot;
these days are astounding...

-bowerbird</description>
		<content:encoded><![CDATA[<p>this &#8220;significant flaw&#8221; is that you can<br />
read a few pages consecutively, which<br />
might be &#8220;enough&#8221; in some situations,<br />
such as in a cookbook or a travel-guide,<br />
or (in this case) to learn a computer hack.</p>
<p>big deal!  here&#8217;s the comment i left<br />
at the blog, which probably will _not_<br />
be allowed, because the blogger has to<br />
&#8220;approve all comments before posting&#8221;.</p>
<p>[deleted first name] said:</p>
<p>[I deleted the quote to prevent cheapsakes from tracking down the blog via Feedster, in case the blogger does let Bowerbird's comments get through. - David.]</p>
<p>um, no.  are you joking?</p>
<p>i know lots of idiots who<br />
figured this out long ago.</p>
<p>if you&#8217;re too cheap to buy<br />
the book in the first place,<br />
as you [the blogger with the how-to - D.R.]<br />
 freely admit, then<br />
o&#8217;reilly lost no money off<br />
your tactic, so you &#8220;beat&#8221;<br />
nobody, you little worm.</p>
<p>enjoy the free hacks!<br />
and spread the word,<br />
because you&#8217;re helping<br />
tim escape obscurity&#8230;</p>
<p>my goodness, the things<br />
that can pass for &#8220;clever&#8221;<br />
these days are astounding&#8230;</p>
<p>-bowerbird</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Database Caching using disk: basic
Object Caching 479/503 objects using disk: basic

Served from: www.teleread.com @ 2012-02-15 12:50:17 -->
