The discussion revolves around a feature request to embed Discourse chat into external webpages, primarily via iframes or widgets, to facilitate synchronous communication during events or alongside other content. Michael_Ball initiates the thread, seeking a solution to bridge remote and in-person attendees for an upcoming event, specifically asking if the existing comments embed view can be leveraged for chat.
Sam responds that while this is a great feature request, it is not currently supported. He notes that “widgetizing” chat would require significant internal rework, particularly regarding anonymous users, and classifies it as a version 2 or 3 priority rather than an immediate roadmap item. Mcwumbly adds context by linking to a related topic and encourages users to provide concrete use cases and mockups to help define requirements.
jordan-violet provides a detailed use case for a developer conference, where they aim to embed chat next to a live stream. They share a mockup and explain that while they used Discord with Widgetbot as a stopgap due to tight deadlines, they strongly prefer a native Discourse solution to maintain community continuity. Jordan emphasizes the need for “staged” (unregistered but identified) users to participate, ensuring executives and prospective customers can chat without full account creation. Michael_Ball agrees, noting that avoiding third-party tools like Discord helps prevent user account fragmentation.
Other users contribute similar needs: MKorndoerfer wants to integrate chat directly into their primary site for casual chats, while satonotdead highlights the value of demonstrating Discourse’s capabilities without friction. nathank outlines two specific use cases: allowing existing logged-in users to access chat easily across their digital estate, and using anonymous chat as a funnel to capture emails and create staged users. hello2029 asks about embedding chat into specific groups for support requests, and Nick_Stager suggests syncing customer service chat with forum FAQs.
Mcwumbly reiterates that while there is significant interest, the feature represents a significant investment. Michael_Ball asks for plugin pointers for iframes, while MKorndoerfer notes that requiring login is acceptable for their use case. The thread concludes with Youan bumping the topic to check for progress, highlighting the need for embedded chat in a community radio station context.