<?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/"
		>
<channel>
	<title>Comments on: A Flurry of updates to Mothra?</title>
	<atom:link href="http://shopsavvy.mobi/2008/12/24/a-flurry-of-updates-to-mothra/feed/" rel="self" type="application/rss+xml" />
	<link>http://shopsavvy.mobi/2008/12/24/a-flurry-of-updates-to-mothra/</link>
	<description>Shopping. Improved.</description>
	<lastBuildDate>Sat, 28 Jan 2012 23:14:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Big in Japan</title>
		<link>http://shopsavvy.mobi/2008/12/24/a-flurry-of-updates-to-mothra/#comment-1311</link>
		<dc:creator>Big in Japan</dc:creator>
		<pubDate>Sat, 27 Dec 2008 04:10:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.biggu.com/?p=1177#comment-1311</guid>
		<description>Prior to using the application (just after downloading) you were required to approve our terms of service (mirrored on Google&#039;s Ts&amp;Cs).  Your comment caught my attention as you seem unaware that ShopSavvy &#039;calls home&#039;.  Of course, every time you scan an item it MUST call home to search for information to present to you.  The terms of service attempt to explain:
&lt;em&gt;
&quot;Our applications collect from Application visitors’ statistical information regarding what UPCs are scanned, pages are visited, the date and time of the visits, how long it took a user to download a page, debugging/crash data and the TCP/IP address of the user. These automated Application functions do not collect this information in a manner intended to identify your individual use of the Application, nor do we use this information for any such purpose. This information is collected to assist us in maintaining a high quality Application, as well as, providing necessary traffic information to our advertisers.&quot;&lt;/em&gt;

Use of the application depends on the ability of the application to &#039;call home&#039;.  If you want to turn off &#039;calling home&#039; you might as well uninstall the application as it won&#039;t do anything - i.e. it can&#039;t offer comparison pricing.  We have tried to make the terms of service as prominent and simple as possible - hopefully the application is worth the overhead it creates.</description>
		<content:encoded><![CDATA[<p>Prior to using the application (just after downloading) you were required to approve our terms of service (mirrored on Google&#8217;s Ts&amp;Cs).  Your comment caught my attention as you seem unaware that ShopSavvy &#8216;calls home&#8217;.  Of course, every time you scan an item it MUST call home to search for information to present to you.  The terms of service attempt to explain:<br />
<em><br />
&#8220;Our applications collect from Application visitors’ statistical information regarding what UPCs are scanned, pages are visited, the date and time of the visits, how long it took a user to download a page, debugging/crash data and the TCP/IP address of the user. These automated Application functions do not collect this information in a manner intended to identify your individual use of the Application, nor do we use this information for any such purpose. This information is collected to assist us in maintaining a high quality Application, as well as, providing necessary traffic information to our advertisers.&#8221;</em></p>
<p>Use of the application depends on the ability of the application to &#8216;call home&#8217;.  If you want to turn off &#8216;calling home&#8217; you might as well uninstall the application as it won&#8217;t do anything &#8211; i.e. it can&#8217;t offer comparison pricing.  We have tried to make the terms of service as prominent and simple as possible &#8211; hopefully the application is worth the overhead it creates.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Gray</title>
		<link>http://shopsavvy.mobi/2008/12/24/a-flurry-of-updates-to-mothra/#comment-1312</link>
		<dc:creator>Jeremy Gray</dc:creator>
		<pubDate>Sat, 27 Dec 2008 01:29:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.biggu.com/?p=1177#comment-1312</guid>
		<description>&quot;One of these items was a handy little feature for the app to “call home” in the background in the event of a crash and send us debugging information.

Now that 3.1.0 is out, it’s already calling home about some obscure bugs.&quot;

In my haste to try out the application, I may have simply brainfarted and missed this during the installation, start-up, and usage process, but at no point do I remember agreeing to phone-home behavior. Was I presented with this option at some point and wasn&#039;t paying enough attention and clicked right on through? (bad Jeremy!) Was there no such declaration/option? (There bloody-well should be.) What&#039;s worse, there appears to be no way to change this behavior when running ShopSavvy itself.

In any case, further transparency in this area is highly recommended, and I dare say that a configuration option is flat-out required unless you want people to start getting angry about the application using bandwidth in an unapproved fashion.

As a software developer myself, I most certainly understand and appreciate the benefit that this kind of functionality can provide. That said, your users need to know about it and have control over it.</description>
		<content:encoded><![CDATA[<p>&#8220;One of these items was a handy little feature for the app to “call home” in the background in the event of a crash and send us debugging information.</p>
<p>Now that 3.1.0 is out, it’s already calling home about some obscure bugs.&#8221;</p>
<p>In my haste to try out the application, I may have simply brainfarted and missed this during the installation, start-up, and usage process, but at no point do I remember agreeing to phone-home behavior. Was I presented with this option at some point and wasn&#8217;t paying enough attention and clicked right on through? (bad Jeremy!) Was there no such declaration/option? (There bloody-well should be.) What&#8217;s worse, there appears to be no way to change this behavior when running ShopSavvy itself.</p>
<p>In any case, further transparency in this area is highly recommended, and I dare say that a configuration option is flat-out required unless you want people to start getting angry about the application using bandwidth in an unapproved fashion.</p>
<p>As a software developer myself, I most certainly understand and appreciate the benefit that this kind of functionality can provide. That said, your users need to know about it and have control over it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Muse</title>
		<link>http://shopsavvy.mobi/2008/12/24/a-flurry-of-updates-to-mothra/#comment-1310</link>
		<dc:creator>Alex Muse</dc:creator>
		<pubDate>Sat, 25 Jun 2005 23:26:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.biggu.com/?p=1177#comment-1310</guid>
		<description>&lt;strong&gt;Where you can find me blogging&#8230;&lt;/strong&gt;

	For now I am swamped with Blogging/RSS/Wiki projects so I cannot keep up this blog too.  So for now you can visit:
	Productivity Blog (Architel)
MotorSport Ranch Blog (Our television show)
Weblogs Work (in partnership with Lightbox5)
Poker Blog (my WS...</description>
		<content:encoded><![CDATA[<p><strong>Where you can find me blogging&#8230;</strong></p>
<p>	For now I am swamped with Blogging/RSS/Wiki projects so I cannot keep up this blog too.  So for now you can visit:<br />
	Productivity Blog (Architel)<br />
MotorSport Ranch Blog (Our television show)<br />
Weblogs Work (in partnership with Lightbox5)<br />
Poker Blog (my WS&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

