# In-line broadcaster chat mod logs

**URL:** <https://staging-discuss.dev.twitch.com/t/in-line-broadcaster-chat-mod-logs/7281>\
**Category:** Chat and IRC\
**Created:** [September 2, 2016, 7:11pm UTC](https://staging-discuss.dev.twitch.com/t/in-line-broadcaster-chat-mod-logs/7281 "2016-09-02T19:11:02Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![xangold](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/xangold/32/527_2.png) [@xangold](https://staging-discuss.dev.twitch.com/u/xangold)\
**Post date:** [September 13, 2016, 8:58pm UTC](https://staging-discuss.dev.twitch.com/t/in-line-broadcaster-chat-mod-logs/7281/21 "2016-09-13T20:58:39Z")

</div>

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)

---

_[View the full topic](https://staging-discuss.dev.twitch.com/t/in-line-broadcaster-chat-mod-logs/7281)._