<?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/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Post.ly (The New Face of Posterous?)</title>
	<atom:link href="http://churchm.ag/post-ly-the-new-face-of-posterous/feed/" rel="self" type="application/rss+xml" />
	<link>http://churchm.ag/post-ly-the-new-face-of-posterous/</link>
	<description>Exploring the Intersection of Church and Technology</description>
	<lastBuildDate>Thu, 09 Feb 2012 22:32:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Trent</title>
		<link>http://churchm.ag/post-ly-the-new-face-of-posterous/#comment-35913</link>
		<dc:creator>Trent</dc:creator>
		<pubDate>Wed, 24 Feb 2010 15:24:59 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=7431#comment-35913</guid>
		<description>I’m real interested in finding out what the size limits are. Up until now, I have had problems sending in some videos to posterous because those videos that I recorded wound up bigger than my email server would allow as an attachment. Now, I’ll be trying post.ly whenever gmail won’t allow my attachments due to size. However, without any info about the upload limitations, I may be stuck anyway.

Lets hope they allow at least 35 MB or more. That would be awesome.</description>
		<content:encoded><![CDATA[<p>I’m real interested in finding out what the size limits are. Up until now, I have had problems sending in some videos to posterous because those videos that I recorded wound up bigger than my email server would allow as an attachment. Now, I’ll be trying post.ly whenever gmail won’t allow my attachments due to size. However, without any info about the upload limitations, I may be stuck anyway.</p>
<p>Lets hope they allow at least 35 MB or more. That would be awesome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://churchm.ag/post-ly-the-new-face-of-posterous/#comment-35912</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sat, 23 Jan 2010 01:55:47 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=7431#comment-35912</guid>
		<description>Sweet, I checked out the article. I dig seeing how people leverage technology like this as a means to their end. 
 
Good stuff. </description>
		<content:encoded><![CDATA[<p>Sweet, I checked out the article. I dig seeing how people leverage technology like this as a means to their end. </p>
<p>Good stuff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://churchm.ag/post-ly-the-new-face-of-posterous/#comment-35911</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sat, 23 Jan 2010 01:54:53 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=7431#comment-35911</guid>
		<description>Big fan of bit.ly. It&#039;s definitely helped me get a clearer picture of what works best when trying to drive traffic to a site from various networks. 
 
When I care about statistics, I use it. When I care about sharing random things I stumble across on the web but don&#039;t care much about things beyond the number of visits, I roll with Posterous. </description>
		<content:encoded><![CDATA[<p>Big fan of bit.ly. It&#039;s definitely helped me get a clearer picture of what works best when trying to drive traffic to a site from various networks. </p>
<p>When I care about statistics, I use it. When I care about sharing random things I stumble across on the web but don&#039;t care much about things beyond the number of visits, I roll with Posterous.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://churchm.ag/post-ly-the-new-face-of-posterous/#comment-35910</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sat, 23 Jan 2010 01:53:27 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=7431#comment-35910</guid>
		<description>I remember when Tumblr first hit the scene. It was pretty slick.  
 
Thing about Posterous and Tumblr, to me, is their approach. Tumblr seeks to bring everything into it where as Posterous seeks to push everything out from it. </description>
		<content:encoded><![CDATA[<p>I remember when Tumblr first hit the scene. It was pretty slick.  </p>
<p>Thing about Posterous and Tumblr, to me, is their approach. Tumblr seeks to bring everything into it where as Posterous seeks to push everything out from it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Lombardi</title>
		<link>http://churchm.ag/post-ly-the-new-face-of-posterous/#comment-35906</link>
		<dc:creator>Rob Lombardi</dc:creator>
		<pubDate>Fri, 22 Jan 2010 22:41:47 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=7431#comment-35906</guid>
		<description>I&#039;ve been using bit.ly and like the addition of the statistics reporting. Their bookmarklet is very straightforward and can post to Facebook and Twitter. If I combined the two, I would get a bit.ly link from the bookmarklet, copy it into an email and send to posterous@posterous.com. I&#039;ll have to try that out. </description>
		<content:encoded><![CDATA[<p>I&#39;ve been using bit.ly and like the addition of the statistics reporting. Their bookmarklet is very straightforward and can post to Facebook and Twitter. If I combined the two, I would get a bit.ly link from the bookmarklet, copy it into an email and send to <a href="mailto:posterous@posterous.com">posterous@posterous.com</a>. I&#39;ll have to try that out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://churchm.ag/post-ly-the-new-face-of-posterous/#comment-35904</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 22 Jan 2010 20:52:45 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=7431#comment-35904</guid>
		<description>Alright, so it took a long time for my first comment to show up, hence the double post. Ah, well. </description>
		<content:encoded><![CDATA[<p>Alright, so it took a long time for my first comment to show up, hence the double post. Ah, well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://churchm.ag/post-ly-the-new-face-of-posterous/#comment-35905</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 22 Jan 2010 20:52:16 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=7431#comment-35905</guid>
		<description>You&#039;re right. The post-via-web face has been around, but it&#039;s definitely been clunky to use. One of the main things that attracted me to Posterous was the fact that my email client was the interface to the service. 
 
And don&#039;t get me wrong, I&#039;m all for Posterous and assimilating it to the masses. I personally have no problem with the web interface - I&#039;m more interested in hearing what others feel about it (hence the article) ;) </description>
		<content:encoded><![CDATA[<p>You&#039;re right. The post-via-web face has been around, but it&#039;s definitely been clunky to use. One of the main things that attracted me to Posterous was the fact that my email client was the interface to the service. </p>
<p>And don&#039;t get me wrong, I&#039;m all for Posterous and assimilating it to the masses. I personally have no problem with the web interface &#8211; I&#039;m more interested in hearing what others feel about it (hence the article) <img src='http://cdn.churchm.ag/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://churchm.ag/post-ly-the-new-face-of-posterous/#comment-35902</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 22 Jan 2010 18:48:45 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=7431#comment-35902</guid>
		<description>What kind of podcast do you run? 
 
I&#039;m usually all for the web interface, but the size limit can definitely be a hindrance when dealing with large media. I don&#039;t publish that much stuff to my Posterous account so that&#039;s not really a problem I deal with. 
 
Anyway, I do agree - they&#039;re just adding appeal to a wider audience - I&#039;m just interested in seeing what the rest of all you Posterous-publishin&#039;-people think. </description>
		<content:encoded><![CDATA[<p>What kind of podcast do you run? </p>
<p>I&#039;m usually all for the web interface, but the size limit can definitely be a hindrance when dealing with large media. I don&#039;t publish that much stuff to my Posterous account so that&#039;s not really a problem I deal with. </p>
<p>Anyway, I do agree &#8211; they&#039;re just adding appeal to a wider audience &#8211; I&#039;m just interested in seeing what the rest of all you Posterous-publishin&#039;-people think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://churchm.ag/post-ly-the-new-face-of-posterous/#comment-35901</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 22 Jan 2010 18:46:26 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=7431#comment-35901</guid>
		<description>True on the web interface. It was so buried within the admin area that it seemed to be less than usable. 
 
I personally am a big fan of the email interface just because, say I stumble across something or have a thought to offer on some music I&#039;m listening to, it&#039;s easy to shoot off a quick email and update Twitter (and occasionally Facebook) without having to launch a new browser tab, login, and construct the post. 
 
I think the point is definitely to target a wider range of people. And don&#039;t get me wrong, I dig Posterous - I&#039;m all for it.  </description>
		<content:encoded><![CDATA[<p>True on the web interface. It was so buried within the admin area that it seemed to be less than usable. </p>
<p>I personally am a big fan of the email interface just because, say I stumble across something or have a thought to offer on some music I&#039;m listening to, it&#039;s easy to shoot off a quick email and update Twitter (and occasionally Facebook) without having to launch a new browser tab, login, and construct the post. </p>
<p>I think the point is definitely to target a wider range of people. And don&#039;t get me wrong, I dig Posterous &#8211; I&#039;m all for it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: @gregdavispsu</title>
		<link>http://churchm.ag/post-ly-the-new-face-of-posterous/#comment-35909</link>
		<dc:creator>@gregdavispsu</dc:creator>
		<pubDate>Fri, 22 Jan 2010 18:11:21 +0000</pubDate>
		<guid isPermaLink="false">http://churchcrunch.com/?p=7431#comment-35909</guid>
		<description>Worth noting is the ability to have Posterous not only update Twitter and Facebook, you can also have it autopost to your WordPress blog.  There is a setting you have to enable on the WP side but it works very well!  </description>
		<content:encoded><![CDATA[<p>Worth noting is the ability to have Posterous not only update Twitter and Facebook, you can also have it autopost to your WordPress blog.  There is a setting you have to enable on the WP side but it works very well!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using memcached (Feed is rejected)
Page Caching using memcached
Database Caching 1/5 queries in 0.002 seconds using memcached
Object Caching 471/475 objects using memcached
Content Delivery Network via cdn.churchm.ag

Served from: churchm.ag @ 2012-02-09 18:39:48 -->
