Building an Application
Integrate live video into your project. - API reference - Our component library
Developers & Self-Hosters
Learn how to deploy, or contribute to Streamplace.
Section titled “Learn how to deploy, or contribute to Streamplace.”Self-Hosting
Run your own Streamplace infrastructure. - Installation guide
Contributing
Help improve Streamplace. - Development setup - Video signing
Support & Community
Get help and connect with other developers. - GitHub issues - Discord community
Chat message timestamps
Section titled “Chat message timestamps”Chat messages (place.stream.chat.message) sent by Streamplace include the
sending device’s local UTC offset in createdAt, for example
2026-10-17T13:30:00.123-07:00. The offset is read at send time, including
daylight-saving adjustments; there is no account-wide time zone setting. Devices
set to UTC send +00:00. Existing records ending in Z remain valid.
The node preserves the original timestamp in the record and compares instants
for chat ordering and freshness. Consumers should parse RFC 3339 timestamps, not
compare their strings or assume a trailing Z.
The offset gives bots the sender’s local wall-clock time, not an IANA time zone
such as America/Los_Angeles. It cannot determine daylight-saving transitions
for future scheduling; ask for a named zone when those rules matter.