<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Convio and Kintera open their APIs but befuddles coders</title>
	<atom:link href="http://www.nonprofittechblog.org/convio-and-kintera-open-their-apis-but-befuddles-coders/feed" rel="self" type="application/rss+xml" />
	<link>http://www.nonprofittechblog.org/convio-and-kintera-open-their-apis-but-befuddles-coders</link>
	<description>Confessions of a Non-Profit Executive Director</description>
	<lastBuildDate>Sat, 13 Mar 2010 11:46:18 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Allan Benamer</title>
		<link>http://www.nonprofittechblog.org/convio-and-kintera-open-their-apis-but-befuddles-coders/comment-page-1#comment-60953</link>
		<dc:creator>Allan Benamer</dc:creator>
		<pubDate>Thu, 25 Oct 2007 02:09:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/convio-and-kintera-open-their-apis-but-befuddles-coders#comment-60953</guid>
		<description>Agreed, maybe the Convio progress bar tool would be more useful. Like a typical programmer, I always want to goldplate the solution and produce something more slick. 

I&#039;ve tried to get into the program myself. I&#039;m not cool enough I guess. It&#039;s a bit like being picked last for a team isn&#039;t it? What am I, chopped liver? :(</description>
		<content:encoded><![CDATA[<p>Agreed, maybe the Convio progress bar tool would be more useful. Like a typical programmer, I always want to goldplate the solution and produce something more slick. </p>
<p>I&#8217;ve tried to get into the program myself. I&#8217;m not cool enough I guess. It&#8217;s a bit like being picked last for a team isn&#8217;t it? What am I, chopped liver? <img src='http://www.nonprofittechblog.org/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kim Ethridge</title>
		<link>http://www.nonprofittechblog.org/convio-and-kintera-open-their-apis-but-befuddles-coders/comment-page-1#comment-60886</link>
		<dc:creator>Kim Ethridge</dc:creator>
		<pubDate>Thu, 25 Oct 2007 00:56:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/convio-and-kintera-open-their-apis-but-befuddles-coders#comment-60886</guid>
		<description>&quot;In other words, you can build a progress bar widget with Kintera&#039;s &quot;query&quot; method but it would be very difficult to do the same thing with Convio&#039;s API. In order to sum up a campaign&#039;s pledge total, you&#039;d have to have as many getuser calls as you have users. This is simply impractical for larger databases that may have thousands of users.&quot;

Convio already provides Convio clients with a progress bar tool that sums up campaign totals.

Convio has about 150 &quot;approved&quot; (for lack of a better word) vendors. You&#039;re right, it&#039;s ashame the rest of you folks can&#039;t get equal access to the &quot;open&quot; api.</description>
		<content:encoded><![CDATA[<p>&#8220;In other words, you can build a progress bar widget with Kintera&#8217;s &#8220;query&#8221; method but it would be very difficult to do the same thing with Convio&#8217;s API. In order to sum up a campaign&#8217;s pledge total, you&#8217;d have to have as many getuser calls as you have users. This is simply impractical for larger databases that may have thousands of users.&#8221;</p>
<p>Convio already provides Convio clients with a progress bar tool that sums up campaign totals.</p>
<p>Convio has about 150 &#8220;approved&#8221; (for lack of a better word) vendors. You&#8217;re right, it&#8217;s ashame the rest of you folks can&#8217;t get equal access to the &#8220;open&#8221; api.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allan Benamer</title>
		<link>http://www.nonprofittechblog.org/convio-and-kintera-open-their-apis-but-befuddles-coders/comment-page-1#comment-57977</link>
		<dc:creator>Allan Benamer</dc:creator>
		<pubDate>Fri, 19 Oct 2007 15:03:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/convio-and-kintera-open-their-apis-but-befuddles-coders#comment-57977</guid>
		<description>@Peter Gulka: Blackbaud going open on the 7x product seems to me to be unlikely but now that they&#039;re literally the last major nonprofit CRM vendor out there without an open API, the pressure is on.

@Doug Yeager: Thanks Doug for your kind comment. Kintera and Convio are not in market leader positions so they have to innovate. Kintera is definitely on the right track and I&#039;m stunned that their API is so open. I&#039;m still holding off on further analysis pending my registration with both of the API partner programs.</description>
		<content:encoded><![CDATA[<p>@Peter Gulka: Blackbaud going open on the 7x product seems to me to be unlikely but now that they&#8217;re literally the last major nonprofit CRM vendor out there without an open API, the pressure is on.</p>
<p>@Doug Yeager: Thanks Doug for your kind comment. Kintera and Convio are not in market leader positions so they have to innovate. Kintera is definitely on the right track and I&#8217;m stunned that their API is so open. I&#8217;m still holding off on further analysis pending my registration with both of the API partner programs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Yeager</title>
		<link>http://www.nonprofittechblog.org/convio-and-kintera-open-their-apis-but-befuddles-coders/comment-page-1#comment-57589</link>
		<dc:creator>Doug Yeager</dc:creator>
		<pubDate>Thu, 18 Oct 2007 23:28:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/convio-and-kintera-open-their-apis-but-befuddles-coders#comment-57589</guid>
		<description>Great job Alan!  My two cents is that both companies have realized that openness is going to drive the market, and that in a very short time managed to get something out the door.  

Not bad, even if it is a bit like &quot;openliness&quot; and in the eye of the beholder.

The good news: this is version 1 and only will get better. I think Kintera thought that the coding would come from their &quot;partner&quot; community, and didn&#039;t even think of the independents and wave of innovation that accompanied the &quot;give it away&quot; pioneers.
doug</description>
		<content:encoded><![CDATA[<p>Great job Alan!  My two cents is that both companies have realized that openness is going to drive the market, and that in a very short time managed to get something out the door.  </p>
<p>Not bad, even if it is a bit like &#8220;openliness&#8221; and in the eye of the beholder.</p>
<p>The good news: this is version 1 and only will get better. I think Kintera thought that the coding would come from their &#8220;partner&#8221; community, and didn&#8217;t even think of the independents and wave of innovation that accompanied the &#8220;give it away&#8221; pioneers.<br />
doug</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Gulka</title>
		<link>http://www.nonprofittechblog.org/convio-and-kintera-open-their-apis-but-befuddles-coders/comment-page-1#comment-57491</link>
		<dc:creator>Peter Gulka</dc:creator>
		<pubDate>Thu, 18 Oct 2007 17:09:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/convio-and-kintera-open-their-apis-but-befuddles-coders#comment-57491</guid>
		<description>I hope Blackbaud is watching this closely. I really do. With the 7x product on the way out in favor of Infinity development it would seem to me to be a no brainer to stop charging for the API. 

Here&#039;s hoping that my calls do not fall on deaf ears.</description>
		<content:encoded><![CDATA[<p>I hope Blackbaud is watching this closely. I really do. With the 7x product on the way out in favor of Infinity development it would seem to me to be a no brainer to stop charging for the API. </p>
<p>Here&#8217;s hoping that my calls do not fall on deaf ears.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
