<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Scribd&#8217;s iPaper and the fragile web</title>
	<link>http://dubroy.com/blog/2008/02/22/scribds-ipaper-and-the-fragile-web/</link>
	<description>on programming, usability, and design; by Patrick Dubroy</description>
	<pubDate>Wed, 20 Aug 2008 13:21:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Patrick</title>
		<link>http://dubroy.com/blog/2008/02/22/scribds-ipaper-and-the-fragile-web/#comment-9225</link>
		<pubDate>Fri, 22 Feb 2008 18:54:36 +0000</pubDate>
		<guid>http://dubroy.com/blog/2008/02/22/scribds-ipaper-and-the-fragile-web/#comment-9225</guid>
					<description>&lt;p&gt;e:&lt;/p&gt;

&lt;p&gt;I agree that it &lt;em&gt;should&lt;/em&gt; be HTML, most of the time. But in reality, there are often many decent reasons why it's not.&lt;/p&gt;

&lt;p&gt;I don't think there's much point in saying what the web was created for, because that was 17 years ago, and the web has long since been twisted for purposes other than those it was designed for. And in my experience, most academic papers are distributed in PDF, not HTML. The reality is that many people have documents that they want to share that are in PDF, .doc, .ppt, etc. They're not in HTML because they were not originally written for the web. For example, from my &lt;a href="http://dubroy.com/blog/about" rel="nofollow"&gt;about page&lt;/a&gt; I link to a few of my project reports. I don't want to bother converting them to HTML, but it would be nice for people to be able to easily view them.&lt;/p&gt;

&lt;p&gt;You're right that they are just reinventing PDF. That's the point though. But it also does more -- PDFs, Word docs, Powerpoint slides, etc. are all viewable through the same interface. From that perspective, I think it's a win.&lt;/p&gt;

&lt;p&gt;I do agree that what they have right now seems pretty half baked. I tried to follow their QuickSwitch instructions to turn one of my PDFs into iPaper, and the sample code that they gave me was missing a really important piece, which I only discovered by looking through the full reference. Once I finally got it working, the page was displaying a blank document. Only by clicking though to the Scribd version could I actually read the document, and even then, the font was so crappy that it was basically unreadable.&lt;/p&gt;

&lt;p&gt;So, for the concept, I give them a B+, for the implementation, a C.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>e:</p>
<p>I agree that it <em>should</em> be HTML, most of the time. But in reality, there are often many decent reasons why it&#8217;s not.</p>
<p>I don&#8217;t think there&#8217;s much point in saying what the web was created for, because that was 17 years ago, and the web has long since been twisted for purposes other than those it was designed for. And in my experience, most academic papers are distributed in PDF, not HTML. The reality is that many people have documents that they want to share that are in PDF, .doc, .ppt, etc. They&#8217;re not in HTML because they were not originally written for the web. For example, from my <a href="http://dubroy.com/blog/about" rel="nofollow">about page</a> I link to a few of my project reports. I don&#8217;t want to bother converting them to HTML, but it would be nice for people to be able to easily view them.</p>
<p>You&#8217;re right that they are just reinventing PDF. That&#8217;s the point though. But it also does more &#8212; PDFs, Word docs, Powerpoint slides, etc. are all viewable through the same interface. From that perspective, I think it&#8217;s a win.</p>
<p>I do agree that what they have right now seems pretty half baked. I tried to follow their QuickSwitch instructions to turn one of my PDFs into iPaper, and the sample code that they gave me was missing a really important piece, which I only discovered by looking through the full reference. Once I finally got it working, the page was displaying a blank document. Only by clicking though to the Scribd version could I actually read the document, and even then, the font was so crappy that it was basically unreadable.</p>
<p>So, for the concept, I give them a B+, for the implementation, a C.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: e</title>
		<link>http://dubroy.com/blog/2008/02/22/scribds-ipaper-and-the-fragile-web/#comment-9224</link>
		<pubDate>Fri, 22 Feb 2008 18:22:06 +0000</pubDate>
		<guid>http://dubroy.com/blog/2008/02/22/scribds-ipaper-and-the-fragile-web/#comment-9224</guid>
					<description>&lt;p&gt;What the is a "document"? The web was created for sharing academic papers. "Document" content should just be straight HTML 'cause that's what HTML is designed to do.&lt;/p&gt;

&lt;p&gt;If they're just trying to do an online rendition of the printed copy, then they're just reinventing PDF. Their tool doesn't appear to provide any extra features, such as annotation, a mechanism for sharing comments, or sharing a single "documents" across multiple sites. When I viewed their demo document that's supposed to contain advertising, it didn't. It sounds like they can't even get their own crippled featureset right.&lt;/p&gt;

&lt;p&gt;Craptastic!&lt;/p&gt;

&lt;p&gt;As to your concerns about centralization on the web, I worry less about utility computing providers (S3, paypal, etc), and more about the centralization of services: google search, gmail, google documents, google calendar, etc. It's only a matter of time until Google (or Microsoft, or Yahoo!, or Amazon) start violating user's privacy. The impact in China is chilling: Yahoo! has cooperated with a repressive regime and people are in jail (or dead) because of it. If utility computing services go down, then there's a denial of service for their customers, but when privacy is at stake, their can be much more serious consequences.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>What the is a &#8220;document&#8221;? The web was created for sharing academic papers. &#8220;Document&#8221; content should just be straight HTML &#8217;cause that&#8217;s what HTML is designed to do.</p>
<p>If they&#8217;re just trying to do an online rendition of the printed copy, then they&#8217;re just reinventing PDF. Their tool doesn&#8217;t appear to provide any extra features, such as annotation, a mechanism for sharing comments, or sharing a single &#8220;documents&#8221; across multiple sites. When I viewed their demo document that&#8217;s supposed to contain advertising, it didn&#8217;t. It sounds like they can&#8217;t even get their own crippled featureset right.</p>
<p>Craptastic!</p>
<p>As to your concerns about centralization on the web, I worry less about utility computing providers (S3, paypal, etc), and more about the centralization of services: google search, gmail, google documents, google calendar, etc. It&#8217;s only a matter of time until Google (or Microsoft, or Yahoo!, or Amazon) start violating user&#8217;s privacy. The impact in China is chilling: Yahoo! has cooperated with a repressive regime and people are in jail (or dead) because of it. If utility computing services go down, then there&#8217;s a denial of service for their customers, but when privacy is at stake, their can be much more serious consequences.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
