<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Lifestream Blog - Latest Comments in Retooling Your Lifestreaming Services and Workflow</title><link>http://lifestreamblog.disqus.com/</link><description>Social data aggregation, lifelogging, quantified self and digital preservation.</description><atom:link href="https://lifestreamblog.disqus.com/retooling_your_lifestreaming_services_and_workflow_lifestream_blog/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 27 Jan 2009 13:56:54 -0000</lastBuildDate><item><title>Re: Retooling Your Lifestreaming Services and Workflow</title><link>http://lifestreamblog.com/retooling-your-lifestreaming-services-and-workflow/#comment-5598067</link><description>&lt;p&gt;I've currently got Tarpipe set up for two workflows: status and pictures.&lt;/p&gt;&lt;p&gt;Sending an email to my status Tarpipe updates Facebook, Twitter, and Friendfeed.&lt;/p&gt;&lt;p&gt;Sending an email to my picture Tarpipe sends the picture to Facebook, Flickr, and the flickr URL to Twitter&lt;/p&gt;&lt;p&gt;I LOVE being able to easily update my workflow and hope that Tarpipe becomes as usable as Yahoo Pipes someday!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">teejayhanton</dc:creator><pubDate>Tue, 27 Jan 2009 13:56:54 -0000</pubDate></item><item><title>Re: Retooling Your Lifestreaming Services and Workflow</title><link>http://lifestreamblog.com/retooling-your-lifestreaming-services-and-workflow/#comment-5071148</link><description>&lt;p&gt;Ahhhh agnostic federation of activity streams? A subject near and dear to my heart!&lt;/p&gt;&lt;p&gt;Consider participating on the DiSo Activity Stream Google Group:&lt;/p&gt;&lt;p&gt;&lt;a href="http://groups.google.com/group/activity-streams" rel="nofollow noopener" target="_blank" title="http://groups.google.com/group/activity-streams"&gt;http://groups.google.com/gr...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;And if you have the time, please review, comment, criticize my concept to map activity stream control to any phone or MID's D-pad:&lt;/p&gt;&lt;p&gt;&lt;a href="http://www.flickr.com/photos/ronin691/3132754199/" rel="nofollow noopener" target="_blank" title="http://www.flickr.com/photos/ronin691/3132754199/"&gt;http://www.flickr.com/photo...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Great post!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Todd</dc:creator><pubDate>Mon, 12 Jan 2009 07:21:05 -0000</pubDate></item><item><title>Re: Retooling Your Lifestreaming Services and Workflow</title><link>http://lifestreamblog.com/retooling-your-lifestreaming-services-and-workflow/#comment-5069601</link><description>&lt;p&gt;Thanks Nathan. Great tip. I really think someone needs to create a detailed post creating a huge list of methods and hacks for cross posting data among multiple services. This seems to a be quite the wildwest and I'm sure there are some more good tips out there that need to get aggregated in a single place.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Krynsky</dc:creator><pubDate>Mon, 12 Jan 2009 02:44:10 -0000</pubDate></item><item><title>Re: Retooling Your Lifestreaming Services and Workflow</title><link>http://lifestreamblog.com/retooling-your-lifestreaming-services-and-workflow/#comment-5069178</link><description>&lt;p&gt;Another easy, do-it-yourself solution for piping Flickr photos to Twitter is to designate a tag (say, "post:twitter") for photos intended for Twitter, grab the feed for that tag, and run it through Twitterfeed. You can then send a photo to Flickr via MMS and include the text "tags:post:twitter" and it will be cross-posted within a half hour or so. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Nathan</dc:creator><pubDate>Mon, 12 Jan 2009 01:43:27 -0000</pubDate></item><item><title>Re: Retooling Your Lifestreaming Services and Workflow</title><link>http://lifestreamblog.com/retooling-your-lifestreaming-services-and-workflow/#comment-5069131</link><description>&lt;p&gt;I agree Bob. These services aren't there yet. Logic to do this can definitely get a bit complicated but I'm sure we'll see improvements in this area in the coming year.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Krynsky</dc:creator><pubDate>Mon, 12 Jan 2009 01:36:30 -0000</pubDate></item><item><title>Re: Retooling Your Lifestreaming Services and Workflow</title><link>http://lifestreamblog.com/retooling-your-lifestreaming-services-and-workflow/#comment-5069108</link><description>&lt;p&gt;I also talked to another friend who has started to use posterous as a method of using his mobile phone to post pictures on Facebook and Flickr. I haven't tried it but it seems like it might be worth checking out.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Krynsky</dc:creator><pubDate>Mon, 12 Jan 2009 01:36:11 -0000</pubDate></item><item><title>Re: Retooling Your Lifestreaming Services and Workflow</title><link>http://lifestreamblog.com/retooling-your-lifestreaming-services-and-workflow/#comment-5048919</link><description>&lt;p&gt;I have never tried twitpic but my brother got me interested in &lt;a href="http://posterous.com" rel="nofollow noopener" target="_blank" title="posterous.com"&gt;posterous.com&lt;/a&gt; lately. I have been enjoying using that and the way it integrates into twitter. But I deliberately decided to keep it separate from flickr because I don't like mixing the iPhone photographs in my regular photostream. &lt;a href="http://michaelkpate.posterous.com/" rel="nofollow noopener" target="_blank" title="http://michaelkpate.posterous.com/"&gt;http://michaelkpate.postero...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael K Pate</dc:creator><pubDate>Sat, 10 Jan 2009 17:46:28 -0000</pubDate></item><item><title>Re: Retooling Your Lifestreaming Services and Workflow</title><link>http://lifestreamblog.com/retooling-your-lifestreaming-services-and-workflow/#comment-4994953</link><description>&lt;p&gt;The problem with Tarpipe or other services that sync or do even more than sync is that they all have a limited repertoire of sites they can work with. Tarpipe has 11. Others are up to 50, but that still is an inadequate arrangement. I use lots of services on the web, but few of them are among the 11 or 50. What is required before this is really going to work is another 'layer' of standards so that I can tell the program where I want it to deposit 'stuff' and it will go and easily find out how to do it. Until then we will all be limping along with inadequate services.&lt;/p&gt;&lt;p&gt;Notwithstanding -- reorganizing one lifestreaming seems like a good idea every year. &lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bobboynton</dc:creator><pubDate>Thu, 08 Jan 2009 15:30:21 -0000</pubDate></item></channel></rss>