<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.9" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments for PubForge Blog</title>
	<link>http://pubforge.org/pubblog</link>
	<description>Talking about open source collaboration for public broadcasting</description>
	<pubDate>Tue,  9 Mar 2010 23:42:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.9</generator>

	<item>
		<title>Comment on How-to: track behavior of &#8220;loyal&#8221; visitors in Google Analytics by josephsheppa</title>
		<link>http://pubforge.org/pubblog/2009/06/22/how-to-track-behavior-of-loyal-visitors-in-google-analytics/#comment-74</link>
		<pubDate>Tue, 23 Jun 2009 17:03:24 +0000</pubDate>
		<guid>http://pubforge.org/pubblog/2009/06/22/how-to-track-behavior-of-loyal-visitors-in-google-analytics/#comment-74</guid>
					<description>Dale,

This is great, thanks for posting. In just a few minutes of comparison, I've found some relevant info for our radio site.</description>
		<content:encoded><![CDATA[<p>Dale,</p>
<p>This is great, thanks for posting. In just a few minutes of comparison, I&#8217;ve found some relevant info for our radio site.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on How-to: track behavior of &#8220;loyal&#8221; visitors in Google Analytics by PubForge Blog » How-to: track behavior of “loyal” visitors in &#8230; &#124; Dale</title>
		<link>http://pubforge.org/pubblog/2009/06/22/how-to-track-behavior-of-loyal-visitors-in-google-analytics/#comment-73</link>
		<pubDate>Tue, 23 Jun 2009 00:28:33 +0000</pubDate>
		<guid>http://pubforge.org/pubblog/2009/06/22/how-to-track-behavior-of-loyal-visitors-in-google-analytics/#comment-73</guid>
					<description>[...] The rest is here:  http://pubforge.org/pubblog/2009/06/22/how-to-track-behavior-of-loyal-visitors-in-google-analytics/ [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] The rest is here:  <a href="http://pubforge.org/pubblog/2009/06/22/how-to-track-behavior-of-loyal-visitors-in-google-analytics/" rel="nofollow">http://pubforge.org/pubblog/2009/06/22/how-to-track-behavior-of-loyal-visitors-in-google-analytics/</a> [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Mashups and Related-Info Sidebars by John McMellen</title>
		<link>http://pubforge.org/pubblog/2009/05/13/mashups-and-related-info-sidebars/#comment-60</link>
		<pubDate>Mon, 18 May 2009 22:11:37 +0000</pubDate>
		<guid>http://pubforge.org/pubblog/2009/05/13/mashups-and-related-info-sidebars/#comment-60</guid>
					<description>API's are becoming a great tool in their own right. I'm glad people are posting about API's they are using and for what purpose. BTW, there is a pretty good API directory at http://www.programmableweb.com/apis/directory</description>
		<content:encoded><![CDATA[<p>API&#8217;s are becoming a great tool in their own right. I&#8217;m glad people are posting about API&#8217;s they are using and for what purpose. BTW, there is a pretty good API directory at <a href="http://www.programmableweb.com/apis/directory" rel="nofollow">http://www.programmableweb.com/apis/directory</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on How to: Use Twitter as part of the public media toolbox by John McMellen</title>
		<link>http://pubforge.org/pubblog/2009/04/10/how-to-use-twitter-as-part-of-the-public-media-toolbox/#comment-56</link>
		<pubDate>Sat, 11 Apr 2009 20:15:55 +0000</pubDate>
		<guid>http://pubforge.org/pubblog/2009/04/10/how-to-use-twitter-as-part-of-the-public-media-toolbox/#comment-56</guid>
					<description>Those are some terrific uses, Dale. I would like to add some additional info based on our usage.
1. We added an additional function to our Twitter usage for pledge drive. On the exit page for our web donation form, we provided a link that set the donor's Twitter status to: "I supported public radio on @ksmu and you should too! http://ksmu.org/pledge". This is super easy to do with Twitter's API (much harder with Facebook), it's just passing that text on an http request which forwards to the donor's Twitter page and lets them hit the send button. There were several people who used that link, hopefully influencing their friends to contribute as well. I also fed a Twitter search for those posts into a Yahoo pipe and put it on our test front page as a widget, but I didn't put it in production for this pledge drive.
2. We are also feeding our RSS feeds into our Twitter accounts, which is probably the most simple, straightforward and sensible way to get a foothold in the Twitter space. I switched us from Twitterfeed to Hootsuite because Hootsuite offers some more user management features, but more importantly, displays statistics for how many people click through to read the story in an RSS-originated tweet.</description>
		<content:encoded><![CDATA[<p>Those are some terrific uses, Dale. I would like to add some additional info based on our usage.<br />
1. We added an additional function to our Twitter usage for pledge drive. On the exit page for our web donation form, we provided a link that set the donor&#8217;s Twitter status to: &#8220;I supported public radio on @ksmu and you should too! <a href="http://ksmu.org/pledge&#8221;." rel="nofollow">http://ksmu.org/pledge&#8221;.</a> This is super easy to do with Twitter&#8217;s API (much harder with Facebook), it&#8217;s just passing that text on an http request which forwards to the donor&#8217;s Twitter page and lets them hit the send button. There were several people who used that link, hopefully influencing their friends to contribute as well. I also fed a Twitter search for those posts into a Yahoo pipe and put it on our test front page as a widget, but I didn&#8217;t put it in production for this pledge drive.<br />
2. We are also feeding our RSS feeds into our Twitter accounts, which is probably the most simple, straightforward and sensible way to get a foothold in the Twitter space. I switched us from Twitterfeed to Hootsuite because Hootsuite offers some more user management features, but more importantly, displays statistics for how many people click through to read the story in an RSS-originated tweet.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on What I learned from IMA09 by Jack Brighton</title>
		<link>http://pubforge.org/pubblog/2009/02/23/what-i-learned-from-ima09/#comment-50</link>
		<pubDate>Thu, 26 Feb 2009 20:55:32 +0000</pubDate>
		<guid>http://pubforge.org/pubblog/2009/02/23/what-i-learned-from-ima09/#comment-50</guid>
					<description>Regarding use of social media: What I took away was a keener sense of how important it's becoming to our core demographics, and not just the younger folks we want to reach but can't seem to.  Facebook adoption rate among the 25 to 54 demo is exploding.  And I didn't seem to have a use for Twitter, but suddenly I do.

In contrast to John's comment about if staff don't dig using Facebook or Twitter find something else, I'm feeling like these tools and 
"places" are becoming critical to our connections with audiences and communities.  In other words, whether we like it or not, we better be there.  And we're starting to see some really great ways to use Twitter for actual journalism and reporting.  I suspect it will be hard for me to convince my new reporters to begin tweeting, but I think I have to try.  To John's last point above: that's exactly right!

Another thing I took away from the IMA is the conviction that the public media community is ready for something like PubForge.  So let's get busy and make it Truly Useful!</description>
		<content:encoded><![CDATA[<p>Regarding use of social media: What I took away was a keener sense of how important it&#8217;s becoming to our core demographics, and not just the younger folks we want to reach but can&#8217;t seem to.  Facebook adoption rate among the 25 to 54 demo is exploding.  And I didn&#8217;t seem to have a use for Twitter, but suddenly I do.</p>
<p>In contrast to John&#8217;s comment about if staff don&#8217;t dig using Facebook or Twitter find something else, I&#8217;m feeling like these tools and<br />
&#8220;places&#8221; are becoming critical to our connections with audiences and communities.  In other words, whether we like it or not, we better be there.  And we&#8217;re starting to see some really great ways to use Twitter for actual journalism and reporting.  I suspect it will be hard for me to convince my new reporters to begin tweeting, but I think I have to try.  To John&#8217;s last point above: that&#8217;s exactly right!</p>
<p>Another thing I took away from the IMA is the conviction that the public media community is ready for something like PubForge.  So let&#8217;s get busy and make it Truly Useful!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on What I learned from IMA09 by John McMellen</title>
		<link>http://pubforge.org/pubblog/2009/02/23/what-i-learned-from-ima09/#comment-49</link>
		<pubDate>Mon, 23 Feb 2009 19:56:18 +0000</pubDate>
		<guid>http://pubforge.org/pubblog/2009/02/23/what-i-learned-from-ima09/#comment-49</guid>
					<description>A few things that stood out to me:

Don't be afraid to experiment, but set realistic expectations.

If your staff don't enjoy using a new tool like Twitter or Facebook, it might be better to look for something else. It should be fun.

Take advantage of the free platforms that are available. Our audience already is.</description>
		<content:encoded><![CDATA[<p>A few things that stood out to me:</p>
<p>Don&#8217;t be afraid to experiment, but set realistic expectations.</p>
<p>If your staff don&#8217;t enjoy using a new tool like Twitter or Facebook, it might be better to look for something else. It should be fun.</p>
<p>Take advantage of the free platforms that are available. Our audience already is.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on PubMedia CMS feature request by Milan Andric</title>
		<link>http://pubforge.org/pubblog/2008/09/24/pubmedia-cms-feature-request/#comment-45</link>
		<pubDate>Mon, 08 Dec 2008 18:58:40 +0000</pubDate>
		<guid>http://pubforge.org/pubblog/2008/09/24/pubmedia-cms-feature-request/#comment-45</guid>
					<description>Apologies, meant to address Jack not John.</description>
		<content:encoded><![CDATA[<p>Apologies, meant to address Jack not John.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on PubMedia CMS feature request by mandric</title>
		<link>http://pubforge.org/pubblog/2008/09/24/pubmedia-cms-feature-request/#comment-44</link>
		<pubDate>Mon, 08 Dec 2008 18:47:38 +0000</pubDate>
		<guid>http://pubforge.org/pubblog/2008/09/24/pubmedia-cms-feature-request/#comment-44</guid>
					<description>Hey John, though I am not using Drupal, these specs and needs are right on with our open source project Django Newsroom.  I'd love to help flush these details out and invent the wheel so others don't have to.</description>
		<content:encoded><![CDATA[<p>Hey John, though I am not using Drupal, these specs and needs are right on with our open source project Django Newsroom.  I&#8217;d love to help flush these details out and invent the wheel so others don&#8217;t have to.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Shades of Creative Comons Licenses for Public Broadcasting Content by Jack Brighton</title>
		<link>http://pubforge.org/pubblog/2008/12/04/shades-of-creative-comons-licenses-for-public-broadcasting-content/#comment-41</link>
		<pubDate>Sat, 06 Dec 2008 19:55:36 +0000</pubDate>
		<guid>http://pubforge.org/pubblog/2008/12/04/shades-of-creative-comons-licenses-for-public-broadcasting-content/#comment-41</guid>
					<description>I'd like to add the following use-case scenario:

A user in the distant future uses your work to help make sense of a complex issue, by combining it with the works of others in an interface or production that provides a deeper and broader view.  This then informs and inspires a larger public in a way that was otherwise not possible.</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to add the following use-case scenario:</p>
<p>A user in the distant future uses your work to help make sense of a complex issue, by combining it with the works of others in an interface or production that provides a deeper and broader view.  This then informs and inspires a larger public in a way that was otherwise not possible.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Survey Results and Sustainability by josephsheppa</title>
		<link>http://pubforge.org/pubblog/2008/09/14/survey-results-and-sustainability/#comment-37</link>
		<pubDate>Mon, 15 Sep 2008 18:50:52 +0000</pubDate>
		<guid>http://pubforge.org/pubblog/2008/09/14/survey-results-and-sustainability/#comment-37</guid>
					<description>Bill's comments are a fair assessment of the online public media situation.

However, I believe that in addition to investing ourselves totally in our online properties, we must also be willing to invest ourselves in public media online as a whole. There are a few knowledge bases out there, and the occasional webinar, but a true collaboration in web design, structure, and technology is yet to be had.

I'd like to see more code sharing. Or random tips. Or just a note about a site that has some cool JavaScript widgets that are fairly easy to implement. Taking a few small steps will get you to the top of that staircase - not quickly, but eventually.</description>
		<content:encoded><![CDATA[<p>Bill&#8217;s comments are a fair assessment of the online public media situation.</p>
<p>However, I believe that in addition to investing ourselves totally in our online properties, we must also be willing to invest ourselves in public media online as a whole. There are a few knowledge bases out there, and the occasional webinar, but a true collaboration in web design, structure, and technology is yet to be had.</p>
<p>I&#8217;d like to see more code sharing. Or random tips. Or just a note about a site that has some cool JavaScript widgets that are fairly easy to implement. Taking a few small steps will get you to the top of that staircase - not quickly, but eventually.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
