This looks pretty cool. I’ve been using Claude Code a lot lately and once you start trying a few things in parallel it gets messy fast — multiple terminals, different branches, remembering which session was doing what, etc.
Wrapping worktrees + sessions into one place with some common actions actually seems pretty useful. Curious to try it out and see how it feels in practice.
If this is Twilio powered, and uses Twilio conferences, it would be limited to 250 participants which seems low for a radio platform. https://www.twilio.com/voice/conference
"An angle grinder or drill bit will cut through the outer layer of a Proteus plate, but once it reaches the embedded ceramic spheres, the fun begins with vibrations that blunt the tool's sharp edges, and then fine particles of ceramic dust begin filling up gaps in the matrix-like structure of the metal."
You should read more about how to build an application on Android, at least in terms of defining UI. I am tempted to try to create a UI framework that can parse these same xml documents and create iPhone UI.
Yeah, we go back and forth on that. We only use it currently to send you a confirmation. You can still login immediately though. OpenID is definitely in the road map.
I suppose we could allow you to login to a more restricted account (no spamming since we do have email/sms out support) until you validate in some way.
The problem with a wiki, from my perspective, is the fact that it is unstructured. Some wiki's attempt to derive structure, or force users to use special syntax but that ends up being a little clunky. With structure comes some power. Tasks suddenly have meaning. A "Restaurant" data type can associate a map, or reviews. What we are trying to create is almost a personal content management system that helps users track all of that interesting structured data.
Wrapping worktrees + sessions into one place with some common actions actually seems pretty useful. Curious to try it out and see how it feels in practice.