I feel sad for the people who will miss out on having children because of anti-family propaganda pushed by the left.
Humanity will collapse without increasing birth rates.
This is very late, but I'm finally done with my 5.5 vid
- use low reasoning
- the name sucks
- it's fast
- best code I've ever seen a model write came from this model
- openai's new pre-training is amazing
- price looks worse than it is
- over sensitive to every little thing in it's context window
- feels wildly different compared to 5.4
- turn reasoning off. try it. turn the reasoning off. do it.
We're open-sourcing Asimov v1, a humanoid robot.
With Asimov v1, you can build, train on, and make it your own humanoid robot. It's the first step of building a humanoid labor force for the rest of us.
Asimov v1 is 1.2 m tall, 35 kg, with 25 actuated degrees of freedom. Structural parts machined in 7075 aluminium and 3D-printed in MJF PA12 nylon.
We're releasing the mechanical design and simulation files. Ready for locomotion policy training out of the box.
The BOM is open too. Source everything yourself, or order the DIY Kit. All components, ready to assemble. $499 deposit, $15,000 target price. Ships end of summer 2026.
GitHub: https://t.co/kjqkny2oqW
Manual: https://t.co/9tjkteOcxO
DIY Kit: https://t.co/tzvzNyXQfA
Most humanoid robots are controlled by the companies that build them. Asimov v1 is built for the rest of us. Build it, test it, and share your feedback with the community.
Open source is dead.
That’s not a statement we ever thought we’d make.
@calcom was built on open source. It shaped our product, our community, and our growth. But the world has changed faster than our principles could keep up.
AI has fundamentally altered the security landscape. What once required time, expertise, and intent can now be automated at scale. Code is no longer just read. It is scanned, mapped, and exploited. Near zero cost.
In that world, transparency becomes exposure. Especially at scale.
After a lot of deliberation, we’ve made the decision to close the core @calcom codebase.
This is not a rejection of what open source gave us. It’s a response to what risks AI is making possible.
We’re still supporting builders, releasing the core code under a new MIT-licensed open source project called cal. diy for hobbyists and tinkerers, but our priority now is simple:
Protecting our customers and community at all costs.
This may not be the most popular call.
But we believe many companies will come to the same conclusion.
My full explanation below ↓
Introducing Gemma 4, our series of open weight (Apache 2.0 licensed) models, which are byte for byte the most capable open models in the world!
Gemma 4 is build to run on your hardware: phones, laptops, and desktops.
Frontier intelligence with a 26B MOE and a 31B Dense model!
This beaver was orphaned and rescued as a newborn,
Watch the incredible instinct to build a dam, even though it’s never seen it’s parents build one.
Placing SpongeBob at the front to absorb the water, damn he knows ball 😂
A user story is not a code word for specification or a requirement or any description of work. It is not a ticket. It is not a to-do item. It is not something you can build. The fact that the term has been corrupted by the Jira-slinging ticket-money pseudo-Agile Scrummy culture is a real shame, because it's a valuable concept:
A "user story" is literally the user's story. It is a description of a problem, not a solution. It is not a specification. It cannot be estimated. It's the topic of conversation that we have with our users/customers to understand their problems and collaboratively develop the smallest, best solution. The story is not the solution—it's the beginning of the conversation you have to arrive at the solution.
A story describes our users' work, not ours.
The idea is that the best software solves real problems that real people have, and that, by identifying those problems, we can build something that's actually useful. By working on the software one small problem at a time, we guarantee that every release does something useful.
People who talk about user stories being dead never understood what they were to begin with. You cannot build software without them.
A lot of people quote tweeted this as 1 year anniversary of vibe coding. Some retrospective -
I've had a Twitter account for 17 years now (omg) and I still can't predict my tweet engagement basically at all. This was a shower of thoughts throwaway tweet that I just fired off without thinking but somehow it minted a fitting name at the right moment for something that a lot of people were feeling at the same time, so here we are: vibe coding is now mentioned on my Wikipedia as a major memetic "contribution" and even its article is longer. lol
The one thing I'd add is that at the time, LLM capability was low enough that you'd mostly use vibe coding for fun throwaway projects, demos and explorations. It was good fun and it almost worked. Today (1 year later), programming via LLM agents is increasingly becoming a default workflow for professionals, except with more oversight and scrutiny. The goal is to claim the leverage from the use of agents but without any compromise on the quality of the software. Many people have tried to come up with a better name for this to differentiate it from vibe coding, personally my current favorite "agentic engineering":
- "agentic" because the new default is that you are not writing the code directly 99% of the time, you are orchestrating agents who do and acting as oversight.
- "engineering" to emphasize that there is an art & science and expertise to it. It's something you can learn and become better at, with its own depth of a different kind.
In 2026, we're likely to see continued improvements on both the model layer and the new agent layer. I feel excited about the product of the two and another year of progress.
I own a small bakery. Business has been slow. Rent is up. I was thinking about closing.
Last Friday, a teenager came in. He looked nervous. He counted out change for a cookie. He was short 50 cents.
"It's okay," I said. "Take it."
He ate it at a table, looking at his math homework. He looked stuck.
I used to be a math tutor.
I walked over. "Quadratic equations?"
He nodded. "I don't get it."
I sat down and helped him for 20 minutes. He got it. He left smiling.
The next day, he came back with two friends. They bought cookies.
The day after that, five kids came.
Apparently, he told the school, "The lady at the bakery helps with homework."
Now, my bakery is the after-school hang-out spot. It's loud. It's messy. There are backpacks everywhere.
Yesterday, I found a note in the tip jar. It was wrapped around a $20 bill.
"Thanks for helping my son pass math. A Mom."
I'm not closing the bakery.
I think I finally found my purpose.
It's not cookies. It's community.
@NickMilo@arscontexta you can do a lot with existing open source tools.
look at nginx-vod module by kaltura and shaka player, developed by Google (used for YouTube).
if you don't have massive amounts of users, you can quite easily get YouTube like user experience.
Required reading for Clawd. There is a HUGE RISK and ATTACK vector with a bot.
This is my biggest concern. Do not use on your primary machine with all your credentials, passwords, private keys, etc.
This is it. The most important video you'll watch this year.
ClawdBot has taken X by storm. And for good reason. It's the greatest application of AI ever
Your own 24/7 AI employee
In this video I cover how it works, how to set it up, and why I think we should all be nervous:
Wow, did not expect that from a food corner documentary. I got emotional, seeing this much passion, love and effort put into something mundane everyday. It somehow touches me deeply. With that example, we can turn around the world!
https://t.co/sM9GXcHqkx
@aljazkosirnik Thanks for this insight. I had the same idea (use custom webhook-listening service to integrate opencode in gitlab). I was sure I'm not the only one, so I searched on X and found you. looking forward to work on that approach.