Engineering Notes from building and running the dtwin ecosystem: deploys, builds, incidents and the fixes behind them, with the commands to reproduce each one.
Mosques from OpenStreetMap: 2,285 congregations, one layer
How dtwin imports every mosque in Uzbekistan from OpenStreetMap and keeps congregation times in a layer of their own, separate from the prayer-time calculation.
Making a brand film from code
How the 19.4-second wonmor brand film is generated from one timeline file: a canvas renderer for the MP4, a generated After Effects project, Blender for materials, synthesised sound and a web encode.
From zero to OpenSSF gold in under two days
bitg's repository was created on 11 November 2026 at 17:08 UTC. The project reached the OpenSSF Best Practices gold level 36 hours later. Most of the code-side criteria took hours; the hardest ones were about people, and one we marked wrongly before correcting it.
Reproducible MSI and .pkg builds, and the timestamp traps inside
Building the bitg installers twice from one commit used to give two different files. We removed the differences layer by layer: compiler, linker, WiX, the OLE container, and the xar archive behind every macOS package. The last four bytes were written by the very call that saved our fix.
- Making a brand film from code How the 19.4-second wonmor brand film is generated from one timeline file: a canvas renderer for the MP4, a generated After Effects project, Blender for materials, synthesised sound and a web encode.
- From zero to OpenSSF gold in under two days bitg's repository was created on 11 November 2026 at 17:08 UTC. The project reached the OpenSSF Best Practices gold level 36 hours later. Most of the code-side criteria took hours; the hardest ones were about people, and one we marked wrongly before correcting it.
- Reproducible MSI and .pkg builds, and the timestamp traps inside Building the bitg installers twice from one commit used to give two different files. We removed the differences layer by layer: compiler, linker, WiX, the OLE container, and the xar archive behind every macOS package. The last four bytes were written by the very call that saved our fix.
- Zero-downtime static deploys with Caddy A deploy used to restart the web server and cut off anyone downloading an installer. The replacement is small: release directories, one atomic rename, a validated config and a graceful reload. The details that make it work are about inodes, bind mounts and a Caddy setting we deliberately left out.
- Telegram HTML widgets in production What it took to ship two live HTML widgets in the dtwin Telegram bot: a 4 KB budget, a 1 KB state, a revision protocol between bot and chat, and a paint limit the documentation does not spell out.
- Lighthouse 55 → 100 without losing the wow How the Halvet concept site went from a mobile Lighthouse performance score of 55 to 100 in one release, then got a WebGL hero and a 3D scene back while staying at 99, and why the score did not stay there.
- Building a self-hosted tunnel How we built tunnel.dtwin.uz on frp: a small gateway that owns sign-in and subdomains, per-subdomain certificates issued before the link is shown, and a client that installs on networks where GitHub downloads stall.
- Mosques from OpenStreetMap: 2,285 congregations, one layer How dtwin imports every mosque in Uzbekistan from OpenStreetMap and keeps congregation times in a layer of their own, separate from the prayer-time calculation.
- Controlling Claude Code from Telegram A small Python bot turns a phone chat into a remote for Claude Code on a desktop: one headless process per message, hooks for notifications and approvals, and parallel slots. What we built in one day and what we learned about phone-sized requests.
- Making a brand film from code How the 19.4-second wonmor brand film is generated from one timeline file: a canvas renderer for the MP4, a generated After Effects project, Blender for materials, synthesised sound and a web encode.
- From zero to OpenSSF gold in under two days bitg's repository was created on 11 November 2026 at 17:08 UTC. The project reached the OpenSSF Best Practices gold level 36 hours later. Most of the code-side criteria took hours; the hardest ones were about people, and one we marked wrongly before correcting it.
- Reproducible MSI and .pkg builds, and the timestamp traps inside Building the bitg installers twice from one commit used to give two different files. We removed the differences layer by layer: compiler, linker, WiX, the OLE container, and the xar archive behind every macOS package. The last four bytes were written by the very call that saved our fix.
- Zero-downtime static deploys with Caddy A deploy used to restart the web server and cut off anyone downloading an installer. The replacement is small: release directories, one atomic rename, a validated config and a graceful reload. The details that make it work are about inodes, bind mounts and a Caddy setting we deliberately left out.
- Telegram HTML widgets in production What it took to ship two live HTML widgets in the dtwin Telegram bot: a 4 KB budget, a 1 KB state, a revision protocol between bot and chat, and a paint limit the documentation does not spell out.
- Lighthouse 55 → 100 without losing the wow How the Halvet concept site went from a mobile Lighthouse performance score of 55 to 100 in one release, then got a WebGL hero and a 3D scene back while staying at 99, and why the score did not stay there.
- Building a self-hosted tunnel How we built tunnel.dtwin.uz on frp: a small gateway that owns sign-in and subdomains, per-subdomain certificates issued before the link is shown, and a client that installs on networks where GitHub downloads stall.
- Mosques from OpenStreetMap: 2,285 congregations, one layer How dtwin imports every mosque in Uzbekistan from OpenStreetMap and keeps congregation times in a layer of their own, separate from the prayer-time calculation.
- Controlling Claude Code from Telegram A small Python bot turns a phone chat into a remote for Claude Code on a desktop: one headless process per message, hooks for notifications and approvals, and parallel slots. What we built in one day and what we learned about phone-sized requests.
Nothing matches your search
Try a shorter word, or clear the search to see every post.
Explore work from other areas
- Agents and MCP 3 posts How AI agents should reach real systems: one gateway with scoped tokens, masking, audit and a kill switch, and products that expose their own tools — 96 of them in dtwin alone.
- Language technology 2 posts Tools for writing Uzbek well on every device — starting with bitg, a keyboard that converts text to the 2026 Latin alphabet as you type, measured at 98.87% on a public evaluation set.
- Infrastructure and reliability 2 posts Running many small products on modest hardware without dropping requests: zero-downtime releases, self-hosted tunnels, status checks and restores that are actually tested.
- Supply-chain security 2 posts Making it possible to check that a download is exactly what the source code says: signed provenance, SBOMs, reproducible packages and the OpenSSF Best Practices gold badge for bitg.
- Interfaces and 3D 3 posts Interfaces people remember: 3D scenes that stay fast, a brand film rendered from code, and pages that score 100 on Lighthouse without losing their motion.
- Faith and society 2 posts Software that respects how people actually organise their day: a planner anchored to the five daily prayers, 2,285 congregations mapped from OpenStreetMap, and missed-prayer planning.
- Digital assets 1 post Should a community app have a token at all? Our answer is still no, for reasons of Uzbek law, platform rules and Islamic finance. What we kept from the technology instead are three planned open tools without tokens, each with a working in-browser demo today: Muhr for timestamp proofs, Sanad for verifiable certificates and Shaffof for verifiable charity reports.