# What scope does PubSub need?

**URL:** <https://staging-discuss.dev.twitch.com/t/what-scope-does-pubsub-need/7514>\
**Category:** Chat and IRC\
**Created:** [September 20, 2016, 6:08am UTC](https://staging-discuss.dev.twitch.com/t/what-scope-does-pubsub-need/7514 "2016-09-20T06:08:53Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://staging-discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [September 20, 2016, 9:45am UTC](https://staging-discuss.dev.twitch.com/t/what-scope-does-pubsub-need/7514/5 "2016-09-20T09:45:59Z")

</div>

> [@In-line broadcaster chat mod logs](https://staging-discuss.dev.twitch.com/t/in-line-broadcaster-chat-mod-logs/7281/21):
>
> Er is that much different than a client-side time-stamp when it receives the event? I imagine this is for ordering purposes, or what? We try to keep events as small as possible to limit maintenance, and to keep performance high. Events should be received as they get sent through, and a timestamp might be slightly different depending on which server handled the request (though we use ntp and theoretically shouldn’t be clock drift)

`UPDATE: We are changing the topic relatively soon, so we can support moderators receiving these messages. You should listen on the `chat\_moderator\_actions.{user\_id}.{room\_id} where user\_id is the moderator user ID, and roomID is the user\_id of the channel/user.`

---

_[View the full topic](https://staging-discuss.dev.twitch.com/t/what-scope-does-pubsub-need/7514)._