<?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: Jeffrey&#8217;s &#8220;Export to Flickr&#8221; Lightroom Plugin</title>
	<atom:link href="http://regex.info/blog/lightroom-goodies/flickr/feed" rel="self" type="application/rss+xml" />
	<link>http://regex.info/blog</link>
	<description>Not a photo blog. A personal blog with photos.</description>
	<lastBuildDate>Wed, 23 May 2012 20:38:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Daniel</title>
		<link>http://regex.info/blog/lightroom-goodies/flickr#comment-46235</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Mon, 14 May 2012 06:17:36 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/flickr/#comment-46235</guid>
		<description>Wow, I am truly impressed that you still support Lr2. I can&#039;t even remember what it was in those days!

To whoever is still using Lr2: It is time to move on. Lr4 has so many new features and the new process version 2012 is great! You can get so much more out of your images.</description>
		<content:encoded><![CDATA[<p>Wow, I am truly impressed that you still support Lr2. I can&#8217;t even remember what it was in those days!</p>
<p>To whoever is still using Lr2: It is time to move on. Lr4 has so many new features and the new process version 2012 is great! You can get so much more out of your images.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Blackburn</title>
		<link>http://regex.info/blog/lightroom-goodies/flickr#comment-46213</link>
		<dc:creator>Phil Blackburn</dc:creator>
		<pubDate>Sun, 13 May 2012 07:43:42 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/flickr/#comment-46213</guid>
		<description>I had already tried deselecting &quot;Include on Export&quot; however this then prevents the Image visibility rules from working - I guess that&#039;s because your publish service only gets to see what Lightroom has exported rather than what is in the catalog?   On the off-chance that this is a bug, I&#039;m using version  20120508.274;   LR4.0;   Win 7.

&lt;span class=&#039;jfriedl&#039;&gt;The plugin should be checking all keywords, not just exportable ones, so indeed it may be a bug. Try a small test, when it doesn&#039;t work as you expect, &lt;a href=&#039;http://regex.info/blog/lightroom-goodies/faq#log&#039; rel=&quot;nofollow&quot;&gt;send a log&lt;/a&gt; along with a note about how what did happen differs from what you expected. Thanks. &#8212;Jeffrey&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p>I had already tried deselecting &#8220;Include on Export&#8221; however this then prevents the Image visibility rules from working &#8211; I guess that&#8217;s because your publish service only gets to see what Lightroom has exported rather than what is in the catalog?   On the off-chance that this is a bug, I&#8217;m using version  20120508.274;   LR4.0;   Win 7.</p>
<p><span class='jfriedl'>The plugin should be checking all keywords, not just exportable ones, so indeed it may be a bug. Try a small test, when it doesn&#8217;t work as you expect, <a href='http://regex.info/blog/lightroom-goodies/faq#log' rel="nofollow">send a log</a> along with a note about how what did happen differs from what you expected. Thanks. &mdash;Jeffrey</span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cletus Lee</title>
		<link>http://regex.info/blog/lightroom-goodies/flickr#comment-46210</link>
		<dc:creator>Cletus Lee</dc:creator>
		<pubDate>Sun, 13 May 2012 02:19:35 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/flickr/#comment-46210</guid>
		<description>I&#039;ve used these deselected &quot;Include on Export&quot; keywords to populate Smart Publish Service  collections for some time.  My internal keyword &quot;@flickr&quot; gets the image included in a jfFlickr Publish Collection.  Another Keyword determines which Flickr set will get the assignment.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve used these deselected &#8220;Include on Export&#8221; keywords to populate Smart Publish Service  collections for some time.  My internal keyword &#8220;@flickr&#8221; gets the image included in a jfFlickr Publish Collection.  Another Keyword determines which Flickr set will get the assignment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Blackburn</title>
		<link>http://regex.info/blog/lightroom-goodies/flickr#comment-46207</link>
		<dc:creator>Phil Blackburn</dc:creator>
		<pubDate>Sat, 12 May 2012 18:34:14 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/flickr/#comment-46207</guid>
		<description>Would it be possible for jdflickr to detect a keyword with a user-specified &quot;{namespace}:&quot; and then block that keyword from being upload?

I&#039;ve started making use of the feature to update the flickr privacy and very useful it is too. However, it not alway practical to use my existing keywords and I so I&#039;ve ended up with a small set dedicate keywords for the purpose: In my case I&#039;m using &quot;flickr:friends&quot; and &quot;flickr:family&quot;.  I&#039;ve used  namespace/machine-tag format here since it is in effect a control keyword rather than descriptive of the image. No only does the namespace help isolate it from other descriptive keywords but has the added benefit of keeping the keywords close to each other in the list.  For me these &#039;machine tags&#039; have no purpose apart from controlling jd Flickr but of course they end up on my flickr page.  Would be just perfect if jdFlickr make them dissappear.
&lt;span class=&#039;jfriedl&#039;&gt;Lightroom lets you set any keyword to not export... visit a keyword&#039;s &quot;Edit&quot; page via the context menu for the keyword in the &quot;Keyword List&quot; panel, and deselect &quot;Include on Export&quot;. &#8212;Jeffrey&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p>Would it be possible for jdflickr to detect a keyword with a user-specified &#8220;{namespace}:&#8221; and then block that keyword from being upload?</p>
<p>I&#8217;ve started making use of the feature to update the flickr privacy and very useful it is too. However, it not alway practical to use my existing keywords and I so I&#8217;ve ended up with a small set dedicate keywords for the purpose: In my case I&#8217;m using &#8220;flickr:friends&#8221; and &#8220;flickr:family&#8221;.  I&#8217;ve used  namespace/machine-tag format here since it is in effect a control keyword rather than descriptive of the image. No only does the namespace help isolate it from other descriptive keywords but has the added benefit of keeping the keywords close to each other in the list.  For me these &#8216;machine tags&#8217; have no purpose apart from controlling jd Flickr but of course they end up on my flickr page.  Would be just perfect if jdFlickr make them dissappear.<br />
<span class='jfriedl'>Lightroom lets you set any keyword to not export&#8230; visit a keyword&#8217;s &#8220;Edit&#8221; page via the context menu for the keyword in the &#8220;Keyword List&#8221; panel, and deselect &#8220;Include on Export&#8221;. &mdash;Jeffrey</span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pl_svn</title>
		<link>http://regex.info/blog/lightroom-goodies/flickr#comment-46132</link>
		<dc:creator>pl_svn</dc:creator>
		<pubDate>Mon, 30 Apr 2012 13:00:22 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/flickr/#comment-46132</guid>
		<description>... not only Lightroom &quot;doesn&#039;t give the plugin insight into what has changed&quot;, it doesn&#039;t give *the user* any insight!!!

I recently reinstalled the OS (thanks, Lion :-/ ) and now almost every picture has the exclamation mark stating that metadata are out of synch between my catalog and my files but... how can I check which are the right ones? :-/

not a question: just a rant! ;-(</description>
		<content:encoded><![CDATA[<p>&#8230; not only Lightroom &#8220;doesn&#8217;t give the plugin insight into what has changed&#8221;, it doesn&#8217;t give *the user* any insight!!!</p>
<p>I recently reinstalled the OS (thanks, Lion :-/ ) and now almost every picture has the exclamation mark stating that metadata are out of synch between my catalog and my files but&#8230; how can I check which are the right ones? :-/</p>
<p>not a question: just a rant! ;-(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://regex.info/blog/lightroom-goodies/flickr#comment-46131</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 30 Apr 2012 10:10:10 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/flickr/#comment-46131</guid>
		<description>Thanks very much for the quick reply, I&#039;ll look at the Library Grid Filter and see how that works and look forward to the light on the horizon ;-)</description>
		<content:encoded><![CDATA[<p>Thanks very much for the quick reply, I&#8217;ll look at the Library Grid Filter and see how that works and look forward to the light on the horizon <img src='http://regex.info/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://regex.info/blog/lightroom-goodies/flickr#comment-46130</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 30 Apr 2012 09:34:37 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/flickr/#comment-46130</guid>
		<description>Hi,

First off great plugin that despite what I&#039;m about to say is invaluable.
The issue I&#039;m having is that I use lots of smart groups so that I can keep track of not only the image content but also the lens and body so that I can easily offer advice to others online and point them to my flickr (just back history to explain i use lots of smart groups and why)

Anyway after I&#039;ve published an image I will sometimes alter the metadata - just name the type of insect, that sort of thing - no actual adjustment to image, which will rightly mark it to be re-published, the problem comes now that sometimes it just flies through the images updating the tags, but often it uploads the whole image again and that breaks the naming of the files as used on forums and so forth, which as I&#039;m running a 365 project (take a photo a day and upload) breaks the images quite a lot.

Also worth noting is that publishing via multiple groups seems to do the same thing too even if metadata has not changed.

I had this before with lightroom three but it seems much worse under lightroom 4.0 - I have just now upgraded to the very latest version (20120429.272) and just saw the same thing an a re-publish I was half way through but stopped to test the latest version.

Sorry that was so long and thanks again.

&lt;span class=&#039;jfriedl&#039;&gt;Unfortunately, that&#039;s how Lightroom is designed.. it doesn&#039;t give the plugin insight into what has changed. There may be light on the horizon, but for now this is how it works. You can handle the metadata upload manually (via the Plugin-extras dialog), and then mark the images as unchanged. It&#039;s a hassle, but that&#039;s the best I can suggest at the moment. (However, tangentially, you can use the Library Grid Filter to isolate upload-to-Flickr images by lens, body, etc., on the fly, which may eliminate your need for so many groups.) &#8212;Jeffrey&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>First off great plugin that despite what I&#8217;m about to say is invaluable.<br />
The issue I&#8217;m having is that I use lots of smart groups so that I can keep track of not only the image content but also the lens and body so that I can easily offer advice to others online and point them to my flickr (just back history to explain i use lots of smart groups and why)</p>
<p>Anyway after I&#8217;ve published an image I will sometimes alter the metadata &#8211; just name the type of insect, that sort of thing &#8211; no actual adjustment to image, which will rightly mark it to be re-published, the problem comes now that sometimes it just flies through the images updating the tags, but often it uploads the whole image again and that breaks the naming of the files as used on forums and so forth, which as I&#8217;m running a 365 project (take a photo a day and upload) breaks the images quite a lot.</p>
<p>Also worth noting is that publishing via multiple groups seems to do the same thing too even if metadata has not changed.</p>
<p>I had this before with lightroom three but it seems much worse under lightroom 4.0 &#8211; I have just now upgraded to the very latest version (20120429.272) and just saw the same thing an a re-publish I was half way through but stopped to test the latest version.</p>
<p>Sorry that was so long and thanks again.</p>
<p><span class='jfriedl'>Unfortunately, that&#8217;s how Lightroom is designed.. it doesn&#8217;t give the plugin insight into what has changed. There may be light on the horizon, but for now this is how it works. You can handle the metadata upload manually (via the Plugin-extras dialog), and then mark the images as unchanged. It&#8217;s a hassle, but that&#8217;s the best I can suggest at the moment. (However, tangentially, you can use the Library Grid Filter to isolate upload-to-Flickr images by lens, body, etc., on the fly, which may eliminate your need for so many groups.) &mdash;Jeffrey</span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Hunt</title>
		<link>http://regex.info/blog/lightroom-goodies/flickr#comment-46121</link>
		<dc:creator>Matthew Hunt</dc:creator>
		<pubDate>Sun, 29 Apr 2012 15:10:10 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/flickr/#comment-46121</guid>
		<description>Thanks, Jeffrey! I tried 20120429.272 with &quot;don&#039;t set any specific location visibility&quot; and it works great for me. I tested it with photos inside and outside my geofences, and with GPS data in the photos at the time of upload and with it added later via &quot;Resend Metadata&quot;, and it worked correctly in each case. Strangers could see the location of photos outside my geofence, but not inside.</description>
		<content:encoded><![CDATA[<p>Thanks, Jeffrey! I tried 20120429.272 with &#8220;don&#8217;t set any specific location visibility&#8221; and it works great for me. I tested it with photos inside and outside my geofences, and with GPS data in the photos at the time of upload and with it added later via &#8220;Resend Metadata&#8221;, and it worked correctly in each case. Strangers could see the location of photos outside my geofence, but not inside.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Whiteman</title>
		<link>http://regex.info/blog/lightroom-goodies/flickr#comment-46120</link>
		<dc:creator>Aaron Whiteman</dc:creator>
		<pubDate>Sun, 29 Apr 2012 14:03:39 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/flickr/#comment-46120</guid>
		<description>&lt;cite&gt;I’m at a loss to explain what page on I was on when I first replied to this comment, but my mental logjam has cleared and I finally understand what I should have understood long ago, and I just pushed a new version of the plugin that addresses this properly. Thanks for your patience. —Jeffrey&lt;/cite&gt;

Thank you Jeffrey, I just updated the plugin and verified that the new &quot;don&#039;t set&quot; setting works perfectly for the geofence I have set up around my parents&#039; home.</description>
		<content:encoded><![CDATA[<p><cite>I’m at a loss to explain what page on I was on when I first replied to this comment, but my mental logjam has cleared and I finally understand what I should have understood long ago, and I just pushed a new version of the plugin that addresses this properly. Thanks for your patience. —Jeffrey</cite></p>
<p>Thank you Jeffrey, I just updated the plugin and verified that the new &#8220;don&#8217;t set&#8221; setting works perfectly for the geofence I have set up around my parents&#8217; home.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Hunt</title>
		<link>http://regex.info/blog/lightroom-goodies/flickr#comment-46094</link>
		<dc:creator>Matthew Hunt</dc:creator>
		<pubDate>Thu, 26 Apr 2012 14:24:54 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/flickr/#comment-46094</guid>
		<description>FWIW, I agree with Dave Townsend&#039;s interpretation of the geofence issue and Flickr&#039;s response. All the uploader needs is an option to upload the GPS tags without explicitly setting the Flickr location permissions. That should allow the Flickr defaults, including geofences, to take effect.

&lt;span class=&#039;jfriedl&#039;&gt;I&#039;m at a loss to explain what page on I was on when I first replied to this comment, but my mental logjam has cleared and I finally understand what I should have understood long ago, and I just pushed a new version of the plugin that addresses this properly. Thanks for your patience. &#8212;Jeffrey&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p>FWIW, I agree with Dave Townsend&#8217;s interpretation of the geofence issue and Flickr&#8217;s response. All the uploader needs is an option to upload the GPS tags without explicitly setting the Flickr location permissions. That should allow the Flickr defaults, including geofences, to take effect.</p>
<p><span class='jfriedl'>I&#8217;m at a loss to explain what page on I was on when I first replied to this comment, but my mental logjam has cleared and I finally understand what I should have understood long ago, and I just pushed a new version of the plugin that addresses this properly. Thanks for your patience. &mdash;Jeffrey</span></p>
]]></content:encoded>
	</item>
</channel>
</rss>

