# Common event system for chatrooms - a specification

**URL:** <https://meta.discourse.org/t/common-event-system-for-chatrooms-a-specification/59245>\
**Category:** Feature\
**Created:** [March 16, 2017, 1:01pm UTC](https://meta.discourse.org/t/common-event-system-for-chatrooms-a-specification/59245 "2017-03-16T13:01:04Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)\
**Post date:** [March 17, 2017, 2:34pm UTC](https://meta.discourse.org/t/common-event-system-for-chatrooms-a-specification/59245/8 "2017-03-17T14:34:30Z")

</div>

> [@david](#):
>
> I don’t fully understand this. If you’re not envisioning any kind of “subscription” model in the common event system, then why is there a need for a separate “notify chat” event, when chat plugins can quite easily attach to a :post\_created event?

I assume that if today you started work on a second chat adapter, you’d end up copying and pasting a bunch of code from the slack one. That’s the stuff that should live in the core plugin! In particular, the admin page the filter rules. The core plugin would watch `post_created`, check those filters, then trigger `notify_chat` for delivery. Any adapters that receive `notify_chat` would just send it, and not worry about filters themselves.

> [@david](#):
>
> Ultimately what I think it all comes down to is who is this feature for, and what’s its use case? I’ve been thinking of it as another way for users to receive updates, whereas I think you’re thinking about it as an admin/mod tool?

Not exactly – an admin has to set it up, but it can be used by public chatrooms. For example, if you are in the emberjs slack, you might want to see when new posts are made on the emberjs discussion board. That has to be set up by an admin, but consumed by regular users.

Once the core product is built we can look into layering user level messages on top, but like we said earlier, that’s a whole bunch of work that depends on other stuff working nicely first.

---

_[View the full topic](https://meta.discourse.org/t/common-event-system-for-chatrooms-a-specification/59245)._