<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Betaworks&#8217; Findings shifts to web clipping, as Amazon bans Kindle clips</title>
	<atom:link href="http://gigaom.com/2012/09/18/betaworks-findings-pivots-as-amazon-bans-kindle-clips/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2012/09/18/betaworks-findings-pivots-as-amazon-bans-kindle-clips/</link>
	<description></description>
	<lastBuildDate>Sat, 18 May 2013 20:35:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: George Rajiv</title>
		<link>http://gigaom.com/2012/09/18/betaworks-findings-pivots-as-amazon-bans-kindle-clips/#comment-1163277</link>
		<dc:creator><![CDATA[George Rajiv]]></dc:creator>
		<pubDate>Fri, 09 Nov 2012 15:44:56 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=564034#comment-1163277</guid>
		<description><![CDATA[you can try k-highlights in iphone app store. it&#039;s pretty new but works well for me to get up to date on books that i&#039;ve read while ago. I highlight ALOT though, for personal reference =)]]></description>
		<content:encoded><![CDATA[<p>you can try k-highlights in iphone app store. it&#8217;s pretty new but works well for me to get up to date on books that i&#8217;ve read while ago. I highlight ALOT though, for personal reference =)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jdouglasj</title>
		<link>http://gigaom.com/2012/09/18/betaworks-findings-pivots-as-amazon-bans-kindle-clips/#comment-1144779</link>
		<dc:creator><![CDATA[jdouglasj]]></dc:creator>
		<pubDate>Sat, 03 Nov 2012 19:32:54 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=564034#comment-1144779</guid>
		<description><![CDATA[correct me if I&#039;m wrong, but My Clippings.txt only shows you the highlights and notes you made on your actual Kindle device, such as the Kindle Touch, which is what I use.  However, if I make a highlight and a note on my Kindle app on my iPad, it will never appear in the My Clippings.txt file, even after synching.    Let me know if I&#039;m wrong.]]></description>
		<content:encoded><![CDATA[<p>correct me if I&#8217;m wrong, but My Clippings.txt only shows you the highlights and notes you made on your actual Kindle device, such as the Kindle Touch, which is what I use.  However, if I make a highlight and a note on my Kindle app on my iPad, it will never appear in the My Clippings.txt file, even after synching.    Let me know if I&#8217;m wrong.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kuote.us</title>
		<link>http://gigaom.com/2012/09/18/betaworks-findings-pivots-as-amazon-bans-kindle-clips/#comment-1025108</link>
		<dc:creator><![CDATA[Kuote.us]]></dc:creator>
		<pubDate>Fri, 28 Sep 2012 21:12:15 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=564034#comment-1025108</guid>
		<description><![CDATA[I love my Kindle.... is great.. but the MyClippings function was complicated. I development a Web aplication:    http://www.kuote.us 
a easy way to manage and share your quotes, notes, clips and bookmarks.. just import the clipping file (myClippings.txt) and the aplication import and categorize all content for your use..]]></description>
		<content:encoded><![CDATA[<p>I love my Kindle&#8230;. is great.. but the MyClippings function was complicated. I development a Web aplication:    <a href="http://www.kuote.us" rel="nofollow">http://www.kuote.us</a><br />
a easy way to manage and share your quotes, notes, clips and bookmarks.. just import the clipping file (myClippings.txt) and the aplication import and categorize all content for your use..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mattmaldre</title>
		<link>http://gigaom.com/2012/09/18/betaworks-findings-pivots-as-amazon-bans-kindle-clips/#comment-1009221</link>
		<dc:creator><![CDATA[mattmaldre]]></dc:creator>
		<pubDate>Thu, 20 Sep 2012 21:05:58 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=564034#comment-1009221</guid>
		<description><![CDATA[I love what Joe Wikert has to say here. I completely agree. There&#039;s this old school stigma where those in power want to squeeze and hold onto things tightly. Like highlights on the Kindle. 

Just when I had hope that Amazon might start making note-sharing and highlight-sharing more social, they go backwards and lock it down further. That&#039;s not the direction Amazon should be going. 

Given Amazon&#039;s perspective on this, as a book reader, I am seriously going to start considering buying my books elsewhere. Ultimately, I want a platform where I can share my notes and highlights with others. 

Instead we have old-fashioned minded book readers in charge who think that the act of reading is a completely solitary one. While you might be in solitare while reading, what&#039;s most important is what happens when you process the book in your mind. When you share what you enjoy. It seems that Amazon is prohibiting the complete sharing of what you enjoy. 

This runs parallel with Twitter. Twitter is holding their API with a tighter and tighter fist. Originally Twitter was built on an open platform. It grew and grew due to people being able to share short tweets. You could have many different readers. You can analyze your tweets in all formats. You could count how many people follow you, at-reply with you, etc. It was an open system. Now Twitter is cracking down on the very developers that made them big in the first place. 

Twitter wants more control over where people can see their tweets, so they close off outside parties to the ability to display and analyze tweets. Just as Amazon is closing off their system for people to be able to read highlights. 

Readers want open systems. Those in power don&#039;t want open systems.]]></description>
		<content:encoded><![CDATA[<p>I love what Joe Wikert has to say here. I completely agree. There&#8217;s this old school stigma where those in power want to squeeze and hold onto things tightly. Like highlights on the Kindle. </p>
<p>Just when I had hope that Amazon might start making note-sharing and highlight-sharing more social, they go backwards and lock it down further. That&#8217;s not the direction Amazon should be going. </p>
<p>Given Amazon&#8217;s perspective on this, as a book reader, I am seriously going to start considering buying my books elsewhere. Ultimately, I want a platform where I can share my notes and highlights with others. </p>
<p>Instead we have old-fashioned minded book readers in charge who think that the act of reading is a completely solitary one. While you might be in solitare while reading, what&#8217;s most important is what happens when you process the book in your mind. When you share what you enjoy. It seems that Amazon is prohibiting the complete sharing of what you enjoy. </p>
<p>This runs parallel with Twitter. Twitter is holding their API with a tighter and tighter fist. Originally Twitter was built on an open platform. It grew and grew due to people being able to share short tweets. You could have many different readers. You can analyze your tweets in all formats. You could count how many people follow you, at-reply with you, etc. It was an open system. Now Twitter is cracking down on the very developers that made them big in the first place. </p>
<p>Twitter wants more control over where people can see their tweets, so they close off outside parties to the ability to display and analyze tweets. Just as Amazon is closing off their system for people to be able to read highlights. </p>
<p>Readers want open systems. Those in power don&#8217;t want open systems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Wikert</title>
		<link>http://gigaom.com/2012/09/18/betaworks-findings-pivots-as-amazon-bans-kindle-clips/#comment-1007039</link>
		<dc:creator><![CDATA[Joe Wikert]]></dc:creator>
		<pubDate>Wed, 19 Sep 2012 20:51:44 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=564034#comment-1007039</guid>
		<description><![CDATA[You raise a good point, Adrienne, but I say shame on those publishers whose contracts don&#039;t allow this sort of excerpt-sharing activity, especially when it&#039;s in the interest of increasing visibility/marketing. I get it that there are agreements like that in place but those publishers affected should quickly address this issue on a go-forward basis or risk losing out in the future where social media becomes even more important to book discovery.

I still doubt publishers are the reason behind Amazon&#039;s directive to Findings. I suspect the concept of fair use would apply to most of this anyway. So if I can write a review of the book and include a couple of short excerpts from it on my blog (thanks to fair use) why shouldn&#039;t I be able to share those same excerpts thru a service like Findings?]]></description>
		<content:encoded><![CDATA[<p>You raise a good point, Adrienne, but I say shame on those publishers whose contracts don&#8217;t allow this sort of excerpt-sharing activity, especially when it&#8217;s in the interest of increasing visibility/marketing. I get it that there are agreements like that in place but those publishers affected should quickly address this issue on a go-forward basis or risk losing out in the future where social media becomes even more important to book discovery.</p>
<p>I still doubt publishers are the reason behind Amazon&#8217;s directive to Findings. I suspect the concept of fair use would apply to most of this anyway. So if I can write a review of the book and include a couple of short excerpts from it on my blog (thanks to fair use) why shouldn&#8217;t I be able to share those same excerpts thru a service like Findings?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrienne Kinney</title>
		<link>http://gigaom.com/2012/09/18/betaworks-findings-pivots-as-amazon-bans-kindle-clips/#comment-1006487</link>
		<dc:creator><![CDATA[Adrienne Kinney]]></dc:creator>
		<pubDate>Wed, 19 Sep 2012 16:53:10 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=564034#comment-1006487</guid>
		<description><![CDATA[Generally publishers love viral sharing of content because it can drive sales. But it&#039;s possible some publishers may want Amazon to control clipping and sharing because extensive clipping (not to mention reaggregation of those clips out of context) can violate author, model and photographer contracts they hold with third parties. 

Yes publishers can control it to an extent, but  they do not have the time to control every aspect of the content detail. As someone who works for a publisher I know this to be very much part of the legal reality.

Adrienne Kinney, Director of Editorial Rights &amp; Licensing, Rodale]]></description>
		<content:encoded><![CDATA[<p>Generally publishers love viral sharing of content because it can drive sales. But it&#8217;s possible some publishers may want Amazon to control clipping and sharing because extensive clipping (not to mention reaggregation of those clips out of context) can violate author, model and photographer contracts they hold with third parties. </p>
<p>Yes publishers can control it to an extent, but  they do not have the time to control every aspect of the content detail. As someone who works for a publisher I know this to be very much part of the legal reality.</p>
<p>Adrienne Kinney, Director of Editorial Rights &amp; Licensing, Rodale</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Thomas</title>
		<link>http://gigaom.com/2012/09/18/betaworks-findings-pivots-as-amazon-bans-kindle-clips/#comment-1004549</link>
		<dc:creator><![CDATA[David Thomas]]></dc:creator>
		<pubDate>Tue, 18 Sep 2012 21:35:07 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=564034#comment-1004549</guid>
		<description><![CDATA[I second Mr. Wikert here: I seriously doubt book publishers would object to e-book consumers essentially promoting their products with small portions of legitimately acquired content. The ability to share wisdom, laughs, poignancy and facts discovered in books is very best advertising that money can&#039;t buy.]]></description>
		<content:encoded><![CDATA[<p>I second Mr. Wikert here: I seriously doubt book publishers would object to e-book consumers essentially promoting their products with small portions of legitimately acquired content. The ability to share wisdom, laughs, poignancy and facts discovered in books is very best advertising that money can&#8217;t buy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Wikert</title>
		<link>http://gigaom.com/2012/09/18/betaworks-findings-pivots-as-amazon-bans-kindle-clips/#comment-1004376</link>
		<dc:creator><![CDATA[Joe Wikert]]></dc:creator>
		<pubDate>Tue, 18 Sep 2012 20:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=564034#comment-1004376</guid>
		<description><![CDATA[I read Lauren&#039;s separate blog post and I find it hard to believe publishers are the reason for this change. Findings helps with the discovery process by letting readers share interesting excerpts. There&#039;s no piracy issue here. What&#039;s at stake is Amazon&#039;s complete ownership of the content discovery and consumption experience. As a reader I&#039;m disappointed and as a publisher I&#039;m outraged by this situation.]]></description>
		<content:encoded><![CDATA[<p>I read Lauren&#8217;s separate blog post and I find it hard to believe publishers are the reason for this change. Findings helps with the discovery process by letting readers share interesting excerpts. There&#8217;s no piracy issue here. What&#8217;s at stake is Amazon&#8217;s complete ownership of the content discovery and consumption experience. As a reader I&#8217;m disappointed and as a publisher I&#8217;m outraged by this situation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
