<?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: Personal publishing via web services</title>
	<atom:link href="http://www.the-haystack.com/2008/05/01/personal-publishing-via-web-services/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.the-haystack.com/2008/05/01/personal-publishing-via-web-services/</link>
	<description>Web, design, and web design</description>
	<pubDate>Thu, 21 Aug 2008 17:29:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Denna Jones</title>
		<link>http://www.the-haystack.com/2008/05/01/personal-publishing-via-web-services/#comment-66266</link>
		<dc:creator>Denna Jones</dc:creator>
		<pubDate>Sun, 06 Jul 2008 12:35:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.the-haystack.com/2008/05/01/personal-publishing-via-web-services/#comment-66266</guid>
		<description>I don't know about the mechanics of web design to comment on specifics, I can only comment on my experience with web designers and dennajones.com. Jon and Jon were my third web designers. The previous two were just unable (unwilling?) to create a site that allowed me any freedom. The latter of the two created the site but all fresh content had to go through him. Once my site was created, I was off his radar. I had to beg to get content upload. It was a horrible experience. I have nothing but praise for Jon and Jon's design for my site. Yes, I have to rely on other sites, but its' a "risk" worth taking. So far, so good. The site is as fresh as I make it. Since the site launched I've been consistent with flickr, and infrequent with the others. I plan to improve my uploads (ie Tumblr), but in the meantime, the site freels fresh to me because I am methodical about the masthead images, and ensure that they link to current work. As far as I'm concerned, Jon and Jon are creative and management geniuses.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know about the mechanics of web design to comment on specifics, I can only comment on my experience with web designers and dennajones.com. Jon and Jon were my third web designers. The previous two were just unable (unwilling?) to create a site that allowed me any freedom. The latter of the two created the site but all fresh content had to go through him. Once my site was created, I was off his radar. I had to beg to get content upload. It was a horrible experience. I have nothing but praise for Jon and Jon&#8217;s design for my site. Yes, I have to rely on other sites, but its&#8217; a &#8220;risk&#8221; worth taking. So far, so good. The site is as fresh as I make it. Since the site launched I&#8217;ve been consistent with flickr, and infrequent with the others. I plan to improve my uploads (ie Tumblr), but in the meantime, the site freels fresh to me because I am methodical about the masthead images, and ensure that they link to current work. As far as I&#8217;m concerned, Jon and Jon are creative and management geniuses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sint</title>
		<link>http://www.the-haystack.com/2008/05/01/personal-publishing-via-web-services/#comment-60594</link>
		<dc:creator>Sint</dc:creator>
		<pubDate>Wed, 11 Jun 2008 13:34:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.the-haystack.com/2008/05/01/personal-publishing-via-web-services/#comment-60594</guid>
		<description>Unfortunately dennajones.com seems to be down at the moment so I cannot comment on that website, but I agree that what Jeremy Keith has done is pretty cool.

While these kind of services are indeed some kind of extra, some people tend to publish a lot of content on them and they therefore tell lots about who we are and what we are doing. Having all those applications at different sites makes it hard to be followed or follow other people's whereabouts, especially when these applications should meet each other.

Online identiy aggregation will get more important than it is now. And when you are hosting the aggregation platform yourself, you don't need to worry about privacy...</description>
		<content:encoded><![CDATA[<p>Unfortunately dennajones.com seems to be down at the moment so I cannot comment on that website, but I agree that what Jeremy Keith has done is pretty cool.</p>
<p>While these kind of services are indeed some kind of extra, some people tend to publish a lot of content on them and they therefore tell lots about who we are and what we are doing. Having all those applications at different sites makes it hard to be followed or follow other people&#8217;s whereabouts, especially when these applications should meet each other.</p>
<p>Online identiy aggregation will get more important than it is now. And when you are hosting the aggregation platform yourself, you don&#8217;t need to worry about privacy&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Tan</title>
		<link>http://www.the-haystack.com/2008/05/01/personal-publishing-via-web-services/#comment-51225</link>
		<dc:creator>Jon Tan</dc:creator>
		<pubDate>Fri, 02 May 2008 08:18:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.the-haystack.com/2008/05/01/personal-publishing-via-web-services/#comment-51225</guid>
		<description>Hi Stephen. Yours is a good analysis. I too am a fan of Jeremy's approach, &lt;a href="http://jontangerine.com/about/aside" rel="nofollow"&gt;as you can see&lt;/a&gt;, but you're right to say there are potential issues with Denna's model that require careful handling: Storing and caching the API output is essential to mitigate any web service burps. It serves two purposes: If the service is cancelled or declines the data can be switched to another service easily, therefore removing any risk. Denna also has an historical archive of her output that she controls and owns. Of course, the model only works if it's a natural fit with the behaviour of the author. In Denna's case it was. Glad you liked it, thanks for the comment.</description>
		<content:encoded><![CDATA[<p>Hi Stephen. Yours is a good analysis. I too am a fan of Jeremy&#8217;s approach, <a href="http://jontangerine.com/about/aside" rel="nofollow">as you can see</a>, but you&#8217;re right to say there are potential issues with Denna&#8217;s model that require careful handling: Storing and caching the API output is essential to mitigate any web service burps. It serves two purposes: If the service is cancelled or declines the data can be switched to another service easily, therefore removing any risk. Denna also has an historical archive of her output that she controls and owns. Of course, the model only works if it&#8217;s a natural fit with the behaviour of the author. In Denna&#8217;s case it was. Glad you liked it, thanks for the comment.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
