Engineering
New Features
- Service worker now supports switching between multiple tonks
- Tonk launcher and desktonk added to the repository. If you are curious to try out a prototype, this would be a good place to start.
Bug Fixes and Improvements
- Service Worker stability and performance has improved A LOT
- Better JS builds all using Bun
- Stable Branch
Works in Progress
- Our sharing and permissioning system will use Dialog DB, so we’ve been working with the Dialog team to make the integration happen.
Product
We have talked to many of you this year about your day-to-day needs, and what you wish Tonk could help you with. What we heard confirmed what we know: collaboration across teams, especially teams from different organizations or teams with no formal organization at all, is still a huge pain. Our lives – both personal and professional – don’t always neatly fit into structures with a single owner. To achieve meaningful collaboration, teams need a shared infrastructure that respects governance and transparency. We call this usage pattern horizontal collaboration.
We imagine Tonk as a substrate that groups can rely on to capture and generate shared, local knowledge. This knowledge is co-owned and maintained by the group, and the data model reflects that.
Our current vision is to make it easy for people to gather in a shared space and to collaborate directly. That includes simple file-sharing and note-taking. Next, we want to offer people different ways to make their space their own, by adding custom apps, styling, and tailored community rules. Ultimately, Tonk should serve your community as invisible infrastructure: something that just works and allows you to make it your way.
We are now continuing to iterate on Tonk with internal testers. If you would like to be an internal tester please come talk to us!