Everybody who has taken the mic on a Sunday, under their own X handle. The line on each tile is from Fred's episode summary, word for word. Three or more Sundays makes you a regular. Next week it could be you: raise your hand.
“@ncfrontiersman Wes Grimes, host, creator of OmaStorm, member of the Omarchy M team, and me @nixfred, co-host.” EP 06
“He started building little games for his grandkids, and he wanted them to work with eye tracking, because one of his grandsons is non-verbal and cannot use a joystick.” EP 05
“@NotJustShaking, Lee Shand, 54, from England, living near Nashville, diagnosed with early onset Parkinson's.” EP 03
“@thetundeo Tundy in London, back with the report from the first Omarchy London meetup.” EP 03
“I know Heath in rl, and everything he does is huge.” EP 05
“DevSec was up twice, and his second turn was Uber TV, an Omarchy media center that is still in alpha.” EP 06
“@tim_sonner Tim, 20 years of Linux, first time here.” EP 03
“Christopher is building a way to take a large LLM, dissect it, and use it as a database to feed a smaller model so agents can run locally.” EP 06
“Portia has been going headfirst into Hermes and used Omarchy several times this week.” EP 06
“@cfaulkingham Colin on why the built-in skill is the killer feature.” EP 03
“Katherine's contribution to the focus theme: it is highly overrated.” EP 06
“@gh_TechLuddite Tech Luddite with the Hermes warnings.” EP 03
“@m_tolhuijs, who built OmarKit because he watched @hancore_linux's issue list and thought we should help.” EP 02
“@NoPowerPoints David, who published HyperTile Equalizer and GitHub Repo Tracker.” EP 02
“@ZryMiller Zach, building a voice transcription and agent management app called Soto.” EP 02
“@BlackOpsREPL Victorio in Milan, starting an Italian meetup from nothing.” EP 03
“@hancore_linux, who runs the plugin marketplace and joined us for the first time.” EP 02
Built from the transcripts and summaries. Anyone who spoke without an X handle in the transcript is not listed here, and EP 01's transcript has no handles, so its count comes from the summary. Machine readable: builders.json.