<?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: Forgetful Flickr</title>
	<atom:link href="http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/feed/" rel="self" type="application/rss+xml" />
	<link>http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/</link>
	<description>Things that Eric A. Meyer, CSS expert, writes about on his personal Web site; it&#039;s largely Web standards and Web technology, but also various bits of culture, politics, personal observations, and other miscellaneous stuff</description>
	<lastBuildDate>Fri, 10 May 2013 11:50:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Eric Meyer</title>
		<link>http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-42432</link>
		<dc:creator>Eric Meyer</dc:creator>
		<pubDate>Fri, 11 Aug 2006 07:40:20 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-42432</guid>
		<description><![CDATA[Derek:  Wait, so you&#039;re telling me that this behavior a core feature of Flickr, and not just a limitation born of not having worked on authenticated RSS feeds?  Because it seems very strange that photos I can see on a web page don&#039;t show up in an RSS feed of what&#039;s on that page.  (And when the wise man posted that, he was talking about core features of a system.)

Okay, so I get that there are extra security concerns with feeds than there are with viewing pages, but I still don&#039;t see how that can be regarded as a &quot;feature&quot;.  Unless it&#039;s a feature to force users to the Flickr site every now and again, just to see if there&#039;s something their RSS feed has failed to inform them they can see.

Could the feed at least say that there&#039;s a private photo available, without including said image the actual feed, so that we know when to go look?]]></description>
		<content:encoded><![CDATA[<p>Derek:  Wait, so you&#8217;re telling me that this behavior a core feature of Flickr, and not just a limitation born of not having worked on authenticated RSS feeds?  Because it seems very strange that photos I can see on a web page don&#8217;t show up in an RSS feed of what&#8217;s on that page.  (And when the wise man posted that, he was talking about core features of a system.)</p>
<p>Okay, so I get that there are extra security concerns with feeds than there are with viewing pages, but I still don&#8217;t see how that can be regarded as a &#8220;feature&#8221;.  Unless it&#8217;s a feature to force users to the Flickr site every now and again, just to see if there&#8217;s something their RSS feed has failed to inform them they can see.</p>
<p>Could the feed at least say that there&#8217;s a private photo available, without including said image the actual feed, so that we know when to go look?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek Powazek</title>
		<link>http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-42411</link>
		<dc:creator>Derek Powazek</dc:creator>
		<pubDate>Fri, 11 Aug 2006 01:25:44 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-42411</guid>
		<description><![CDATA[Making photos private means keeping them out of public view. As a wise man recently posted: &quot;Accept it and move on, or reject it and walk away, but don&quot;t waste your time complaining about it.&quot;

I consider having my private photos kept out of RSS a feature, not a bug.]]></description>
		<content:encoded><![CDATA[<p>Making photos private means keeping them out of public view. As a wise man recently posted: &#8220;Accept it and move on, or reject it and walk away, but don&#8221;t waste your time complaining about it.&#8221;</p>
<p>I consider having my private photos kept out of RSS a feature, not a bug.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Meriblog: Meri Williams&#8217; Weblog &#187; links for 2006-08-02</title>
		<link>http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-41291</link>
		<dc:creator>Meriblog: Meri Williams&#8217; Weblog &#187; links for 2006-08-02</dc:creator>
		<pubDate>Thu, 03 Aug 2006 08:07:41 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-41291</guid>
		<description><![CDATA[[...] Bloglines &#124; News Cool &#8212; looks like Bloglines are taking on feed access control head-on, which I&#8217;m sure Eric might be pleased to here. Now we just need the Flickr guys to make the same change (tags: flickr rss privacy photos) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Bloglines | News Cool &#8212; looks like Bloglines are taking on feed access control head-on, which I&#8217;m sure Eric might be pleased to here. Now we just need the Flickr guys to make the same change (tags: flickr rss privacy photos) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Meyer</title>
		<link>http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38711</link>
		<dc:creator>Eric Meyer</dc:creator>
		<pubDate>Thu, 06 Jul 2006 15:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38711</guid>
		<description><![CDATA[I &lt;strong&gt;never&lt;/strong&gt; said that I don&#039;t really care about privacy.  I said that I understand that placing photos on a server is already a privacy risk, and using a random-token obscurity approach didn&#039;t seem a huge additional risk.  However, Drew pointed out something I hadn&#039;t considered regarding multi-user aggregators, so I have a different point of view now.

I&#039;m totally happy with an https solution.  Many RSS clients support username/password combinations over https connections, so it&#039;s something Flickr could offer-- in other words, the part of the problem that Flickr can resolve hasn&#039;t been resolved, whereas the other half has been.]]></description>
		<content:encoded><![CDATA[<p>I <strong>never</strong> said that I don&#8217;t really care about privacy.  I said that I understand that placing photos on a server is already a privacy risk, and using a random-token obscurity approach didn&#8217;t seem a huge additional risk.  However, Drew pointed out something I hadn&#8217;t considered regarding multi-user aggregators, so I have a different point of view now.</p>
<p>I&#8217;m totally happy with an https solution.  Many RSS clients support username/password combinations over https connections, so it&#8217;s something Flickr could offer&#8211; in other words, the part of the problem that Flickr can resolve hasn&#8217;t been resolved, whereas the other half has been.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Isaac Lin</title>
		<link>http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38710</link>
		<dc:creator>Isaac Lin</dc:creator>
		<pubDate>Thu, 06 Jul 2006 15:17:12 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38710</guid>
		<description><![CDATA[It would be misleading for Flickr to provide a half-baked privacy solution, so I disagree with just using randomly generated URLs as a &quot;security through obscurity&quot; solution.

If you don&#039;t really care about privacy, then wouldn&#039;t it be sufficient to leave the photos as public, but to tag it with some kind of FamilyAndFriends tag? (Flickr could help automate the application of this tag.)

Both your and Jeffrey&#039;s suggestions about having private information available through an RSS feed falls into the trap of thinking of RSS as a push delivery method. With its current design, though, the RSS clients would have to support authentication (say, an HTTPS connection with your Flickr password stored in the RSS client). So it isn&#039;t something solely under the control of Flickr to resolve.]]></description>
		<content:encoded><![CDATA[<p>It would be misleading for Flickr to provide a half-baked privacy solution, so I disagree with just using randomly generated URLs as a &#8220;security through obscurity&#8221; solution.</p>
<p>If you don&#8217;t really care about privacy, then wouldn&#8217;t it be sufficient to leave the photos as public, but to tag it with some kind of FamilyAndFriends tag? (Flickr could help automate the application of this tag.)</p>
<p>Both your and Jeffrey&#8217;s suggestions about having private information available through an RSS feed falls into the trap of thinking of RSS as a push delivery method. With its current design, though, the RSS clients would have to support authentication (say, an HTTPS connection with your Flickr password stored in the RSS client). So it isn&#8217;t something solely under the control of Flickr to resolve.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Drew McLellan</title>
		<link>http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38568</link>
		<dc:creator>Drew McLellan</dc:creator>
		<pubDate>Tue, 04 Jul 2006 11:48:43 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38568</guid>
		<description><![CDATA[One issue with using unguessable tokens in the URL is that multi-user aggregators often share feeds amongst their users in order to prevent multiple fetches of the same content. Therefore its possible that a &#039;secret&#039; feed is presented as an option to users for whom it was never intended. 

Plus, ultimately any URL that you&#039;re requesting once an hour and is being sent clear over the wire and logged in dozens of log files along the way is no secret at all.]]></description>
		<content:encoded><![CDATA[<p>One issue with using unguessable tokens in the URL is that multi-user aggregators often share feeds amongst their users in order to prevent multiple fetches of the same content. Therefore its possible that a &#8216;secret&#8217; feed is presented as an option to users for whom it was never intended. </p>
<p>Plus, ultimately any URL that you&#8217;re requesting once an hour and is being sent clear over the wire and logged in dozens of log files along the way is no secret at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: outbreak &#187; The little bumps of the first time user (written on July 3rd, 2006 by Marko Mrdjenovic)</title>
		<link>http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38437</link>
		<dc:creator>outbreak &#187; The little bumps of the first time user (written on July 3rd, 2006 by Marko Mrdjenovic)</dc:creator>
		<pubDate>Sun, 02 Jul 2006 22:23:17 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38437</guid>
		<description><![CDATA[[...] On a side note, there seems to be a lot going on about Flickr. I haven&#8217;t really used it ever, but I&#8217;m doing it while writing this - I&#8217;ve been trying to get around to posting my pics from @media for some time now. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] On a side note, there seems to be a lot going on about Flickr. I haven&#8217;t really used it ever, but I&#8217;m doing it while writing this &#8211; I&#8217;ve been trying to get around to posting my pics from @media for some time now. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Meriblog: Meri Williams&#8217; Weblog &#187; links for 2006-06-29</title>
		<link>http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38230</link>
		<dc:creator>Meriblog: Meri Williams&#8217; Weblog &#187; links for 2006-06-29</dc:creator>
		<pubDate>Fri, 30 Jun 2006 08:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38230</guid>
		<description><![CDATA[[...] Eric&#8217;s Archived Thoughts: Forgetful Flickr Wouldn&#8217;t it be wonderful if just the simple desire to be able to see friend&#8217;s and families&#8217; photos in Flickr RSS feeds stimulated the Flickr team (who we all know design shit-hot stuff) to solve the problem of secure syndication? (tags: rss flickr design webdevelopment webapplications) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Eric&#8217;s Archived Thoughts: Forgetful Flickr Wouldn&#8217;t it be wonderful if just the simple desire to be able to see friend&#8217;s and families&#8217; photos in Flickr RSS feeds stimulated the Flickr team (who we all know design shit-hot stuff) to solve the problem of secure syndication? (tags: rss flickr design webdevelopment webapplications) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aristotle Pagaltzis</title>
		<link>http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38170</link>
		<dc:creator>Aristotle Pagaltzis</dc:creator>
		<pubDate>Thu, 29 Jun 2006 03:02:16 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38170</guid>
		<description><![CDATA[LiveJournal already does this well. If you subscribe to an LJ feed, you get only the person&quot;s public posts. But you can subscribe to a feed with &lt;code&gt;?auth=digest&lt;/code&gt; added to the URL, which requires you to supply an LJ account and password as HTTP credentials. When you poll such a feed it will contains all the items you could see if you visited the associated journal while logged into the account whose details you&quot;ve provided.

It&quot;s a no-brainer, really.]]></description>
		<content:encoded><![CDATA[<p>LiveJournal already does this well. If you subscribe to an LJ feed, you get only the person&#8221;s public posts. But you can subscribe to a feed with <code>?auth=digest</code> added to the URL, which requires you to supply an LJ account and password as HTTP credentials. When you poll such a feed it will contains all the items you could see if you visited the associated journal while logged into the account whose details you&#8221;ve provided.</p>
<p>It&#8221;s a no-brainer, really.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BenJ</title>
		<link>http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38169</link>
		<dc:creator>BenJ</dc:creator>
		<pubDate>Thu, 29 Jun 2006 03:02:02 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38169</guid>
		<description><![CDATA[Another solution might be separate feeds (or the same feed, for that matter) that provide a notice of private activity, letting you click through to authenticate and see whatever it is. Not quite as nice as the actual content, but better than nothing.]]></description>
		<content:encoded><![CDATA[<p>Another solution might be separate feeds (or the same feed, for that matter) that provide a notice of private activity, letting you click through to authenticate and see whatever it is. Not quite as nice as the actual content, but better than nothing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Porter</title>
		<link>http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38155</link>
		<dc:creator>Porter</dc:creator>
		<pubDate>Wed, 28 Jun 2006 21:33:04 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38155</guid>
		<description><![CDATA[This has bothered me, too, but authentication is indeed the problem, as Dave points out. A possible solution would be to allow friends &amp; family to see a different RSS URL that contained an &quot;unguessable&quot; token, which is good enough security for posting photos via email (&lt;a href=&quot;http://www.flickr.com/photos/adactio/122923214/&quot; rel=&quot;nofollow&quot;&gt;unless you&#039;re Jeremy&lt;/a&gt;).

But of course, that doesn&#039;t address handling people who you revoke &quot;friendship&quot; for still being subscribed to your secret feed, so you&#039;d need a different token for each person that could be revoked if you changed their contact status...]]></description>
		<content:encoded><![CDATA[<p>This has bothered me, too, but authentication is indeed the problem, as Dave points out. A possible solution would be to allow friends &amp; family to see a different RSS URL that contained an &#8220;unguessable&#8221; token, which is good enough security for posting photos via email (<a href="http://www.flickr.com/photos/adactio/122923214/" rel="nofollow">unless you&#8217;re Jeremy</a>).</p>
<p>But of course, that doesn&#8217;t address handling people who you revoke &#8220;friendship&#8221; for still being subscribed to your secret feed, so you&#8217;d need a different token for each person that could be revoked if you changed their contact status&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edward</title>
		<link>http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38154</link>
		<dc:creator>Edward</dc:creator>
		<pubDate>Wed, 28 Jun 2006 21:29:37 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38154</guid>
		<description><![CDATA[As Dave has already said, RSS security isn&#039;t particularly, well, existent.  You can actually grab RSS feeds for anybody you want by checking out their ID in their Photostream feed and plugging that into the structure for the Recent Activity/Comments Made feed.

I&#039;ve actually appreciated that Flickr doesn&#039;t put those into the feeds.

Right on with the added tag thing, though.  That&#039;s something which would be nice to be able to keep a track of.]]></description>
		<content:encoded><![CDATA[<p>As Dave has already said, RSS security isn&#8217;t particularly, well, existent.  You can actually grab RSS feeds for anybody you want by checking out their ID in their Photostream feed and plugging that into the structure for the Recent Activity/Comments Made feed.</p>
<p>I&#8217;ve actually appreciated that Flickr doesn&#8217;t put those into the feeds.</p>
<p>Right on with the added tag thing, though.  That&#8217;s something which would be nice to be able to keep a track of.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave S.</title>
		<link>http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38150</link>
		<dc:creator>Dave S.</dc:creator>
		<pubDate>Wed, 28 Jun 2006 20:41:50 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2006/06/28/forgetful-flickr/#comment-38150</guid>
		<description><![CDATA[I don&#039;t know about you, but if I mark a photo friends or contacts only, I don&#039;t want the rest of the world to see it. On-site authentication prevents that from happening, but as far as I know, RSS security is still an oxymoron. 

Above and beyond HTTPS authentication -- which doesn&#039;t work universally amongst RSS readers -- the only other method of actually keeping a feed private is a unique, non-guessable URL. But that smacks of security through obscurity, and I&#039;m not inclined to trust private photos and comments to a method like that.

So, I agree with their current practice, at least in relation to RSS.]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t know about you, but if I mark a photo friends or contacts only, I don&#8217;t want the rest of the world to see it. On-site authentication prevents that from happening, but as far as I know, RSS security is still an oxymoron. </p>
<p>Above and beyond HTTPS authentication &#8212; which doesn&#8217;t work universally amongst RSS readers &#8212; the only other method of actually keeping a feed private is a unique, non-guessable URL. But that smacks of security through obscurity, and I&#8217;m not inclined to trust private photos and comments to a method like that.</p>
<p>So, I agree with their current practice, at least in relation to RSS.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->