<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php" />
  <link rel="self" type="application/atom+xml" href="http://www.readwriteweb.com/atom.xml" />
  <id>tag:www.readwriteweb.com,2011:/1/tag:www.readwriteweb.com,2009://1.13393-</id>
  <updated>2011-08-16T17:54:36Z</updated>
  <title>Comments for LifestreamBackup: Keeping a Copy of Your Posts, Tweets, Photos, and More</title>
  
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.35-en</generator>
  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13393</id>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.readwriteweb.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=13393" title="LifestreamBackup: Keeping a Copy of Your Posts, Tweets, Photos, and More" />
    <published>2009-01-16T08:45:59Z</published>
    <updated>2009-01-16T09:25:28Z</updated>
    <title>LifestreamBackup: Keeping a Copy of Your Posts, Tweets, Photos, and More</title>
    <summary>Anyone who has ever crashed a computer without a backup knows the painful and arduous process required to restore the machine to its previous state. As such, many of us keep regular backups of the data on our systems, just in case. But there&apos;s another vast set of data many of us are creating on...</summary>
    <author>
      <name>Rick Turoczy</name>
      
    </author>
    
    <category term="Lifestreaming" />
    
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
      <![CDATA[<p><img alt="Lifestream" src="http://www.readwriteweb.com/imgLifestream.jpg" width="150" height="200" />Anyone who has ever crashed a computer without a backup knows the painful and arduous process required to restore the machine to its previous state. As such, many of us keep regular backups of the data on our systems, just in case.  </p>

<p>But there's another vast set of data many of us are creating on a daily basis that has little to no backup at all - beyond the services that host that content: our lifestreams. Now, a new service - named appropriately enough, <a href="http://lifestreambackup.com/">LifestreamBackup</a> - aims to provide the peace of mind that your lifestream data will always be just as accessible as the backup of your machine.</p>]]>
      <![CDATA[<p>Is losing this data really a problem? If it's not now, it soon will be.</p>

<p>The most obvious example of this loss of access to lifestream data? The inability to access anything beyond <a href="http://twitter.com/rww?page=162">beyond page 162 on Twitter</a>. No matter how many times you've posted, you cannot go back any further than 3240 tweets. So, every new public message you send removes one from your history. (To see this in action, simply add "?page=162" to the end of any  Twitter user's default URL.) Those who had seen Twitter as a journal of sorts for recording fleeting moments for posterity, suddenly found those moments just as fleeting online. </p>

<p>That's just one example. There are thousands of others: blogs crashing, videos being taken down, <a href="http://www.readwriteweb.com/archives/google_giveth_and_it_taketh_away.php">companies shutting down services</a>. The list goes on and on.</p>

<p>The point being: saving the content you are producing elsewhere so that you always have access to it is going to become a bigger and bigger problem as time goes on - especially as more and more people move into the social Web. For that reason, LifestreamBackup seems to be ahead of the game with this proposed offering.</p>

<p>While not yet available, LifestreamBackup proposes to launch in the coming weeks. For a small fee, the service will take your various feeds and back them up on Amazon S3 - either your account or theirs. Current pricing is set at $6.95 per month for 10G of data.</p>

<blockquote>"We will launch with the ability to backup Flickr and a blog (via RSS feed). Google Docs, Twitter feeds, Youtube and Facebook backup are all in the works and will come shortly after launch. If it has an API that allows us to pull data, we are happy to back it up for you."
</blockquote>
The cloud provides a cost-effective resource for storage. Still, one has to wonder, given the concerns with availability, is saving to the cloud the best place to back things up? The cloud for all its benefits is <a href="http://www.readwriteweb.com/archives/dark_side_of_the_cloud.php">not a perfect place</a>. Apparently, the more cautious among us will still be pulling a backup of that backup - which we'll house offsite somewhere.

<p>For more, <a href="http://lifestreamblog.com/launch-of-the-first-lifestreaming-backup-service/">Lifestream Blog</a> points us to a video from "<a href="http://www.somewhatfrank.com/2009/01/nyc-breakfast-social-media-tech-talks.html">Somewhat Frank</a>" Gruber where a number of people - for the first few minutes - chat about the <a href="http://www.flixwagon.com/watch/1418001">pros and cons of the concept</a>.</p>

<p>Suffice it to say, it's a start. And, a step in the right direction. LifestreamBackup isn't likely to take the market by storm. But it's important to consider it, nonetheless, because it's definitely addressing a growing need. </p>

<p>We're still very early in this version of the Web. There's no doubt that saving the things that are important to us - our social interactions and our historical references - for future reference will become a very important business indeed.</p>

<p><em>(<a href="http://flickr.com/photos/jemsweb/13001105/in/photostream/">Image "Lifestream-Seaform" courtesy jemsweb</a>. Used under Creative Commons.)</em></p>]]>
    </content>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13393-comment:123458</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13393" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php#c123458" />
    <title>Comment from Rutger Blom on 2009-01-18</title>
    <author>
        <name>Rutger Blom</name>
        <uri>http://friendfeed.com/rutgerblom</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/rutgerblom">
        <![CDATA[<p>Backup via RSS? You can do that yourself. Either subscribe to several different lifestreaming services to create redundancy or subscribe to all your lifestreaming feeds with a RSS reader.</p>]]>
    </content>
    <published>2009-01-18T08:25:51Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13393-comment:123332</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13393" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php#c123332" />
    <title>Comment from juniorbonner on 2009-01-16</title>
    <author>
        <name>juniorbonner</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>what I do is subscribe to all my various feeds of information in something like soup or tumblr or you can create a folder in google reader and publish that - basically anything to amalgamate all the feeds in one feed, then I use a service that turns this feed into email, which I get sent to gmail and have a filter set up so it all just gets stored away.</p>]]>
    </content>
    <published>2009-01-16T22:33:41Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13393-comment:123280</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13393" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php#c123280" />
    <title>Comment from Strategic Blend on 2009-01-16</title>
    <author>
        <name>Strategic Blend</name>
        <uri>http://www.strategicblend.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.strategicblend.com">
        <![CDATA[<p>This is another solution...</p>

<p><a href="http://www.strategicblend.com/where-does-it-all-go-in-the-end/" rel="nofollow">http://www.strategicblend.com/where-does-it-all-go-in-the-end/</a></p>]]>
    </content>
    <published>2009-01-16T19:03:07Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13393-comment:123264</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13393" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php#c123264" />
    <title>Comment from Sanjeev on 2009-01-16</title>
    <author>
        <name>Sanjeev</name>
        <uri>http://www.clickonf5.org</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.clickonf5.org">
        <![CDATA[<p>Really great idea for the protection of the data on our blogs.<br />
I will try to do this ASAP.</p>

<p>Thanks a lot Rick for this informative article</p>]]>
    </content>
    <published>2009-01-16T17:32:25Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13393-comment:123243</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13393" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php#c123243" />
    <title>Comment from coldbrew on 2009-01-16</title>
    <author>
        <name>coldbrew</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Backup is interesting, not anything I'd pay for, but interesting. </p>

<p>Where is the ability to restore it though? </p>

<p>This is only half a solution because I can "backup" any RSS feed with my desktop feed reader, and taking backups of your blog installation is pretty simple (not sure about hosted).</p>

<p>The lack of any mention about what can be done with the backed-up data is mind boggling.</p>]]>
    </content>
    <published>2009-01-16T15:47:27Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13393-comment:123234</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13393" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php#c123234" />
    <title>Comment from Wendy Reynolds on 2009-01-16</title>
    <author>
        <name>Wendy Reynolds</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Do we *really* need to keep everything? I'd be hard-pressed to think of a single Tweet worthy of retention. What I'd like to see is a cloud archive, where you can select material from your own docs or those of others, which you can then stash away and search at need.</p>]]>
    </content>
    <published>2009-01-16T14:37:12Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13393-comment:123231</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13393" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php#c123231" />
    <title>Comment from eschnou on 2009-01-16</title>
    <author>
        <name>eschnou</name>
        <uri>http://eschnou.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://eschnou.com">
        <![CDATA[<p>If you want a free, but text only, backup. Check out <a href="http://storytlr.com," rel="nofollow">http://storytlr.com,</a> it enable you to download your data in CSV files (like you complete twitter history). Quite handy !</p>]]>
    </content>
    <published>2009-01-16T13:25:34Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13393-comment:123230</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13393" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php#c123230" />
    <title>Comment from Raj on 2009-01-16</title>
    <author>
        <name>Raj</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><br />
You cannot get a complete and thus accurate backup of a blog simply using an RSS feed.  It's just not possible because lots of important data are not present in the feed.  </p>

<p>One example ---- comments are not in the feed for the vast majority of platforms.  Wordpress has a comments feed, but even that data is not complete.  Blogger doesn't even display a date for comments.  </p>

<p>I looked at data portability for these types of applications extensively.  Certain revelations during this process actually led to my last startup.  I can tell you with certainty that a complete backup is not possible without a "Wordpress Agent" much like an "Exchange Agent."</p>]]>
    </content>
    <published>2009-01-16T13:09:31Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13393-comment:123218</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13393" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php#c123218" />
    <title>Comment from Ryan on 2009-01-16</title>
    <author>
        <name>Ryan</name>
        <uri>http://blogfwrd.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://blogfwrd.com">
        <![CDATA[<p>Basically, it is still backing-up on the cloud, just combining various stream to just one single cloud (S3).</p>

<p>What if you want to back-up your lifestream by downloading them to your own HDD? I guess it is still quite impossible to do so without going through lots of pain.</p>

<p>What if one day you are inaccessible to internet, but need those information?</p>]]>
    </content>
    <published>2009-01-16T09:37:14Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13393-comment:123217</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13393" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/lifestreambackup_keeping_a_copy.php#c123217" />
    <title>Comment from Rob Mowery on 2009-01-16</title>
    <author>
        <name>Rob Mowery</name>
        <uri>http://www.linkedin.com/in/rmowery</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.linkedin.com/in/rmowery">
        <![CDATA[<p>Definitely a smart idea in the wake of the economy and rate many companies have shutdown or shutdown services (AOL, GooG, etc).  </p>

<p>The part I think is beneficial and I wish other companies would follow is allowing me to back up to my own Amazon S3 storage area. This assures me that I have control of that and likewise if needed I can always copy down my bucket locally to backup. I hate when companies lock you into their own S3 slice, these folks are doing that right way by offering two options.</p>]]>
    </content>
    <published>2009-01-16T09:35:15Z</published>
  </entry>

</feed>
