<?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"
	>
<channel>
	<title>Comments on: Using Flickr for website images</title>
	<atom:link href="http://xebidy.com/2008/02/using-flickr-for-website-images/feed/" rel="self" type="application/rss+xml" />
	<link>http://xebidy.com/2008/02/using-flickr-for-website-images/</link>
	<description>Web 2.0 eCommerce Strategy Design and Implementation</description>
	<pubDate>Sun, 27 Jul 2008 08:36:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Andrew</title>
		<link>http://xebidy.com/2008/02/using-flickr-for-website-images/#comment-3263</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Thu, 21 Feb 2008 04:30:46 +0000</pubDate>
		<guid isPermaLink="false">http://xebidy.com/?p=133#comment-3263</guid>
		<description>Just looking on the forums - I think the approach is okay - check out http://www.flickr.com/help/forum/29690/ (though there is heaps of other threads on the subject)

Stewart response from Flickr - re their hard line ethos approach is very informative.</description>
		<content:encoded><![CDATA[<p>Just looking on the forums - I think the approach is okay - check out <a href="http://www.flickr.com/help/forum/29690/" rel="nofollow">http://www.flickr.com/help/forum/29690/</a> (though there is heaps of other threads on the subject)</p>
<p>Stewart response from Flickr - re their hard line ethos approach is very informative.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://xebidy.com/2008/02/using-flickr-for-website-images/#comment-3246</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Thu, 21 Feb 2008 03:22:18 +0000</pubDate>
		<guid isPermaLink="false">http://xebidy.com/?p=133#comment-3246</guid>
		<description>Cool - I'll have to look into it.

At the time I was just a little apprehensive about basing an important  part of the site (i.e. the imagery) on a third party server when I was unsure whether or not that could suspend the account at some later date.

Though from what you say the Pro account guidelines have changed - so should be all okay now.</description>
		<content:encoded><![CDATA[<p>Cool - I&#8217;ll have to look into it.</p>
<p>At the time I was just a little apprehensive about basing an important  part of the site (i.e. the imagery) on a third party server when I was unsure whether or not that could suspend the account at some later date.</p>
<p>Though from what you say the Pro account guidelines have changed - so should be all okay now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: xebidy</title>
		<link>http://xebidy.com/2008/02/using-flickr-for-website-images/#comment-3231</link>
		<dc:creator>xebidy</dc:creator>
		<pubDate>Thu, 21 Feb 2008 02:18:24 +0000</pubDate>
		<guid isPermaLink="false">http://xebidy.com/?p=133#comment-3231</guid>
		<description>Hi Andrew, yeah it seems like a grey area, but we purchased a pro account for all the examples above and in the promotional material it says for holding large quantities of photos for businesses etc.</description>
		<content:encoded><![CDATA[<p>Hi Andrew, yeah it seems like a grey area, but we purchased a pro account for all the examples above and in the promotional material it says for holding large quantities of photos for businesses etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://xebidy.com/2008/02/using-flickr-for-website-images/#comment-3154</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Wed, 20 Feb 2008 00:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://xebidy.com/?p=133#comment-3154</guid>
		<description>Hey mate - what are the current rules governing this? I looked into it a few years ago and the previous Flickr Terms of Use were:

"Flickr is intended for personal use and is not a generic image hosting service. Professional or corporate uses of Flickr are prohibited."

When I looked again last year these had changed - though it still seemed a grey area: 

"DonÃ¢â‚¬â„¢t use Flickr for commercial purposes. Flickr is for personal use only... "

And lot of the discussions I read since still point it being against the terms for a company to use Flickr as an image hosting service for their commercial website (even if you have a valid API account and so forth - as the commercial use of this seems to surround what you build i.e. the application - rather than it's use). 

Just wondering if you have had any experience with this - as I'd still like to incorporate the same type of system as you mention above into our websites (I'd developed an upload system based on their APU for staff and web visitors to submit their photos directly to our Flickr account via our website - however never ended up using it for the above reasons).</description>
		<content:encoded><![CDATA[<p>Hey mate - what are the current rules governing this? I looked into it a few years ago and the previous Flickr Terms of Use were:</p>
<p>&#8220;Flickr is intended for personal use and is not a generic image hosting service. Professional or corporate uses of Flickr are prohibited.&#8221;</p>
<p>When I looked again last year these had changed - though it still seemed a grey area: </p>
<p>&#8220;DonÃ¢â‚¬â„¢t use Flickr for commercial purposes. Flickr is for personal use only&#8230; &#8221;</p>
<p>And lot of the discussions I read since still point it being against the terms for a company to use Flickr as an image hosting service for their commercial website (even if you have a valid API account and so forth - as the commercial use of this seems to surround what you build i.e. the application - rather than it&#8217;s use). </p>
<p>Just wondering if you have had any experience with this - as I&#8217;d still like to incorporate the same type of system as you mention above into our websites (I&#8217;d developed an upload system based on their APU for staff and web visitors to submit their photos directly to our Flickr account via our website - however never ended up using it for the above reasons).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
