The running history of the weekly Omarchy X Space. What got said, who said it, and the questions nobody has answered yet. Every episode: the summary as posted on X and the full transcript.
Open X on Sunday at 3pm Eastern and look for the Space on @ncfrontiersman or @NixFred. Raise your hand, tell us what you're building, tell us where you're stuck. Everything is recorded; if you speak, you consent. Summaries land here after each episode.
If X drops the room, close your browser and rejoin. It puts speakers back automatically.
@NotJustShaking, Lee Shand, has early onset Parkinson's, and he opened the room by explaining how Omarchy and an AI-maintained Obsidian vault give him back the memory the disease took. Then the room filled up: @thetundeo's London meetup report, a Milan meetup starting from scratch, @tylermayberry's Ibara, a retired engineer printing Lego bricks from a CAD MCP server, a man running his home lab from a boat, and a long practical thread on Hermes, Kanban agents and the built-in Omarchy skill.
What a plugin actually is, how you clone one and make it yours, and how you publish it. The marketplace maintainer @hancore_linux dropped in with news of a new submission system. @m_tolhuijs shipped OmarKit to run the marketplace pipeline on your own machine, @cfaulkingham reported back honestly from trying to fine tune a local Omarchy model, @thetundeo explained how he started the London meetup by just doing it, and @MuchmoreIT is working toward a federal grade Omarchy. Plus the elephant in the room: the Arch crowd, the walls, and where the frontier actually went.
First episode. OmaStorm's origin, Blip and the memory problem, Tech Luddite on three years fighting AI, Tundy's London meetup, the Omarchy Guild, small local models versus a troubleshooting corpus, Apple Silicon and big iron, and the twelve questions nobody has answered yet.