# Google Chrome extension for discourse notifications

**URL:** https://meta.discourse.org/t/google-chrome-extension-for-discourse-notifications/34496
**Category:** Extras
**Created:** [October 14, 2015, 10:56am UTC](https://meta.discourse.org/t/google-chrome-extension-for-discourse-notifications/34496 "2015-10-14T10:56:56Z")
**Posts on this page:** 1
**Showing post:** 25

<div class="post-metadata">

### Author: ![alep](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/alep/32/120750_2.png) [@alep](https://meta.discourse.org/u/alep)
#### Post date: [April 20, 2016, 2:09pm UTC](https://meta.discourse.org/t/google-chrome-extension-for-discourse-notifications/34496/25 "2016-04-20T14:09:06Z")

</div>

> [@ljpp](#):
>
> Could you give a brief explanation of the technical implementation - how does this extension poll the site for notifications? Does it keep the session constantly online, or does the pluging check-in to the site periodically for new notfications?

It gets some user data at boot, for example to get the user id.  
Then it uses message bus to receive notifications.  
@sam gave me the advice in this [post](https://meta.discourse.org/t/discourse-chrome-extension-to-show-unread-count/27853/12)

> [@ljpp](#):
>
> Recently I’ve had some messagebus load issues under very high traffic spikes, so I am concerned what it will do to my server load, if all my loyalists install this plugin.

Probably you may find some useful information [here](https://meta.discourse.org/t/analyzing-discourse-performance-using-nginx-logs/30117)

---

_[View the full topic](https://meta.discourse.org/t/google-chrome-extension-for-discourse-notifications/34496)._
