elm.chat v0.1.2 is a maintenance release centered on a concrete self-hosting fix.
What changed
- Cloudflare can now detect the npm-workspaces project from the repository root through a root
wrangler.jsoncand root build/deploy commands. - An automated drift check keeps the public deployment template aligned with the production Worker configuration.
- Independent deployments omit elm.chat's optional aggregate growth-measurement binding.
- Invite sharing now prefers the native share sheet, falls back to the clipboard, and records only successful aggregate handoffs.
- Closed-WebSocket handling is more defensive during room teardown and refresh flows.
The full public self-host path was tested through Cloudflare's setup screen. The expected build command, deploy command, and repository path were detected; the verification stopped before creating a test Worker.
- Try elm.chat: https://elm.chat
- Deploy your own instance: https://elm.chat/deploy/cloudflare
- Architecture and deployment lesson: https://elm.chat/building-ephemeral-chat-cloudflare
- Full changelog: https://github.com/shawnbure/elm-chat/blob/v0.1.2/CHANGELOG.md
Security status
elm.chat has not completed an independent security audit. Message authentication and replay/duplicate protection remain unfinished. The Cloudflare relay can observe ordinary connection metadata, and participants or compromised devices can retain message or file copies. This release is not an anonymity system, high-risk source channel, compliance product, or production-ready financial communications system.