<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;C0AHSHg6eSp7ImA9WhdTEEQ.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738</id><updated>2011-07-07T22:22:19.611-04:00</updated><category term="kindle" /><category term="features" /><category term="pricing" /><category term="piracy" /><category term="copyright" /><category term="infringement" /><category term="law" /><category term="functionality" /><category term="copyright arms-race" /><category term="subscriptions" /><category term="stamp.la" /><title>DocMonk Blog</title><subtitle type="html">DocMonk is the web-based service that fights piracy by personalizing PDF documents for your readers.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://blog.docmonk.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://blog.docmonk.com/" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>20</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/Docmonk" /><feedburner:info uri="docmonk" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;CEQERH84eSp7ImA9WxFQE0s.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-6483874709143359584</id><published>2010-05-08T19:37:00.008-04:00</published><updated>2010-05-08T19:45:05.131-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-05-08T19:45:05.131-04:00</app:edited><title>DocMonk Marketplace - Coming Very Soon!</title><content type="html">&lt;div style="text-align: left;"&gt;We're working hard and putting the finishing touches on a new DocMonk site that makes it easy and fun to sell PDF documents online. The DocMonk Marketplace is in it's final stages (sneek peek below).&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;In a broad nutshell - here's what we're trying to do:&lt;/div&gt;&lt;div&gt;- Make it simple and easy for content holders to list PDF documents for sale.&lt;/div&gt;&lt;div&gt;- Make document listings work great and be easy to find by both people and the all-important search engines.&lt;/div&gt;&lt;div&gt;- Make the process of buying and receiving a personalized PDF document as quick and easy as possible.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;We're still several weeks from launch, but I just thought it was time to give you a heads up.&lt;/div&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;(click the images for a larger version)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_QXlH3SVhl-E/S-X20etd8xI/AAAAAAAAABo/n3seKb4cShI/s1600/marketplace_homepage.png"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 200px; height: 189px;" src="http://2.bp.blogspot.com/_QXlH3SVhl-E/S-X20etd8xI/AAAAAAAAABo/n3seKb4cShI/s200/marketplace_homepage.png" border="0" alt="" id="BLOGGER_PHOTO_ID_5469048703968736018" /&gt;&lt;/a&gt;&lt;span class="Apple-style-span"  style="color:#0000EE;"&gt;&lt;span class="Apple-style-span"  style="color:#000000;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="color: rgb(0, 0, 238); -webkit-text-decorations-in-effect: underline; "&gt;&lt;img src="http://4.bp.blogspot.com/_QXlH3SVhl-E/S-X3Ba6vwcI/AAAAAAAAABw/kFVwwF8Ji6E/s200/marketplace_listing.png" border="0" alt="" id="BLOGGER_PHOTO_ID_5469048926288986562" style="display: block; margin-top: 0px; margin-right: auto; margin-bottom: 10px; margin-left: auto; text-align: center; cursor: pointer; width: 200px; height: 189px; " /&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class="Apple-style-span"  style="color:#0000EE;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="color: rgb(0, 0, 238); -webkit-text-decorations-in-effect: underline; "&gt;&lt;span class="Apple-style-span" style="-webkit-text-decorations-in-effect: underline; "&gt;&lt;img src="http://3.bp.blogspot.com/_QXlH3SVhl-E/S-X3NFbbkmI/AAAAAAAAAB4/8nE8C5CmFXM/s200/searchresults.png" border="0" alt="" id="BLOGGER_PHOTO_ID_5469049126678925922" style="display: block; margin-top: 0px; margin-right: auto; margin-bottom: 10px; margin-left: auto; text-align: center; cursor: pointer; width: 200px; height: 189px; " /&gt;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="color: rgb(0, 0, 238); -webkit-text-decorations-in-effect: underline; "&gt;&lt;span class="Apple-style-span" style="-webkit-text-decorations-in-effect: underline; "&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="color: rgb(0, 0, 238); -webkit-text-decorations-in-effect: underline; "&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="color: rgb(0, 0, 238); -webkit-text-decorations-in-effect: underline; "&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="color: rgb(0, 0, 238); -webkit-text-decorations-in-effect: underline; "&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-6483874709143359584?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/S4u_ldY2OXw" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/6483874709143359584/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2010/05/docmonk-marketplace-coming-very-soon.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/6483874709143359584?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/6483874709143359584?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/S4u_ldY2OXw/docmonk-marketplace-coming-very-soon.html" title="DocMonk Marketplace - Coming Very Soon!" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_QXlH3SVhl-E/S-X20etd8xI/AAAAAAAAABo/n3seKb4cShI/s72-c/marketplace_homepage.png" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2010/05/docmonk-marketplace-coming-very-soon.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE4BSHg9eip7ImA9WxNUEUs.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-4194413168778035956</id><published>2009-11-02T08:00:00.001-05:00</published><updated>2009-11-02T08:02:39.662-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-02T08:02:39.662-05:00</app:edited><title>A Twitter/DRM Experiment</title><content type="html">A Twitter user imposed &lt;a href="http://ebooktest.wordpress.com/2009/02/11/my-twitter-guidelines/"&gt;strict rules&lt;/a&gt; for his followers.  All of the rules reflected this person's particular preferences about how exactly his Twitter feed should be used.  I'm not certain that this is any kind of valid test of anything, but his conclusions jibe with much of what DocMonk &lt;a href="http://blog.docmonk.com/2009_07_01_archive.html"&gt;stands&lt;/a&gt; &lt;a href="http://blog.docmonk.com/2009/10/do-heavy-handed-copyright-laws-work.html"&gt;for&lt;/a&gt;. For instance:&lt;br /&gt;&lt;blockquote&gt;Pushing anyone into a corner with no other alternatives will make that person see the odds as “I’ve got nothing to lose by fighting back.” Right now, the technical skills to break eBook copy-protection are not widespread. If you cage your customers, they’ll become “Nothing to lose” combatants and &lt;em&gt;will seek out the tools to break your DRM.&lt;/em&gt; They might even turn spiteful and go pirate, uploading those files for others. Most users who crack DRM simply do it in order to be able to read on more than one device they have &lt;em&gt;paid&lt;/em&gt; for. This is private-use “piracy” (in sensible minds, this is called Buyer’s Fair Use!). Don’t push them into becoming outright outlaws!&lt;/blockquote&gt;The rest is &lt;a href="http://ebooktest.wordpress.com/2009/02/11/my-twitter-guidelines/"&gt;here&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-4194413168778035956?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/nwsC_YB_h8E" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/4194413168778035956/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/11/twitterdrm-experiment.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/4194413168778035956?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/4194413168778035956?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/nwsC_YB_h8E/twitterdrm-experiment.html" title="A Twitter/DRM Experiment" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/11/twitterdrm-experiment.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUEFQ3k6eyp7ImA9WxNVEkw.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-1106491220552893277</id><published>2009-10-15T15:42:00.007-04:00</published><updated>2009-10-22T09:20:12.713-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-22T09:20:12.713-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="subscriptions" /><category scheme="http://www.blogger.com/atom/ns#" term="pricing" /><category scheme="http://www.blogger.com/atom/ns#" term="kindle" /><title>The Economist Magazine Embraces the Kindle as a Revenue Generator</title><content type="html">&lt;blockquote&gt;&lt;/blockquote&gt;It pays to pay attention to those who command premium prices.  In the weekly news magazine market, The Economist is by far the leader in actually getting their customers to pay.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Charlie Rose had Economist editor John Micklethwait on recently and he talked about their strategy for the Kindle. (Note: this is my transcription - not official)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;/div&gt;&lt;blockquote&gt;&lt;div&gt;Micklethwait: The interesting one to me is the Kindle.  If you want an example of the difference between us and other magazines.  If you look at the Kindle, we charge $10 per month.  Virtually every other magazine charges $2 or $3 per month.  And the reason why we charge that is because we have worked out that that is what we need to make money from it.  Remember that you can't carry advertising at all on the Kindle, and what worries me a bit from the perspective of the other magazines is that they are all looking at the Kindle as a little bit of incremental business.  We're looking at it as something which we think long term, it or its descendants or a derivative of it would replace a chunk of the print magazine.  &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Charlie: It has to stand alone.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Micklethwait: Yeah and you have to look at it as something that could eventually cannibalize your product.  But ultimately I think that's exciting.  I'm mean look we have distribute The Economist all the way around this country and all the way around the world.  The idea that people with electronic e-readers could actually be getting this almost immediately on a Thursday evening or Friday morning - that's a very exciting idea.&lt;/div&gt;&lt;/blockquote&gt;&lt;div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div&gt;Time and Newsweek are &lt;a href="http://gawker.com/news/time-inc./time-inc-layoffs-surveying-the-wreckage-229978.php"&gt;struggling&lt;/a&gt; and &lt;a href="http://www.tnr.com/article/politics/backward-runs-newsweek"&gt;changing their strategies&lt;/a&gt;.  The Economist seems to be thriving.  I think that The Economist's forward-thinking and confident perspective on the future of publishing is a big reason for this strength.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Video &lt;a href="http://www.charlierose.com/"&gt;here&lt;/a&gt;.  The discussion about e-readers starts at about 16:50.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-1106491220552893277?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/zxsqWsXqTIo" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/1106491220552893277/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/10/economist-magazine-embraces-kindle-as.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/1106491220552893277?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/1106491220552893277?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/zxsqWsXqTIo/economist-magazine-embraces-kindle-as.html" title="The Economist Magazine Embraces the Kindle as a Revenue Generator" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/10/economist-magazine-embraces-kindle-as.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUEGSHYzfCp7ImA9WxNVEkw.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-6486375291146681364</id><published>2009-10-10T11:59:00.004-04:00</published><updated>2009-10-22T09:20:29.884-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-22T09:20:29.884-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="stamp.la" /><category scheme="http://www.blogger.com/atom/ns#" term="functionality" /><category scheme="http://www.blogger.com/atom/ns#" term="features" /><title>stamp.la is a World Traveler</title><content type="html">&lt;div&gt;We quietly launched support for four languages this week:&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;a href="http://stamp.la/?lang=es"&gt;stamp.la habla español&lt;/a&gt;&lt;/div&gt;&lt;div&gt;&lt;a href="http://stamp.la/?lang=fr"&gt;stamp.la parle français&lt;/a&gt;&lt;/div&gt;&lt;div&gt;&lt;a href="http://stamp.la/?lang=de"&gt;stamp.la spricht Deutsch&lt;/a&gt;&lt;/div&gt;&lt;div&gt;&lt;a href="http://stamp.la/?lang=it"&gt;stamp.la parla italiano&lt;/a&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;We're working on more languages, and getting language support for the entire DocMonk website as well.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-6486375291146681364?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/ZDK_5sygE1U" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/6486375291146681364/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/10/stampla-is-world-traveler.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/6486375291146681364?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/6486375291146681364?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/ZDK_5sygE1U/stampla-is-world-traveler.html" title="stamp.la is a World Traveler" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/10/stampla-is-world-traveler.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUEDQ3k6eip7ImA9WxNVEkw.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-3780420658463370874</id><published>2009-10-07T17:33:00.023-04:00</published><updated>2009-10-22T09:21:12.712-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-22T09:21:12.712-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="law" /><category scheme="http://www.blogger.com/atom/ns#" term="copyright" /><category scheme="http://www.blogger.com/atom/ns#" term="piracy" /><category scheme="http://www.blogger.com/atom/ns#" term="infringement" /><category scheme="http://www.blogger.com/atom/ns#" term="copyright arms-race" /><title>Do Heavy-Handed Copyright Laws Work?</title><content type="html">It's our philosophy here at &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;DocMonk&lt;/span&gt; that publishers who &lt;a href="http://blog.docmonk.com/2009/07/respect.html"&gt;respect&lt;/a&gt; their readers will have their copyrights respected in return.   The inverse is that publishers who employ heavy-handed &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;DRM&lt;/span&gt; technologies in an effort to stop theft of their intellectual property risk instigating a copyright arms-race.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;A copyright arms-race happens when publishers continuously try harder and harder to lock down their publications, and readers feel more and more justified in trying to break the locks.  The readers always win these contests in the end.  We at &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;DocMonk&lt;/span&gt; document this phenomenon in our &lt;a href="http://twitter.com/docmonk/favorites"&gt;favorite tweets&lt;/a&gt;.&lt;div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Lately, I've been thinking about our philosophy as it relates to copyright law.  Nothing is more heavy-handed than our police and courts, so it seems that the same principles that we apply to &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;DRM&lt;/span&gt; technologies might be applied to the law as well.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;Is it possible that onerous copyright laws are actually encouraging copyright infringement?&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;The length of terms and severity of sanctions of copyright law have steadily increased over the years.  The first US copyright law was passed in 1790 and  granted a 14 year term for copyright, plus the opportunity to renew the copyright for another 14 years for one time only.  Today, copyright holders have a term that extends to 70 years past the death of the creator, or up to 120 years for corporations.  The Digital Millennium Copyright Act of 2000 included, for the first time, criminal penalties for certain forms of copyright infringement.  Previous laws had only focused on civil penalties.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;It's important to remember that the purpose of copyright, as stated by the US Constitution, is to "promote the Progress of Science and the useful Arts."  The question is, are ever-longer copyright terms and increased penalties promoting or hindering this objective?  Equally important, do these laws actually succeed in decreasing the losses suffered by copyright holders?&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;Copyright in the Real World&lt;/b&gt;&lt;/div&gt;&lt;div&gt;Google Books is a project that aspires to scan and index all of the books ever published.  According to the New York Times, they have already &lt;a href="http://www.nytimes.com/2009/10/04/books/review/Hyde-t.html"&gt;scanned&lt;/a&gt; about 7 million books.  However, an astounding 4 to 5 million of those books are "orphaned"  This means that that the copyright is still in force, but the copyright holders (or more likely their heirs) cannot be located or are not willing to take steps to make the work available.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;It's shocking that  a majority of the books in the Google database are in this situation. You can't buy a copy, but you can't legally make a copy on your own either.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Now you may be able to see where I'm going with this. Cue movie trailer guy:&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;blockquote&gt;&lt;i&gt;In a world where millions of books aren't available for sale, and can't be legally copied, how quickly will consumers learn to infringe routinely, even for first-run, brand new material?&lt;/i&gt;&lt;/blockquote&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;In most cases, copying an orphaned work really is a victimless crime because the rights-holder just isn't interested.  There may be rare cases where works of significant interest are orphaned because the heirs are unaware they they own the rights.  Somewhere, there might be some snotty kid who isn't aware that great-granddad was Ernest Hemingway - but I don't think that happens very often.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;Introducing the Slippery Slope &lt;/b&gt;&lt;/div&gt;&lt;div&gt;Once consumers get used to copying orphaned works, where does the infringement end?  It's not a great leap to go from, "I'll just do it one time because there really is no other option" to "Why should I pay for the new Harry Potter book?  I'll just &lt;a href="http://thepiratebay.org/search/harry%20potter/0/99/600"&gt;download it&lt;/a&gt;.  I learned how to do it that time when I needed that obscure book that was written in 1942."&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;The Case for Shorter Copyright Terms&lt;/b&gt;&lt;/div&gt;&lt;div&gt;Copyright law should only cover works that are worth protecting.  Fourteen years (the original law) sounds about right.  That way, content creators will be able to make a coherent case that copyright infringement really is theft, and not just a victimless crime.  Meanwhile, millions of works that are currently orphaned would enter the public domain, to "promote the Progress of Science and the useful Arts."&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-3780420658463370874?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/szHY5TiuvaY" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/3780420658463370874/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/10/do-heavy-handed-copyright-laws-work.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/3780420658463370874?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/3780420658463370874?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/szHY5TiuvaY/do-heavy-handed-copyright-laws-work.html" title="Do Heavy-Handed Copyright Laws Work?" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/10/do-heavy-handed-copyright-laws-work.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0YBQHczfip7ImA9WxNXE08.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-4504032365156469118</id><published>2009-09-29T18:53:00.009-04:00</published><updated>2009-09-30T11:39:11.986-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-30T11:39:11.986-04:00</app:edited><title>What Gets Measured Gets Managed</title><content type="html">A phone conversation with a new DocMonk client today reminded me of a quote by the business guru &lt;a href="http://philosophersnotes.com/quotes/by_teacher/Peter%20Drucker"&gt;Peter Drucker&lt;/a&gt;:&lt;div&gt;&lt;blockquote&gt;What gets measured gets managed.&lt;/blockquote&gt;&lt;/div&gt;&lt;div&gt;The client I was speaking with had just sent his weekly newsletter through DocMonk for the third time.  We were discussing the download rates for the issues he's sent.  Currently, only about 40% of the newsletters to paid subscribers are being downloaded. Downloading the issue is the only way to read it (DocMonk is the only form of fulfillment offered), so it's puzzling that so many people who had paid a lot of money to receive a newsletter aren't even reading it.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Then, we started thinking of ideas to increase the download-rate.  Maybe he should send a mid-week reminder (this newsletter arrives on Monday morning).  Maybe he needs to include a more-detailed summary of that week's content in the email body.  Certainly, there are many other things to be tried!&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;This is what made me think Drucker's quote.  Before he started using DocMonk, this client had not been measuring the percentage of his subscribers that were actually reading the newsletter.  The reason for this is simple enough: it wasn't possible.  Previously, he would email the PDF out to the subscribers as an attachment, and assume that they were reading it.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;DocMonk provides detailed reports of exactly who is and who is not opening the documents that are sent.  This gives publishers the opportunity to test strategies for improving the "read-rate" of their newsletters.   I have no doubt that this client will be driving his download rate higher in the coming weeks.  Ultimately, he will see all the benefits of higher readership including increased word of mouth, more responses to the content; and most importantly,  more renewals.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-4504032365156469118?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/r70u9UcTPRs" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/4504032365156469118/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/09/what-gets-measured-gets-managed.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/4504032365156469118?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/4504032365156469118?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/r70u9UcTPRs/what-gets-measured-gets-managed.html" title="What Gets Measured Gets Managed" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/09/what-gets-measured-gets-managed.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CU8MR345eCp7ImA9WxNXE0k.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-4205217547566848325</id><published>2009-09-21T19:56:00.021-04:00</published><updated>2009-09-30T16:51:26.020-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-30T16:51:26.020-04:00</app:edited><title>How DocMonk Prevents Search Engines from Caching Your Premium Content</title><content type="html">&lt;div&gt;One way that DocMonk increases ease of use for document recipients is by eliminating the need for users to log in to the site. Users need only click on the link they receive from the publisher and they immediately get to download their personalized PDF document. The main way that DocMonk protects publishers' content is by keeping the URL a secret between the publisher and subscriber.&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_QXlH3SVhl-E/Srgh2JUJttI/AAAAAAAAABc/v1CuOjgCnVM/s1600-h/draft_lens1878564module9096918photo_1208106771No_Right_Turn_sign.png"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 100px; height: 100px;" src="http://4.bp.blogspot.com/_QXlH3SVhl-E/Srgh2JUJttI/AAAAAAAAABc/v1CuOjgCnVM/s200/draft_lens1878564module9096918photo_1208106771No_Right_Turn_sign.png" border="0" alt="" id="BLOGGER_PHOTO_ID_5384090568618522322" /&gt;&lt;/a&gt;Of course, just having a secret URL isn't very good security. One risk is search engines, which may find the page and then index the content or allow others to find it. DocMonk prevents search engines from getting to publishers' valuable content by using a robots.txt file, which directs search engine crawlers to go away.  However, a robots.txt direction is kind of like a "No Right Turn" sign; less civically minded members of the community might choose to ignore it.  To put some teeth into our "no search engine" policy, we use &lt;a href="http://en.wikipedia.org/wiki/Captcha"&gt;CAPTCHAs&lt;/a&gt; to make sure every visitor is a living, breathing human being.&lt;/div&gt;&lt;br /&gt;&lt;div&gt;We've all seen CAPTCHAs.  They are those distorted series of characters that you must type when a website is trying to prevent spam.  DocMonk uses &lt;a href="http://recaptcha.net/"&gt;reCAPTCHA&lt;/a&gt; to verify that the entity trying to download a protected document is a human being.  By ensuring that only humans get through to the document, DocMonk prevents search engines from indexing and caching the documents.  Once DocMonk determines that a particular user is really human, subsequent attempts to download documents usually do not require completing a new CAPTCHA challenge.&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_QXlH3SVhl-E/Srgcw5PBxuI/AAAAAAAAABE/i9LwABj6wuA/s1600-h/captcha.png"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 200px; height: 126px;" src="http://3.bp.blogspot.com/_QXlH3SVhl-E/Srgcw5PBxuI/AAAAAAAAABE/i9LwABj6wuA/s200/captcha.png" border="0" alt="" id="BLOGGER_PHOTO_ID_5384084980844578530" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;div&gt;CAPTCHAs are one way that DocMonk strikes a balance between security and usability.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-4205217547566848325?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/owdXK-aGFIQ" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/4205217547566848325/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/09/how-docmonk-keeps-search-engines-from.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/4205217547566848325?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/4205217547566848325?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/owdXK-aGFIQ/how-docmonk-keeps-search-engines-from.html" title="How DocMonk Prevents Search Engines from Caching Your Premium Content" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/_QXlH3SVhl-E/Srgh2JUJttI/AAAAAAAAABc/v1CuOjgCnVM/s72-c/draft_lens1878564module9096918photo_1208106771No_Right_Turn_sign.png" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/09/how-docmonk-keeps-search-engines-from.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0YFQ30-eCp7ImA9WxNQEk4.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-3587541114919436810</id><published>2009-09-17T19:12:00.008-04:00</published><updated>2009-09-17T19:45:12.350-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-17T19:45:12.350-04:00</app:edited><title>29 Ideas for PDF Documents to Personalize</title><content type="html">Below are 29 ideas for PDF documents that you may want to personalize before sharing with others.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Personalizing a document is an example of Social DRM.  It is perfect for situations where you don't want the information in the document to spread beyond its intended recipients, but you also don't want to insult or inconvenience people either.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;You probably trust your friends, family, coworkers and customers; but not 100% and not all the time.  For relationships like these, personalizing a PDF document is a great strategy for protecting your work because it is proportional to the threat.  You don't need an expensive, heavy-handed and inconvenient DRM solution.  You just need the ability to let your recipients know that you care about sharing, and a way to trace back any shared copies that end up in the wrong hands or on the internet.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Certainly you wouldn't need to personalize all of these types of documents all the time.  But in many cases, doing so could give you piece of mind:&lt;/div&gt;&lt;div&gt;&lt;ol&gt;&lt;li&gt;Reports&lt;/li&gt;&lt;li&gt;Manuscripts&lt;/li&gt;&lt;li&gt;Newsletters&lt;/li&gt;&lt;li&gt;Business Plans&lt;/li&gt;&lt;li&gt;Legal Documents&lt;/li&gt;&lt;li&gt;Health Records&lt;/li&gt;&lt;li&gt;Resumes&lt;/li&gt;&lt;li&gt;RFPs&lt;/li&gt;&lt;li&gt;Compensation Plans&lt;/li&gt;&lt;li&gt;Memos&lt;/li&gt;&lt;li&gt;Ebooks&lt;/li&gt;&lt;li&gt;Computer Code&lt;/li&gt;&lt;li&gt;Financial Statements&lt;/li&gt;&lt;li&gt;Schematics&lt;/li&gt;&lt;li&gt;Tax Records&lt;/li&gt;&lt;li&gt;Invitations (for an exclusive party)&lt;/li&gt;&lt;li&gt;Manuals&lt;/li&gt;&lt;li&gt;Ballots/Voting&lt;/li&gt;&lt;li&gt;Company Policies/Handbooks&lt;/li&gt;&lt;li&gt;ScreenPlays&lt;/li&gt;&lt;li&gt;Schedules&lt;/li&gt;&lt;li&gt;Insurance Forms&lt;/li&gt;&lt;li&gt;Itineraries&lt;/li&gt;&lt;li&gt;Meeting Minutes&lt;/li&gt;&lt;li&gt;Treasure Maps&lt;/li&gt;&lt;li&gt;Academic Papers&lt;/li&gt;&lt;li&gt;Software Design&lt;/li&gt;&lt;li&gt;Performance Reviews&lt;/li&gt;&lt;li&gt;Price Lists&lt;/li&gt;&lt;/ol&gt;Obviously this list is a small sample of the possibilities.  Remember to use &lt;a href="http://stamp.la/"&gt;stamp.la&lt;/a&gt; for simple, one time jobs and &lt;a href="http://www.docmonk.com/"&gt;DocMonk &lt;/a&gt;for robust PDF personalization and delivery. &lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-3587541114919436810?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/F_jZsuy4XE4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/3587541114919436810/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/09/29-ideas-for-pdf-documents-to.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/3587541114919436810?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/3587541114919436810?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/F_jZsuy4XE4/29-ideas-for-pdf-documents-to.html" title="29 Ideas for PDF Documents to Personalize" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/09/29-ideas-for-pdf-documents-to.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A08AQXw9eSp7ImA9WxNRFEQ.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-3021153424627278999</id><published>2009-09-09T08:31:00.002-04:00</published><updated>2009-09-09T08:37:20.261-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-09T08:37:20.261-04:00</app:edited><title>Introducing stamp.la</title><content type="html">I'm pleased to announce that &lt;a href="http://stamp.la"&gt;stamp.la&lt;/a&gt; is officially launched.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;stamp.la is really just a simple hack that takes advantage of the &lt;a href="http://www.docmonk.com/api/"&gt;DocMonk API&lt;/a&gt; and makes it faster and easier than ever to stamp a person's name to a PDF document.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Hopefully you'll find it useful.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-3021153424627278999?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/-eRPnJF1CwI" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/3021153424627278999/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/09/introducing-stampla.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/3021153424627278999?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/3021153424627278999?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/-eRPnJF1CwI/introducing-stampla.html" title="Introducing stamp.la" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/09/introducing-stampla.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0MNQ3g4fSp7ImA9WxNSGE0.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-4901116503409616549</id><published>2009-08-31T19:36:00.009-04:00</published><updated>2009-09-01T08:51:32.635-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-01T08:51:32.635-04:00</app:edited><title>Font Snobs</title><content type="html">Some connoisseurs of all things font are "outraged" over &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;Ikea's&lt;/span&gt; &lt;a href="http://www.time.com/time/business/article/0,8599,1919127,00.html"&gt;decision&lt;/a&gt; to use &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;Verdana&lt;/span&gt; as their new &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_2"&gt;official&lt;/span&gt; font.  &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;Verdana&lt;/span&gt; of course was invented by Microsoft and is freely available.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;It's interesting that some &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_4"&gt;critics&lt;/span&gt; call &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;Ikea&lt;/span&gt; "cheap" for &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_6"&gt;choosing&lt;/span&gt; a free font. Undoubtedly others are just hating on all things Microsoft.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;A question: Would anybody accuse Idea of being "cheap" if they used open source software?  What exactly is the difference?&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Also, isn't &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_7"&gt;Ikea's&lt;/span&gt; cheapness part of its corporate image?  &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Anyway, this reminded me of this &lt;a href="http://online.wsj.com/article/SB123992364819927171.html"&gt;article&lt;/a&gt; from the Wall Street Journal about another infamous font: Comic Sans.  &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;I think as an information &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_8"&gt;publisher&lt;/span&gt;, your goal should be to avoid these debates entirely.  In response to the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_9"&gt;Ikea&lt;/span&gt; flap, Fast Company has published a &lt;a href="http://www.fastcompany.com/blog/cliff-kuang/design-innovation/six-fonts-piss-people"&gt;list&lt;/a&gt; of six fonts that people love to hate.  Perhaps you should have a "banned font" list in your &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_10"&gt;organization&lt;/span&gt;?&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;You never know who may be looking down their nose, stroking their chin, tut-tutting you for your choice of font. &lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-4901116503409616549?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/HQR_jwKrFxk" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/4901116503409616549/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/08/font-snobs.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/4901116503409616549?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/4901116503409616549?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/HQR_jwKrFxk/font-snobs.html" title="Font Snobs" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/08/font-snobs.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0AGRH44eSp7ImA9WxNSF0s.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-3944399508349097978</id><published>2009-08-31T19:30:00.004-04:00</published><updated>2009-08-31T19:35:25.031-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-31T19:35:25.031-04:00</app:edited><title>If you were a publisher of sheet music. . .</title><content type="html">Do you think &lt;a href="http://www.freehandsystems.com/products.html?utm_source=toplink&amp;amp;utm_medium=link&amp;amp;utm_content=text&amp;amp;utm_campaign=MusicPad"&gt;this&lt;/a&gt; would have any effect on your business?&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;By the way, our API was just &lt;a href="http://www.docmonk.com/api/"&gt;released&lt;/a&gt; today and the &lt;a href="http://www.docmonk.com/api/apiExample.php"&gt;example application&lt;/a&gt; uses a PDF of sheet music.  Why did I use sheet music?  I needed some content in the public domain and it seemed like a classical composer would fit the bill.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-3944399508349097978?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/2evKXMfkdtM" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/3944399508349097978/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/08/if-you-were-publisher-of-sheet-music.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/3944399508349097978?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/3944399508349097978?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/2evKXMfkdtM/if-you-were-publisher-of-sheet-music.html" title="If you were a publisher of sheet music. . ." /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/08/if-you-were-publisher-of-sheet-music.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU4DQX05eCp7ImA9WxNSEk8.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-5134008246110460902</id><published>2009-08-25T15:08:00.004-04:00</published><updated>2009-08-25T15:19:30.320-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-25T15:19:30.320-04:00</app:edited><title>Sony Steps up with Wireless E-Reader to Rival the Kindle</title><content type="html">&lt;div&gt;I think it's a sure thing that e-books are going to change the high-value newsletters and reports industry in a big way.  It's important to pay attention to these developments.  With that in mind. . . &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;From &lt;a href="http://www.blogger.com/://news.cnet.com/8301-17938_105-10317087-1.html"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;cnet&lt;/span&gt;&lt;/a&gt;:&lt;br /&gt;&lt;blockquote&gt;Sony on Tuesday announced its first e-book reader with built-in wireless capability. The new Reader Daily Edition offers an integrated 3G wireless connection, allowing it to access Sony's online bookstore as well as yet-to-be-announced newspaper and magazine subscriptions. The unit--which boasts a 7-inch touch screen (displayable in portrait or landscape mode)--will sell for $399 when it debuts in December. Wireless service is provided by AT&amp;amp;T with no direct charge to the customer.&lt;br /&gt;&lt;/blockquote&gt;&lt;br /&gt;It looks like Sony has learned a lot from the Kindle, which was a big hit mostly because the built-in wireless capability made it much more user-friendly.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-5134008246110460902?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/6lLdbridI5s" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/5134008246110460902/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/08/sony-steps-up-with-wireless-e-reader-to.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/5134008246110460902?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/5134008246110460902?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/6lLdbridI5s/sony-steps-up-with-wireless-e-reader-to.html" title="Sony Steps up with Wireless E-Reader to Rival the Kindle" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/08/sony-steps-up-with-wireless-e-reader-to.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0YFR3czfCp7ImA9WxNTGE4.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-6116354336611846053</id><published>2009-08-20T19:27:00.006-04:00</published><updated>2009-08-21T01:05:16.984-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-21T01:05:16.984-04:00</app:edited><title>Internal AP Document Describing their Online Content Strategy Leaked</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.mediabistro.com/fishbowlny/original/APLogo.jpg"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 114px; height: 80px;" src="http://www.mediabistro.com/fishbowlny/original/APLogo.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;As I &lt;a href="http://blog.docmonk.com/2009/07/associated-press-experiements-with.html"&gt;wrote &lt;/a&gt;a few weeks ago, the Associated Press is planning to launch a new online licensing scheme designed to make sure they get paid when their content gets posted online on blogs and other sites.&lt;br /&gt;&lt;br /&gt;The &lt;a href="http://www.scribd.com/doc/18555024/Protect-Point-Pay-An-Associated-Press-Plan-for-Reclaiming-News-Content-Online"&gt;document&lt;/a&gt; describes AP's effort to store and track all of their content internally, track its use online through their own licensing technology, and look for unauthorized uses using web robot crawlers.  It also has some analysis of the roles sites like Wikipedia, Google News and Twitter are playing in the current news environment.&lt;br /&gt;&lt;br /&gt;If you're a puppy-dog content-provider wondering what the big dogs are thinking vis-a-vis intellectual property, it might be worth a read.&lt;br /&gt;&lt;br /&gt;Of course, if the AP used &lt;a href="http://www.docmonk.com/"&gt;DocMonk&lt;/a&gt; to distribute their confidential memos, they'd probably have better luck keeping their secrets secret.  Just sayin.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-6116354336611846053?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/v4vEJbfiFwE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/6116354336611846053/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/08/internal-ap-document-describing-their.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/6116354336611846053?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/6116354336611846053?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/v4vEJbfiFwE/internal-ap-document-describing-their.html" title="Internal AP Document Describing their Online Content Strategy Leaked" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/08/internal-ap-document-describing-their.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUYNSXw7fCp7ImA9WxNTFU4.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-6495334371003960583</id><published>2009-08-17T14:12:00.004-04:00</published><updated>2009-08-17T14:19:58.204-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-17T14:19:58.204-04:00</app:edited><title>SitePoint, Publisher of Information Products for Web Professionals, Eliminates Passwords on their PDF Books</title><content type="html">An eloquent and forward-thinking rationale for unprotected PDFs &lt;a href="http://www.sitepoint.com/blogs/2009/08/11/no-more-passwords-on-sitepoint-pdfs/"&gt;here&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-6495334371003960583?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/v0JLAjm5b-k" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/6495334371003960583/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/08/sitepoint-publisher-of-information.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/6495334371003960583?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/6495334371003960583?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/v0JLAjm5b-k/sitepoint-publisher-of-information.html" title="SitePoint, Publisher of Information Products for Web Professionals, Eliminates Passwords on their PDF Books" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/08/sitepoint-publisher-of-information.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkYNQX4zfyp7ImA9WxJaEU4.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-7397459489977745888</id><published>2009-08-01T10:18:00.006-04:00</published><updated>2009-08-01T10:49:50.087-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-01T10:49:50.087-04:00</app:edited><title>"View in HTML" Feature in Gmail Stripping out PDF DRM</title><content type="html">Yet &lt;a href="http://www.techcrunch.com/2009/07/31/am-i-last-to-find-out-you-can-circumvent-pdf-usage-restrictions-with-gmail/"&gt;another way&lt;/a&gt; that DRM for PDF can be defeated.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Also, check the comments of the link above.  Everybody is sharing their favorite way to defeat protected PDFs.  That's the "copyright arms race."&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-7397459489977745888?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/3R3_L979n4A" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/7397459489977745888/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/08/view-in-html-feature-in-gmail-stripping.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/7397459489977745888?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/7397459489977745888?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/3R3_L979n4A/view-in-html-feature-in-gmail-stripping.html" title="&quot;View in HTML&quot; Feature in Gmail Stripping out PDF DRM" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/08/view-in-html-feature-in-gmail-stripping.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CU8EQH84fSp7ImA9WxJbF0w.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-1566204926186792515</id><published>2009-07-27T09:21:00.005-04:00</published><updated>2009-07-27T12:56:41.135-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-27T12:56:41.135-04:00</app:edited><title>Associated Press Experiments with Increased Content Control</title><content type="html">&lt;blockquote&gt;&lt;/blockquote&gt;The Associated Press is trying to &lt;a href="http://www.nytimes.com/2009/07/24/business/media/24content.html"&gt;combat&lt;/a&gt; online piracy by adding a bunch of tracking to their documents.  I don't really understand exactly what they will be doing, but it looks like they intend to include some kind beacon or other tracking technology that will supposedly tell them when and where their content is being used, so they can go after illegal uses.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;It's too early to tell, but here are a couple of predictions:&lt;/div&gt;&lt;div&gt;&lt;ul&gt;&lt;li&gt;The system will be buggy, annoying and will outright fail in many instances.&lt;/li&gt;&lt;li&gt;The backlash will come in the form of users &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_0"&gt;actively&lt;/span&gt; working to defeat the controls.&lt;/li&gt;&lt;li&gt;The backlash will also come  in the form of users &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_1"&gt;choosing&lt;/span&gt; to use other news sources.&lt;/li&gt;&lt;/ul&gt;&lt;div&gt;I don't see how the AP can &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_2"&gt;achieve&lt;/span&gt; anything with this strategy, but who knows?&lt;/div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-1566204926186792515?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/SN7p4tnExU4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/1566204926186792515/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/07/associated-press-experiements-with.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/1566204926186792515?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/1566204926186792515?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/SN7p4tnExU4/associated-press-experiements-with.html" title="Associated Press Experiments with Increased Content Control" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/07/associated-press-experiements-with.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEMHRXo_fSp7ImA9WxJbFUs.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-1199305337911014911</id><published>2009-07-25T18:32:00.006-04:00</published><updated>2009-07-25T18:53:54.445-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-25T18:53:54.445-04:00</app:edited><title>PDFs Now Face More Security Threats than Microsoft Windows</title><content type="html">By one measure, &lt;a href="http://www.examiner.com/x-14651-Minneapolis-Information-Technology-Examiner~y2009m7d25-Adobe-surpasses-Microsoft-as-number-one-target"&gt;48% of all computer attacks (viruses, worms and the like) are now targeted at PDF documents&lt;/a&gt;.  I don't think many consumers are aware yet of the threats associated with PDF files. &lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;However, I'm willing to bet that in the future, we will see more and more people and IT departments being wary of PDF files.  In particular, files that contain scripts or other security features may be banned completely at some companies and be shunned consumers in general.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;If you're relying on a PDF security solution that involves tracking opens, forwards, prints, etc., this could be a serious problem.  To a virus scanner or IT department email filter, it may be impossible to tell legitimate tracking technology from the malicious scripts that might be embedded in a document.  You may find that your documents get caught by filters or go unread as a result.&lt;/div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-1199305337911014911?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/3iGpRvtr1c0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/1199305337911014911/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/07/pdfs-now-face-more-security-threats.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/1199305337911014911?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/1199305337911014911?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/3iGpRvtr1c0/pdfs-now-face-more-security-threats.html" title="PDFs Now Face More Security Threats than Microsoft Windows" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/07/pdfs-now-face-more-security-threats.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0YFSXwzeSp7ImA9WxJbFEk.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-6001306879574860224</id><published>2009-07-24T10:13:00.003-04:00</published><updated>2009-07-24T10:18:38.281-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-24T10:18:38.281-04:00</app:edited><title>Are Legal Briefs Protected by Copyright?</title><content type="html">As I understand it, &lt;a href="http://volokh.com/posts/1248389303.shtml"&gt;legal briefs&lt;/a&gt; filed in court are in the public record but not in the public domain.  Where does that leave companies like Lexis and Westlaw who sell access to these works?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-6001306879574860224?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/Wp7MSrSiVdY" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/6001306879574860224/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/07/are-legal-briefs-protected-by-copyright.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/6001306879574860224?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/6001306879574860224?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/Wp7MSrSiVdY/are-legal-briefs-protected-by-copyright.html" title="Are Legal Briefs Protected by Copyright?" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/07/are-legal-briefs-protected-by-copyright.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUIHRHYzfip7ImA9WxJbEk4.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-7435798941799472254</id><published>2009-07-20T19:35:00.008-04:00</published><updated>2009-07-22T00:38:55.886-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-22T00:38:55.886-04:00</app:edited><title>Respect</title><content type="html">One thing that I &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_0"&gt;fervently&lt;/span&gt; believe high-value information publishers need to understand is that it's probably not a good idea to engage your customers in a copyright arms race.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;What do I mean by "copyright arms-race?"  I'm talking about publishers who have a strategy of doing anything and everything they can to make it hard to share their work. I believe that if a publisher adopts this approach, he should not be surprised when his customers (who really are good, honest people most of the time) start devoting significant time and energy to defeat any and all controls and restrictions on sharing copyrighted works.&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;The music recording industry is probably the best example of this.  They tried everything they could think of to ratchet up control over users' copying, including annoying "Digital Rights Management" schemes for online purchases and lawsuits against file sharers.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;That strategy resulted in music fans adopting an "anything goes" attitude that basically declared that anything that could be done to defeat the copy protections was fair game.  Rather than appealing to the decent character of their customers, record companies aroused the warrior instinct inside music fans.  The music fans then proceeded to win the war of piracy and cause significant pain for the recording industry.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;I &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_3"&gt;absolutely&lt;/span&gt; believe that publishers have the right to control the copying of their work, and they have the right to impose &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_4"&gt;technological&lt;/span&gt; tools to thwart copying.  However, I also believe these rights should be exercised wisely.  Just because it's a right, doen't mean that you have to exercise it. In many cases it is wiser and more productive to have a light touch.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Respect your customers and they might just respect your copyright in return.&lt;/div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-7435798941799472254?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/WY17QU4-U_8" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/7435798941799472254/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/07/respect.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/7435798941799472254?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/7435798941799472254?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/WY17QU4-U_8/respect.html" title="Respect" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/07/respect.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0AHSH8-fip7ImA9WxJbEUw.&quot;"><id>tag:blogger.com,1999:blog-2355358038307267738.post-4045385683304133182</id><published>2009-07-20T14:30:00.000-04:00</published><updated>2009-07-20T14:48:59.156-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-20T14:48:59.156-04:00</app:edited><title>Welcome to DocMonk</title><content type="html">This is the &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_0"&gt;inaugural&lt;/span&gt; post of the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;DocMonk&lt;/span&gt; blog.  To kick things off, I'd like to take a moment to just introduce myself and very briefly explain what &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;DocMonk&lt;/span&gt; is about.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;My name is Jay &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;Muntz&lt;/span&gt;.  I have over 12 years of software development experience.  Over that time I've &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_4"&gt;built&lt;/span&gt; many different web-based applications including marketing, email and content management.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;For the past several months I've been working on building &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;DocMonk&lt;/span&gt;.  &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_6"&gt;DocMonk&lt;/span&gt; is a web site that allows print publishers to send their readers &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_7"&gt;personalized&lt;/span&gt; &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_8"&gt;PDF&lt;/span&gt; &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_9"&gt;document&lt;/span&gt; and to track when those documents are downloaded.  This idea is driven by a specific philosophy I have which says that you must demonstrate respect and trust towards your users, if you want them to respect your copyright.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;There's a lot more to say but I'll leave it at that for now.  &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_10"&gt;DocMonk&lt;/span&gt; will transition from private beta to pubic beta within a few days.  Contact me anytime if you'd like to know more.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2355358038307267738-4045385683304133182?l=blog.docmonk.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Docmonk/~4/SiIDvmgah5s" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.docmonk.com/feeds/4045385683304133182/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.docmonk.com/2009/07/welcome-to-docmonk.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/4045385683304133182?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2355358038307267738/posts/default/4045385683304133182?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Docmonk/~3/SiIDvmgah5s/welcome-to-docmonk.html" title="Welcome to DocMonk" /><author><name>Jay Muntz - DocMonk</name><uri>http://www.blogger.com/profile/15725574635976939718</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.docmonk.com/2009/07/welcome-to-docmonk.html</feedburner:origLink></entry></feed>

