<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Flickr&#8217;s Big Fail On Creative Common&#8217;s Attribution Guidelines</title>
	<atom:link href="http://daggle.com/flickr-fail-on-creative-commons-attribution-691/feed" rel="self" type="application/rss+xml" />
	<link>http://daggle.com/flickr-fail-on-creative-commons-attribution-691</link>
	<description>Danny Sullivan&#039;s Personal Blog</description>
	<lastBuildDate>Thu, 18 Mar 2010 22:23:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Robb Shecter</title>
		<link>http://daggle.com/flickr-fail-on-creative-commons-attribution-691/comment-page-1#comment-11284</link>
		<dc:creator>Robb Shecter</dc:creator>
		<pubDate>Tue, 17 Nov 2009 08:59:55 +0000</pubDate>
		<guid isPermaLink="false">http://daggle.com/?p=691#comment-11284</guid>
		<description>Yes yes yes!!  I&#039;ve gone through these EXACT SAME STEPS and been frustrated every time for the exact same reasons.  Thanks for taking the time to spell it out.

The first case you describe (no attribution info spec&#039;d) is by far the most common.  

I&#039;m frequently looking for CC photos I can use in the sites I build --- it&#039;s a win-win.  I get unique works, and the creators get more exposure.  It shouldn&#039;t be hard to do the right thing.</description>
		<content:encoded><![CDATA[<p>Yes yes yes!!  I&#8217;ve gone through these EXACT SAME STEPS and been frustrated every time for the exact same reasons.  Thanks for taking the time to spell it out.</p>
<p>The first case you describe (no attribution info spec&#8217;d) is by far the most common.  </p>
<p>I&#8217;m frequently looking for CC photos I can use in the sites I build &#8212; it&#8217;s a win-win.  I get unique works, and the creators get more exposure.  It shouldn&#8217;t be hard to do the right thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian</title>
		<link>http://daggle.com/flickr-fail-on-creative-commons-attribution-691/comment-page-1#comment-3594</link>
		<dc:creator>Adrian</dc:creator>
		<pubDate>Fri, 10 Jul 2009 07:26:54 +0000</pubDate>
		<guid isPermaLink="false">http://daggle.com/?p=691#comment-3594</guid>
		<description>Creative Commons says the Attribution license (which is on all CC photos): &quot;You let others copy, distribute, display, and perform your copyrighted work — and derivative works based upon it — but only if they give credit the way you request.&quot;
The usual way to do this is by adding the name of the photographer and a link to where the photo is from. The issue on Flickr is to decide if you use the user&#039;s name or username which aren&#039;t always the same though users sometimes speciy which to use on their profile page and where to linkback.</description>
		<content:encoded><![CDATA[<p>Creative Commons says the Attribution license (which is on all CC photos): &#8220;You let others copy, distribute, display, and perform your copyrighted work — and derivative works based upon it — but only if they give credit the way you request.&#8221;<br />
The usual way to do this is by adding the name of the photographer and a link to where the photo is from. The issue on Flickr is to decide if you use the user&#8217;s name or username which aren&#8217;t always the same though users sometimes speciy which to use on their profile page and where to linkback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Aulia</title>
		<link>http://daggle.com/flickr-fail-on-creative-commons-attribution-691/comment-page-1#comment-3582</link>
		<dc:creator>Michael Aulia</dc:creator>
		<pubDate>Thu, 09 Jul 2009 23:38:09 +0000</pubDate>
		<guid isPermaLink="false">http://daggle.com/?p=691#comment-3582</guid>
		<description>It is frustrating in some ways. I thought that linking back from the image to the Flickr page is enough. Even last time I thought if I searched for images that can be used for commercial purposes, you didn&#039;t even need a link back.

So the question remains, is linking back to the photo flickr page enough or you really have to credit the photographer&#039;s name on the posts with links etc?</description>
		<content:encoded><![CDATA[<p>It is frustrating in some ways. I thought that linking back from the image to the Flickr page is enough. Even last time I thought if I searched for images that can be used for commercial purposes, you didn&#8217;t even need a link back.</p>
<p>So the question remains, is linking back to the photo flickr page enough or you really have to credit the photographer&#8217;s name on the posts with links etc?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian</title>
		<link>http://daggle.com/flickr-fail-on-creative-commons-attribution-691/comment-page-1#comment-2732</link>
		<dc:creator>Adrian</dc:creator>
		<pubDate>Wed, 17 Jun 2009 13:17:26 +0000</pubDate>
		<guid isPermaLink="false">http://daggle.com/?p=691#comment-2732</guid>
		<description>Interesting article. We have our own way of doing it at Fotopedia through widgets which have the attribution, license and link issues dealt with. I&#039;d be interested to know what you think about it: &lt;a href=&quot;http://www.fotopedia.com&quot; rel=&quot;nofollow&quot;&gt;fotopedia&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Interesting article. We have our own way of doing it at Fotopedia through widgets which have the attribution, license and link issues dealt with. I&#8217;d be interested to know what you think about it: <a href="http://www.fotopedia.com" rel="nofollow">fotopedia</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scott lewis</title>
		<link>http://daggle.com/flickr-fail-on-creative-commons-attribution-691/comment-page-1#comment-2423</link>
		<dc:creator>scott lewis</dc:creator>
		<pubDate>Mon, 15 Jun 2009 00:04:48 +0000</pubDate>
		<guid isPermaLink="false">http://daggle.com/?p=691#comment-2423</guid>
		<description>Great comment on the probs with Flickr. Like you I find it so frustrating when you want to comply with CC copyright, and a sophisticated provider like Flickr makes it hard to do.
If you dig into the code for the Flickr photo pages, you come up with this fragment:&lt;code&gt;
Uploaded on &lt;a href=&quot;/photos/kt/archives/date-posted/2004/10/29/&quot; rel=&quot;nofollow&quot;&gt;October 29, 2004&lt;/a&gt; by &lt;a href=&quot;/photos/kt/&quot; title=&quot;Link to The Rocketeer&#039;s photostream&quot; rel=&quot;nofollow&quot;&gt;&lt;b&gt;The Rocketeer&lt;/b&gt;&lt;/a&gt;
&lt;/code&gt;
Note the part of the A tag, which has the curious attribute: rel=&quot;dc:creator cc:attributionURL&quot;&gt;. Digging around through some searches, it looks like this is, indeed, the attribution URL as specified by Creative Commons. (Though why is it a relative url?) So I guess you would use the person&#039;s Flickr name linked through this URL. Though as your case study suggests, this might not satisfy some individuals, I would think you would be legally covered to some extent. Obviously this applies more to parsing these pages automatically, but it is a hint as to what should be done manually as well. Thanks for the post.</description>
		<content:encoded><![CDATA[<p>Great comment on the probs with Flickr. Like you I find it so frustrating when you want to comply with CC copyright, and a sophisticated provider like Flickr makes it hard to do.<br />
If you dig into the code for the Flickr photo pages, you come up with this fragment:<code><br />
Uploaded on <a href="/photos/kt/archives/date-posted/2004/10/29/" rel="nofollow">October 29, 2004</a> by <a href="/photos/kt/" title="Link to The Rocketeer's photostream" rel="nofollow"><b>The Rocketeer</b></a><br />
</code><br />
Note the part of the A tag, which has the curious attribute: rel=&#8221;dc:creator cc:attributionURL&#8221;&gt;. Digging around through some searches, it looks like this is, indeed, the attribution URL as specified by Creative Commons. (Though why is it a relative url?) So I guess you would use the person&#8217;s Flickr name linked through this URL. Though as your case study suggests, this might not satisfy some individuals, I would think you would be legally covered to some extent. Obviously this applies more to parsing these pages automatically, but it is a hint as to what should be done manually as well. Thanks for the post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jlbraaten</title>
		<link>http://daggle.com/flickr-fail-on-creative-commons-attribution-691/comment-page-1#comment-1559</link>
		<dc:creator>jlbraaten</dc:creator>
		<pubDate>Mon, 08 Jun 2009 03:54:30 +0000</pubDate>
		<guid isPermaLink="false">http://daggle.com/?p=691#comment-1559</guid>
		<description>All this Creative Commons stuff is confusing to me.  I just went with the $1 images over at Fotolia.com.  When in doubt, pay a dollar :D</description>
		<content:encoded><![CDATA[<p>All this Creative Commons stuff is confusing to me.  I just went with the $1 images over at Fotolia.com.  When in doubt, pay a dollar <img src='http://daggle.com/wordpress/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: miha</title>
		<link>http://daggle.com/flickr-fail-on-creative-commons-attribution-691/comment-page-1#comment-1558</link>
		<dc:creator>miha</dc:creator>
		<pubDate>Sun, 07 Jun 2009 23:33:12 +0000</pubDate>
		<guid isPermaLink="false">http://daggle.com/?p=691#comment-1558</guid>
		<description>Well, CC license for Mark’s photo makes it quite clear:
&lt;/cite&gt;If you distribute, publicly display, publicly perform, or publicly digitally perform the Work, You must keep intact all &lt;b&gt;copyright notices&lt;/b&gt; for the Work and give the Original Author credit reasonable to the medium or means You are utilizing by conveying &lt;b&gt;the name&lt;/b&gt; (or pseudonym if applicable) of the Original Author if supplied; &lt;b&gt;the title&lt;/b&gt; of the Work if supplied; and to the extent reasonably practicable, the &lt;b&gt;Uniform Resource Identifier&lt;/b&gt;, if any, that Licensor specifies to be associated with the Work, unless such URI does not refer to the copyright notice or licensing information for the Work. Such credit may be implemented in any reasonable manner; provided, however, that in the case of a Collective Work, at a minimum such credit will appear where any other comparable authorship credit appears and in a manner at least as prominent as such other comparable authorship credit.&lt;/cite&gt;</description>
		<content:encoded><![CDATA[<p>Well, CC license for Mark’s photo makes it quite clear:<br />
If you distribute, publicly display, publicly perform, or publicly digitally perform the Work, You must keep intact all <b>copyright notices</b> for the Work and give the Original Author credit reasonable to the medium or means You are utilizing by conveying <b>the name</b> (or pseudonym if applicable) of the Original Author if supplied; <b>the title</b> of the Work if supplied; and to the extent reasonably practicable, the <b>Uniform Resource Identifier</b>, if any, that Licensor specifies to be associated with the Work, unless such URI does not refer to the copyright notice or licensing information for the Work. Such credit may be implemented in any reasonable manner; provided, however, that in the case of a Collective Work, at a minimum such credit will appear where any other comparable authorship credit appears and in a manner at least as prominent as such other comparable authorship credit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tyler Yip</title>
		<link>http://daggle.com/flickr-fail-on-creative-commons-attribution-691/comment-page-1#comment-1547</link>
		<dc:creator>Tyler Yip</dc:creator>
		<pubDate>Fri, 05 Jun 2009 19:52:44 +0000</pubDate>
		<guid isPermaLink="false">http://daggle.com/?p=691#comment-1547</guid>
		<description>Interesting viewpoint.

After reading your comments about the problems I had getting CrunchGear and TechCrunch to comply with my photo&#039;s license and your comment about my own statement about proper photo credits, I have added a more explicit description of my expectations for a photo credit as required by the license I have applied to my photo.</description>
		<content:encoded><![CDATA[<p>Interesting viewpoint.</p>
<p>After reading your comments about the problems I had getting CrunchGear and TechCrunch to comply with my photo&#8217;s license and your comment about my own statement about proper photo credits, I have added a more explicit description of my expectations for a photo credit as required by the license I have applied to my photo.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://daggle.com/flickr-fail-on-creative-commons-attribution-691/comment-page-1#comment-1541</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Thu, 04 Jun 2009 19:27:04 +0000</pubDate>
		<guid isPermaLink="false">http://daggle.com/?p=691#comment-1541</guid>
		<description>&quot;It’s like driving to work everyday and ignoring the posted speed limit because it doesn’t “work” for you.&quot;

If you&#039;re driving the speed limit, good for you, but ... doesn&#039;t the honking bother you?</description>
		<content:encoded><![CDATA[<p>&#8220;It’s like driving to work everyday and ignoring the posted speed limit because it doesn’t “work” for you.&#8221;</p>
<p>If you&#8217;re driving the speed limit, good for you, but &#8230; doesn&#8217;t the honking bother you?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mconnors</title>
		<link>http://daggle.com/flickr-fail-on-creative-commons-attribution-691/comment-page-1#comment-1520</link>
		<dc:creator>mconnors</dc:creator>
		<pubDate>Mon, 01 Jun 2009 21:57:02 +0000</pubDate>
		<guid isPermaLink="false">http://daggle.com/?p=691#comment-1520</guid>
		<description>You can use http://morguefile.com, we have the easiest to use free photo license and an advanced filtering/ sorting utilities.</description>
		<content:encoded><![CDATA[<p>You can use <a href="http://morguefile.com" rel="nofollow">http://morguefile.com</a>, we have the easiest to use free photo license and an advanced filtering/ sorting utilities.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
