# Plugin install statistics

**URL:** https://meta.discourse.org/t/plugin-install-statistics/68473
**Category:** Development
**Created:** [August 21, 2017, 1:45pm UTC](https://meta.discourse.org/t/plugin-install-statistics/68473 "2017-08-21T13:45:28Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [August 21, 2017, 1:45pm UTC](https://meta.discourse.org/t/plugin-install-statistics/68473/1 "2017-08-21T13:45:28Z")

</div>

So this is really cool:

> <https://twitter.com/discourse/status/895765398569623552>

I wonder, do [@team](https://meta.discourse.org/groups/team) collect any similar statistics for plugin installations? It would be really cool to know what are the most used plugins for Discourse. Right now the only real measure I can see is the number of posts on meta about the plugin - and that generally just means something has gone wrong with it 😉

One example of a plugin that loads of people clearly use, but haven’t posted about much is the [dropbox sync](https://meta.discourse.org/t/discourse-backups-to-dropbox/51176/62) plugin (3rd topic in the “top” list of Meta for this year). It’s just recently got a lot of posts about it because it’s broken 😆.

If it’s not something you collect, is it something you’d be interested in adding to the existing version check pings?

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [August 21, 2017, 6:14pm UTC](https://meta.discourse.org/t/plugin-install-statistics/68473/2 "2017-08-21T18:14:32Z")

</div>

Giant can of worms there, so not particularly interested in reopening it at this time.

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [August 21, 2017, 6:18pm UTC](https://meta.discourse.org/t/plugin-install-statistics/68473/3 "2017-08-21T18:18:27Z")

</div>

From a technical perspective? Or a privacy perspective?

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [August 21, 2017, 7:14pm UTC](https://meta.discourse.org/t/plugin-install-statistics/68473/4 "2017-08-21T19:14:54Z")

</div>

Well, you’d need to start with public page that lists the installed plugins. The value of such a page is pretty questionable to the outside world.

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [August 21, 2017, 7:59pm UTC](https://meta.discourse.org/t/plugin-install-statistics/68473/5 "2017-08-21T19:59:08Z")

</div>

Rather than a public page, I was thinking that a list of plugins could be attached to the payload currently sent to `https://api.discourse.org/hub` whenever updates are checked. So the info would only be available to the team, and could then be shared in an anonymised way with the public.

> <https://github.com/discourse/discourse/blob/main/lib/discourse_hub.rb#L8>

It’s a bit of a minefield from a privacy perspective, but I still think it would be cool (probably cos I’m not the one that would have to take responsibility for collecting the data 😉 ).

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [August 21, 2017, 8:15pm UTC](https://meta.discourse.org/t/plugin-install-statistics/68473/6 "2017-08-21T20:15:05Z")

</div>

For political reasons, it has to be a public page. Sorry!
