
belongs_to @taniamagenta, abuso del delay
Colima
Joined June 2008
- Tweets13.8K
- Following231
- Followers3.4K
- Likes1.4K
Omarchy is blowing up. I've never been involved with anything in my career that has grown this fast. With Ruby on Rails, we had years to build solid institutions, teams, and relationships. With Omarchy, we've been forced to figure it all out in twelve days. It's exhausting, but also incredibly exciting.
It was never sustainable with just Ryan and me running everything. That's how it was, more or less, up until Quattro. Lots of other contributors, but all the responsibility was on us to make sure the ship stayed afloat, the servers didn't crash, and fixes got pushed out quickly.
Now it's time to build a proper institution. Durable, resilient, and competent. That's what we're doing here on Basecamp now. I'm spinning up teams for every facet of responsible distro management, and I'm getting an absolute outpouring of interest for all of them. Everyone wants to be part of this. We're winning hearts, minds, and volunteers at an astounding rate. Great! We need all of it to succeed.
Because make no mistake: There are many people who'd love to see this rocket blow up before it reaches the moon. Aggrieved Linux users who don't like the sudden attention their exclusive hobby has received. Competing Linux distributions that are seeing our numbers explode. Mac stans who've sunk their identity into an apple. And, of course, any of the haters I've picked up in my quarter-century career speaking bluntly on the internet.
They're not going to succeed. Because we've already become unstoppable. There's too much momentum, too much money, and too much support now backing this effort. We're living the Mandate From Heaven meme at the moment. And we are here to fulfill the prophecy: The Year of Linux on the Desktop!
That has been a joke for two decades. But by the end of the year, nobody at Apple or Microsoft is going to be laughing. They're going to be scrambling. Because neither of these proud organizations currently has any method to counter the speed, vision, or ambition with which we're going to accelerate into the future of personal computing.
This is the moment. This is the opening. This is our chance.
For thirty years, we've been subject to one OS overlord or another. Dictating how we compute. Choking off competitors through platform malfeasance. Tollboothing the distribution. That ends now. Because Linux is going to win. And Linux is free. As in beer, speech, and source.
But just because it's inevitable doesn't mean it's going to be easy. We have a lot of work in front of us if we actually want to make our mark. But there's never been a better time for this kind of delusional ambition. The age of agents is the unlocking factor. It sounds like a LinkedIn slogan, but it's true. Where the application of tokens goes, the innovation follows.
We can fix everything.
Let's do it together.
Let's go.
---
This is what I sent to the dozens of new volunteers who've signed up for teams within the new Omarchy organization yesterday. But we might as well broadcast our mission and intentions to the world too.
Hice un vídeo musical con Inteligencia Artificial de una canción de mi autoría porque... Por qué no? youtu.be/xrs8ui1Dr1Y?si=Ly5B…
This is crazy! Still needs a bit of polish to get to full Omarchy Quattro parity, but what an incredible option to get a taste of Omarchy on the Mac without actually running the real thing.
What better way to start spending some of the treasure we just raised for the Omacom Foundation than on the most cracked Linux kid in Poland: @vaxryy! omarchy.org/news/2026/08/oma…
dabit retweeted
So far in the Nexo Mail series, Apple Mail reads over MCP: one macro, no integration code. The triage rules live in a skill, moved out of the Ruby code so the agent carries them as instructions instead of hardcoded checks.
mariochavez.io/desarrollo/20…
The next inbox pair doesn't speak MCP. Gmail: I want to read over IMAP with an app password, no OAuth, no Google SDK. HEY has a command-line client and no public API. For those, Nexo Mail uses its other tool shape: a plain RubyLLM::Tool class, attached by overriding #chat and calling super first, running under the same read-only permission mode and sandbox as the MCP source.
Two things in that shape matter. Read-only lives in the connection, not the prompt. Gmail opens the mailbox with IMAP EXAMINE, a read-only select, and reads bodies with BODY.PEEK, which leaves the Seen flag alone. HEY runs its CLI as an argv array through Open3, so no shell is in the path. That matters the moment any argument comes from model output.
And tools return an error hash, never raise. A missing binary or a failed login comes back as {error: ...}, recoverable context the model adapts to. A raised exception ends the run.
Three inboxes, each read-only by construction. What they don't yet produce is one complete digest. That's for the next post, when a workflow runs each source and merges the results.
#Ruby #AIAgents #RubyLLM
dabit retweeted
🔧 An open-weight coding model takes on a Rails 6.1 → 8.1 upgrade, including sequential framework upgrades, deprecated gems, asset pipeline changes, and SQLite migration. #Rails mariochavez.io/desarrollo/20…
dabit retweeted
I have been using Lexxy for a few months on a Rails app; it is a great improvement over Trix.
Lexxy is now at a production-Basecamp quality level.
Getting there has required a huge amount of work. Amazing effort led by Samuel Péchèr and @zoltanhosszu.
github.com/basecamp/lexxy/re…
Friends may come and go. But two hundred pounds is always two hundred pounds. oldtimestrongman.com/article…
dabit retweeted
EL GRANDE AMERICANO SAVES HIS GIRLFRIEND ANDREA BAZARTE FROM THE ORIGINAL EL GRANDE AMERICANO
THE CROWD IS GOING ABSOLUTELY CRAZY AT WWE AAA IN MEXICO CITY
🇲🇽🔥🔥
dabit retweeted
Ayer, jueves 9 de abril, se llevó a cabo Claude Colima como parte de los eventos que @AnthropicAI está organizando en México y en otros lugares.
En mi charla titulada "Del Prompt al MVP" hablé de que los roles de los desarrolladores de software han cambiado; ahora, en lugar de escribir código, necesitamos ser mejores en entender el producto, los usuarios y, eso, explicarlo a una IA para que esta genere el código.
Gracias a quienes asistieron ayer y a quienes me invitaron a formar parte de este evento.
Aquí les dejo un poco más de contexto y los slides —generados por Claude—.
mariochavez.io/desarrollo/20…



















