<?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: Should developers charge for add-ons?</title>
	<atom:link href="http://www.oxymoronical.com/blog/2008/06/Should-developers-charge-for-add-ons/feed" rel="self" type="application/rss+xml" />
	<link>http://www.oxymoronical.com/blog/2008/06/Should-developers-charge-for-add-ons</link>
	<description>Spouting nonsense from the depths of my spare time</description>
	<lastBuildDate>Sat, 14 Jan 2012 22:20:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Archaeopteryx</title>
		<link>http://www.oxymoronical.com/blog/2008/06/Should-developers-charge-for-add-ons#comment-7349</link>
		<dc:creator>Archaeopteryx</dc:creator>
		<pubDate>Mon, 14 Jul 2008 18:51:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.oxymoronical.com/?p=64#comment-7349</guid>
		<description>At first I have to confess that in the past and also probably today my main motivation for installing a piece of software is if you can get it for free. The only thing bought was the operating system (Win XP) together with the machine and I probably wouldn&#039;t pay for add-ons, maybe donate later when I will have an income. Openness has a lower priority.

It&#039;s the right of developer to sell an extension or not. If he does, he should remember the following consequences:
- If it was for free, users will try to live with the existing version and keep it alive = continued development on their own (at least private) . The user rate will drop by more than 90 percent, iirc only three percent of the internet users is willing to pay for things in the internet [citation needed].
- External supporters like testers and localizers will often loose interest in supporting your product (because they think that they already invested something in your product and won&#039;t pay anything for it).
- Clones of your product will probably develop. If they already existed, people will replace your add-on with theirs, even if it has less quality.
- Indirect payments by the users should be tested: Adding ads to your add-on or the web pages or changing the search engine could be an alternative.

Consequences for AMO:
- If a free version had a license which allowed to use the code, the files shouldn&#039;t be deleteable.
- There should be an easy way to exclude buyable extensions from search results (just visit a page with freeware and shareware and you will get know how frustating it will be if you can&#039;t). Free limited versions which only describe the limited versions are ok to list.
- Maybe paid versions should only be linked from AMO (there is a general bug about external add-ons and AMO), so they can improve their quality by submitting fixes as updates faster to the consumers (without the need for amo editors). Also, paid add-ons are often more complex and so the chance to get reviewed is lower.</description>
		<content:encoded><![CDATA[<p>At first I have to confess that in the past and also probably today my main motivation for installing a piece of software is if you can get it for free. The only thing bought was the operating system (Win XP) together with the machine and I probably wouldn&#8217;t pay for add-ons, maybe donate later when I will have an income. Openness has a lower priority.</p>
<p>It&#8217;s the right of developer to sell an extension or not. If he does, he should remember the following consequences:<br />
- If it was for free, users will try to live with the existing version and keep it alive = continued development on their own (at least private) . The user rate will drop by more than 90 percent, iirc only three percent of the internet users is willing to pay for things in the internet [citation needed].<br />
- External supporters like testers and localizers will often loose interest in supporting your product (because they think that they already invested something in your product and won&#8217;t pay anything for it).<br />
- Clones of your product will probably develop. If they already existed, people will replace your add-on with theirs, even if it has less quality.<br />
- Indirect payments by the users should be tested: Adding ads to your add-on or the web pages or changing the search engine could be an alternative.</p>
<p>Consequences for AMO:<br />
- If a free version had a license which allowed to use the code, the files shouldn&#8217;t be deleteable.<br />
- There should be an easy way to exclude buyable extensions from search results (just visit a page with freeware and shareware and you will get know how frustating it will be if you can&#8217;t). Free limited versions which only describe the limited versions are ok to list.<br />
- Maybe paid versions should only be linked from AMO (there is a general bug about external add-ons and AMO), so they can improve their quality by submitting fixes as updates faster to the consumers (without the need for amo editors). Also, paid add-ons are often more complex and so the chance to get reviewed is lower.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DonGato</title>
		<link>http://www.oxymoronical.com/blog/2008/06/Should-developers-charge-for-add-ons#comment-6648</link>
		<dc:creator>DonGato</dc:creator>
		<pubDate>Sun, 06 Jul 2008 14:04:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.oxymoronical.com/?p=64#comment-6648</guid>
		<description>No problem with them asking for money, but not at AMO. That&#039;s unfair as I&#039;m investing a lot of time for free and expect some difference/preference from people getting paid of. As I posted in the other blog about AMO allowing adverts I think the compromise would be to set a separate section or site for paid addons.

If you don&#039;t do that (differentiate them and prioritize free over paid) and most of the people working for free will switch to ask money for their work or even stop working, and that would be really bad for Mozilla.</description>
		<content:encoded><![CDATA[<p>No problem with them asking for money, but not at AMO. That&#8217;s unfair as I&#8217;m investing a lot of time for free and expect some difference/preference from people getting paid of. As I posted in the other blog about AMO allowing adverts I think the compromise would be to set a separate section or site for paid addons.</p>
<p>If you don&#8217;t do that (differentiate them and prioritize free over paid) and most of the people working for free will switch to ask money for their work or even stop working, and that would be really bad for Mozilla.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Basil Hashem</title>
		<link>http://www.oxymoronical.com/blog/2008/06/Should-developers-charge-for-add-ons#comment-6033</link>
		<dc:creator>Basil Hashem</dc:creator>
		<pubDate>Sat, 28 Jun 2008 01:51:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.oxymoronical.com/?p=64#comment-6033</guid>
		<description>@funtomas, actually, it&#039;s not true that an add-on author can&#039;t host their own add-on and update it. Many do, take e.g. Google Toolbar - it is currently not hosted on AMO and they publish updates themselves. See &lt;a href=&quot;http://developer.mozilla.org/en/docs/Extension_Versioning,_Update_and_Compatibility#Securing_Updates.&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;

Examples of commercial add-ons: &lt;a href=&quot;http://www.attensa.com&quot; rel=&quot;nofollow&quot;&gt;Attensa Feed Reader&lt;/a&gt;, &lt;a href=&quot;http://www.iopus.com/imacros/&quot; rel=&quot;nofollow&quot;&gt;iMacros&lt;/a&gt;, &lt;a href=&quot;http://www.drawloop.com&quot; rel=&quot;nofollow&quot;&gt;Loop-to-PDF&lt;/a&gt; and many ohers.</description>
		<content:encoded><![CDATA[<p>@funtomas, actually, it&#8217;s not true that an add-on author can&#8217;t host their own add-on and update it. Many do, take e.g. Google Toolbar &#8211; it is currently not hosted on AMO and they publish updates themselves. See <a href="http://developer.mozilla.org/en/docs/Extension_Versioning,_Update_and_Compatibility#Securing_Updates." rel="nofollow">here</a></p>
<p>Examples of commercial add-ons: <a href="http://www.attensa.com" rel="nofollow">Attensa Feed Reader</a>, <a href="http://www.iopus.com/imacros/" rel="nofollow">iMacros</a>, <a href="http://www.drawloop.com" rel="nofollow">Loop-to-PDF</a> and many ohers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vygantas</title>
		<link>http://www.oxymoronical.com/blog/2008/06/Should-developers-charge-for-add-ons#comment-6007</link>
		<dc:creator>Vygantas</dc:creator>
		<pubDate>Fri, 27 Jun 2008 07:27:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.oxymoronical.com/?p=64#comment-6007</guid>
		<description>Any examples (urls) with paid add-ons?</description>
		<content:encoded><![CDATA[<p>Any examples (urls) with paid add-ons?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stahn</title>
		<link>http://www.oxymoronical.com/blog/2008/06/Should-developers-charge-for-add-ons#comment-6003</link>
		<dc:creator>Stahn</dc:creator>
		<pubDate>Fri, 27 Jun 2008 04:58:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.oxymoronical.com/?p=64#comment-6003</guid>
		<description>Use Opera, all add ons are integrated.

Mozilla Inc. shouldn&#039;t support this.</description>
		<content:encoded><![CDATA[<p>Use Opera, all add ons are integrated.</p>
<p>Mozilla Inc. shouldn&#8217;t support this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kiroset</title>
		<link>http://www.oxymoronical.com/blog/2008/06/Should-developers-charge-for-add-ons#comment-5992</link>
		<dc:creator>kiroset</dc:creator>
		<pubDate>Thu, 26 Jun 2008 23:23:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.oxymoronical.com/?p=64#comment-5992</guid>
		<description>AMO should make it easier for add-on authors to collect donations.  Not as a financial broker, but just provide a space on the AMO page for an official link where the author has a donation page set up.</description>
		<content:encoded><![CDATA[<p>AMO should make it easier for add-on authors to collect donations.  Not as a financial broker, but just provide a space on the AMO page for an official link where the author has a donation page set up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelson</title>
		<link>http://www.oxymoronical.com/blog/2008/06/Should-developers-charge-for-add-ons#comment-5988</link>
		<dc:creator>Kelson</dc:creator>
		<pubDate>Thu, 26 Jun 2008 23:00:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.oxymoronical.com/?p=64#comment-5988</guid>
		<description>This reminds me a little of the controversy over WordPress themes a while back.  Although in that case it was over &quot;sponsored links&quot; built into the theme, sort of the equivalent of an extension adding advertisements to the browser chrome.</description>
		<content:encoded><![CDATA[<p>This reminds me a little of the controversy over WordPress themes a while back.  Although in that case it was over &#8220;sponsored links&#8221; built into the theme, sort of the equivalent of an extension adding advertisements to the browser chrome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mossop</title>
		<link>http://www.oxymoronical.com/blog/2008/06/Should-developers-charge-for-add-ons#comment-5974</link>
		<dc:creator>Mossop</dc:creator>
		<pubDate>Thu, 26 Jun 2008 13:07:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.oxymoronical.com/?p=64#comment-5974</guid>
		<description>funtomas, that is not the case. Add-on developers can still host their add-ons outside of AMO with Firefox 3, however they would need to meet the same security restrictions that AMO already does, either by hosting on an ssl secured website or using signed updates (which cost nothing except a little effort to set up)</description>
		<content:encoded><![CDATA[<p>funtomas, that is not the case. Add-on developers can still host their add-ons outside of AMO with Firefox 3, however they would need to meet the same security restrictions that AMO already does, either by hosting on an ssl secured website or using signed updates (which cost nothing except a little effort to set up)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: funtomas</title>
		<link>http://www.oxymoronical.com/blog/2008/06/Should-developers-charge-for-add-ons#comment-5973</link>
		<dc:creator>funtomas</dc:creator>
		<pubDate>Thu, 26 Jun 2008 12:57:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.oxymoronical.com/?p=64#comment-5973</guid>
		<description>I too konw of one non-free addon. Before FF3 was released, it was hosted on author&#039;s website which is now impossible - FF3 blocks those addons pinging for update outside of AMO. Solution? Adding PayPal capabilities to AMO.</description>
		<content:encoded><![CDATA[<p>I too konw of one non-free addon. Before FF3 was released, it was hosted on author&#8217;s website which is now impossible &#8211; FF3 blocks those addons pinging for update outside of AMO. Solution? Adding PayPal capabilities to AMO.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

