Comments on: Add-on Stats-a-holic http://blog.mozilla.com/addons/2008/06/26/add-on-stats-a-holic/ Official Blog of Mozilla Add-ons Tue, 24 Nov 2009 06:36:43 -0800 http://wordpress.org/?v=2.8.6 hourly 1 By: bhashem http://blog.mozilla.com/addons/2008/06/26/add-on-stats-a-holic/comment-page-1/#comment-184 bhashem Thu, 26 Jun 2008 18:51:54 +0000 http://blog.mozilla.com/basil/2008/06/26/add-on-stats-a-holic/#comment-184 @Arch: One of the pieces of data that I've wanted to introduce back into the public detailed pages for add-ons is Active Users. The concern is that some companies (and individuals) do not want this information made public for competitive or other reasons. That's understandable. My approach was going to be to enable active users by default (when we add it) but allow authors to hide it if they want. Download numbers are already public on the site. Depending on how this plays out, we can then make most stats dashboards public while honoring author's preference as to whether to include Active User counts. Thanks for the feedback. @Arch: One of the pieces of data that I’ve wanted to introduce back into the public detailed pages for add-ons is Active Users. The concern is that some companies (and individuals) do not want this information made public for competitive or other reasons. That’s understandable.

My approach was going to be to enable active users by default (when we add it) but allow authors to hide it if they want. Download numbers are already public on the site.

Depending on how this plays out, we can then make most stats dashboards public while honoring author’s preference as to whether to include Active User counts.

Thanks for the feedback.

]]> By: Archaeopteryx http://blog.mozilla.com/addons/2008/06/26/add-on-stats-a-holic/comment-page-1/#comment-183 Archaeopteryx Thu, 26 Jun 2008 16:01:05 +0000 http://blog.mozilla.com/basil/2008/06/26/add-on-stats-a-holic/#comment-183 Imho, the statistics should be public for everyone (including details about active versions). This would be something with which nearly every developer should be able to live. If a vulnerable extension exists, it can be disabled by the blocklist and everyone knows that not all people update in the first weeks (the same for Firefox). But this data has valueable information, i.e. for localizers which search for popular add-ons which aren't yet available in their language, the IT consumer press ("Popular Firefox extensions"), application developers (what do people miss in the app and how should the ideal app behave), other extension developers whose extension needs another one (can they expect that the people have the version they need), QA interested people (which are the extensions which are the most userDisabled), educational stuff (trends, marketing analysis, about software distributions etc.). Imho, the statistics should be public for everyone (including details about active versions). This would be something with which nearly every developer should be able to live. If a vulnerable extension exists, it can be disabled by the blocklist and everyone knows that not all people update in the first weeks (the same for Firefox). But this data has valueable information, i.e. for localizers which search for popular add-ons which aren’t yet available in their language, the IT consumer press (”Popular Firefox extensions”), application developers (what do people miss in the app and how should the ideal app behave), other extension developers whose extension needs another one (can they expect that the people have the version they need), QA interested people (which are the extensions which are the most userDisabled), educational stuff (trends, marketing analysis, about software distributions etc.).

]]>