<?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: Grrr</title>
	<atom:link href="http://4.flowsnake.org/archives/883/feed" rel="self" type="application/rss+xml" />
	<link>http://4.flowsnake.org/archives/883</link>
	<description>A Pythoneer's adventures with Scheme, Clojure and a whole lot more. ^_^</description>
	<lastBuildDate>Sat, 22 May 2010 22:09:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Ben Bangert</title>
		<link>http://4.flowsnake.org/archives/883/comment-page-1#comment-710</link>
		<dc:creator>Ben Bangert</dc:creator>
		<pubDate>Mon, 04 Jan 2010 20:43:06 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/?p=883#comment-710</guid>
		<description>Good offline solutions should always be available. One of the things that won me over to tumblr was this:
http://www.marco.org/277762675

For big blog posts, use an app, like Mars Edit, that keeps the whole thing local, then uses a web interface to publish the story. If it fails, no prob, just retry it later, no lost posts!

Hopefully with offline apps and such with HTML5, this will be less of an issue as your browser can save posts in progress locally and then sync back to the webapp.</description>
		<content:encoded><![CDATA[<p>Good offline solutions should always be available. One of the things that won me over to tumblr was this:<br />
<a href="http://www.marco.org/277762675" rel="nofollow">http://www.marco.org/277762675</a></p>
<p>For big blog posts, use an app, like Mars Edit, that keeps the whole thing local, then uses a web interface to publish the story. If it fails, no prob, just retry it later, no lost posts!</p>
<p>Hopefully with offline apps and such with HTML5, this will be less of an issue as your browser can save posts in progress locally and then sync back to the webapp.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
