<?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: The danger of posting a decent photograph</title>
	<atom:link href="http://www.regularjen.com/archives/2009/06/19/the-danger-of-posting-a-decent-photograph/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.regularjen.com/archives/2009/06/19/the-danger-of-posting-a-decent-photograph/</link>
	<description>sharing too much since 2003</description>
	<lastBuildDate>Mon, 06 Feb 2012 16:20:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: jEN</title>
		<link>http://www.regularjen.com/archives/2009/06/19/the-danger-of-posting-a-decent-photograph/comment-page-1/#comment-100404</link>
		<dc:creator>jEN</dc:creator>
		<pubDate>Fri, 19 Jun 2009 16:20:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.regularjen.com/?p=1582#comment-100404</guid>
		<description>Thank you CC :)

I agree- and asking a simple permission question is so easy! Asking permission on flickr is a no-brainer. Asking from a blog is typically easy enough with contact emails, contact forms, comments, or even a whois lookup. There is no excuse for lazy theft. Makes me sad too.

It is flattering to be asked permission and on a couple of occasions I&#039;ve even granted it (not ever without a paper trail, of course).

At the very least, if a person cannot be absolutely certain of the origins of a work, then that person needs to move on to Plan B and leave Plan A alone. It&#039;s easy to be honest.</description>
		<content:encoded><![CDATA[<p>Thank you CC <img src='http://www.regularjen.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I agree- and asking a simple permission question is so easy! Asking permission on flickr is a no-brainer. Asking from a blog is typically easy enough with contact emails, contact forms, comments, or even a whois lookup. There is no excuse for lazy theft. Makes me sad too.</p>
<p>It is flattering to be asked permission and on a couple of occasions I&#8217;ve even granted it (not ever without a paper trail, of course).</p>
<p>At the very least, if a person cannot be absolutely certain of the origins of a work, then that person needs to move on to Plan B and leave Plan A alone. It&#8217;s easy to be honest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C.C. Chapman</title>
		<link>http://www.regularjen.com/archives/2009/06/19/the-danger-of-posting-a-decent-photograph/comment-page-1/#comment-100403</link>
		<dc:creator>C.C. Chapman</dc:creator>
		<pubDate>Fri, 19 Jun 2009 16:07:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.regularjen.com/?p=1582#comment-100403</guid>
		<description>I&#039;m glad the problem was resolved, but it is sad that so many sites and individuals can&#039;t take the simple step of asking for permission to use a photo.

I know most of us who share our photography online would be flattered to be approached and asked about using a photo in a situation like this. Most of us just want to have a proper credit and a link back to us so other people can discover our photography.

I&#039;m not looking for money as much as I just want credit.

Glad to hear that this ended well.</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad the problem was resolved, but it is sad that so many sites and individuals can&#8217;t take the simple step of asking for permission to use a photo.</p>
<p>I know most of us who share our photography online would be flattered to be approached and asked about using a photo in a situation like this. Most of us just want to have a proper credit and a link back to us so other people can discover our photography.</p>
<p>I&#8217;m not looking for money as much as I just want credit.</p>
<p>Glad to hear that this ended well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

