<?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: Phweet and consumer voice mashups</title>
	<atom:link href="http://voodoolabs.wordpress.com/2008/08/05/phweet-case-study-for-consumer-voice-mashups/feed/" rel="self" type="application/rss+xml" />
	<link>http://voodoolabs.wordpress.com/2008/08/05/phweet-case-study-for-consumer-voice-mashups/</link>
	<description>News and thoughts from VoodooVox R&#38;D</description>
	<lastBuildDate>Fri, 15 Aug 2008 13:06:34 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: voodoolabs</title>
		<link>http://voodoolabs.wordpress.com/2008/08/05/phweet-case-study-for-consumer-voice-mashups/#comment-61</link>
		<dc:creator>voodoolabs</dc:creator>
		<pubDate>Fri, 15 Aug 2008 13:06:34 +0000</pubDate>
		<guid isPermaLink="false">http://voodoolabs.wordpress.com/?p=57#comment-61</guid>
		<description>@ben10dough:  Are you talking about accessibility in terms of easy-of-access/use, or accessibility for those with disabilities?</description>
		<content:encoded><![CDATA[<p>@ben10dough:  Are you talking about accessibility in terms of easy-of-access/use, or accessibility for those with disabilities?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ben10dough</title>
		<link>http://voodoolabs.wordpress.com/2008/08/05/phweet-case-study-for-consumer-voice-mashups/#comment-60</link>
		<dc:creator>ben10dough</dc:creator>
		<pubDate>Fri, 15 Aug 2008 08:33:20 +0000</pubDate>
		<guid isPermaLink="false">http://voodoolabs.wordpress.com/?p=57#comment-60</guid>
		<description>How is the site with accessibility?</description>
		<content:encoded><![CDATA[<p>How is the site with accessibility?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phweet Quotes - Thanks &#124; stuart henshall</title>
		<link>http://voodoolabs.wordpress.com/2008/08/05/phweet-case-study-for-consumer-voice-mashups/#comment-59</link>
		<dc:creator>Phweet Quotes - Thanks &#124; stuart henshall</dc:creator>
		<pubDate>Thu, 07 Aug 2008 05:13:40 +0000</pubDate>
		<guid isPermaLink="false">http://voodoolabs.wordpress.com/?p=57#comment-59</guid>
		<description>[...] Phweet and consumer voice mashups « VoodooLabs’s Weblog Phweet may really have hit on something in the use of Twitter as the invite and notification medium du jour. They’ve had pretty good traffic in their first week for a service that’s spread through word-of-mouth, and many telephony bloggers have taken notice. And Phweet is truly a voice mashup, combining the Twitter API with TringMe (for the Flash-based VoIP piece) and Televolution’s in order to build something fundamentally new and cool - for consumers.What’s been particularly enjoyable is seeing how conscious the Phweet guys are of how exciting it is to be able to build a service like theirs, and how much credit they give to the existence of the APIs on which they depend. And then there’s this observation from their blog: Phweet proves both as a reference service and in terms of potential that web/voice/social-media mashups are the future…We believe that Phweet and others can sit at the intersection of the web and telephony. [...]</description>
		<content:encoded><![CDATA[<p>[...] Phweet and consumer voice mashups « VoodooLabs’s Weblog Phweet may really have hit on something in the use of Twitter as the invite and notification medium du jour. They’ve had pretty good traffic in their first week for a service that’s spread through word-of-mouth, and many telephony bloggers have taken notice. And Phweet is truly a voice mashup, combining the Twitter API with TringMe (for the Flash-based VoIP piece) and Televolution’s in order to build something fundamentally new and cool &#8211; for consumers.What’s been particularly enjoyable is seeing how conscious the Phweet guys are of how exciting it is to be able to build a service like theirs, and how much credit they give to the existence of the APIs on which they depend. And then there’s this observation from their blog: Phweet proves both as a reference service and in terms of potential that web/voice/social-media mashups are the future…We believe that Phweet and others can sit at the intersection of the web and telephony. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
