Blog

From infrastructure
to real-world AI.

Tech

Apr 6, 2026

We Found a Ticking Time Bomb in macOS TCP Networking - It Detonates After Exactly 49 Days

Every Mac has a hidden expiration date. After exactly 49 days, 17 hours, 2 minutes, and 47 seconds of continuous uptime, a 32-bit unsigned integer overflow in Apple's XNU kernel freezes the internal TCP timestamp clock. Once frozen, TIME_WAIT connections never expire, ephemeral ports slowly exhaust, and eventually no new TCP connections can be established at all. ICMP (ping) keeps working. Everything else dies. The only fix most people know is a reboot. We discovered this bug on our iMessage service monitoring fleet, reproduced it live on two machines, and traced the root cause to a single comparison in the XNU kernel source. This is the full story.

Tech

Apr 6, 2026

We Found a Ticking Time Bomb in macOS TCP Networking - It Detonates After Exactly 49 Days

Every Mac has a hidden expiration date. After exactly 49 days, 17 hours, 2 minutes, and 47 seconds of continuous uptime, a 32-bit unsigned integer overflow in Apple's XNU kernel freezes the internal TCP timestamp clock. Once frozen, TIME_WAIT connections never expire, ephemeral ports slowly exhaust, and eventually no new TCP connections can be established at all. ICMP (ping) keeps working. Everything else dies. The only fix most people know is a reboot. We discovered this bug on our iMessage service monitoring fleet, reproduced it live on two machines, and traced the root cause to a single comparison in the XNU kernel source. This is the full story.

Tech

Apr 6, 2026

We Found a Ticking Time Bomb in macOS TCP Networking - It Detonates After Exactly 49 Days

Every Mac has a hidden expiration date. After exactly 49 days, 17 hours, 2 minutes, and 47 seconds of continuous uptime, a 32-bit unsigned integer overflow in Apple's XNU kernel freezes the internal TCP timestamp clock. Once frozen, TIME_WAIT connections never expire, ephemeral ports slowly exhaust, and eventually no new TCP connections can be established at all. ICMP (ping) keeps working. Everything else dies. The only fix most people know is a reboot. We discovered this bug on our iMessage service monitoring fleet, reproduced it live on two machines, and traced the root cause to a single comparison in the XNU kernel source. This is the full story.

Customer Story

Mar 14, 2026

How MimiClaw Put a Pocket AI Assistant on iMessage

MimiClaw built a personal AI assistant that runs on a $5 chip. With Photon, it now lives natively in iMessage - the app 1.3 billion people already text from every day

Customer Story

Mar 14, 2026

How MimiClaw Put a Pocket AI Assistant on iMessage

MimiClaw built a personal AI assistant that runs on a $5 chip. With Photon, it now lives natively in iMessage - the app 1.3 billion people already text from every day

Tech

Jan 29, 2026

CI/CD in the Age of AI

At Photon, we only hire 10x engineers. We shipped a full SDK in a week, then built the infrastructure to support it in a month. That kind of work usually takes big companies a year. But as we moved faster, one thing started slowing us down: the CI/CD pipeline—releases, versioning, testing, and binary builds. In 2026, we're writing software at a speed we never imagined possible, but our CI/CD is still stuck in 2015.

Tech

Jan 29, 2026

CI/CD in the Age of AI

At Photon, we only hire 10x engineers. We shipped a full SDK in a week, then built the infrastructure to support it in a month. That kind of work usually takes big companies a year. But as we moved faster, one thing started slowing us down: the CI/CD pipeline—releases, versioning, testing, and binary builds. In 2026, we're writing software at a speed we never imagined possible, but our CI/CD is still stuck in 2015.

Interaction

Jan 7, 2026

Frontier Agent Interaction on iMessage: Tech Overview

At Photon, we keep asking ourselves a simple question: what should AI and agents actually look like in the future? Will we really open a browser, type in a URL, and use agents as if they were just another SaaS tool? Will we download yet another app just to “chat with an AI boyfriend or girlfriend”? This feels unexciting and it certainly does not match the futures we see in sci-fi scenes. We believe that in the world we are heading toward, AI should not appear as a “feature” or a “tool.” It should feel like a type form of life, deeply woven into our social structures. Our kids will not be surprised when they see AI as we were. They will not treat it as a cold, external program as we treat our macs and phones. They will look at AI the same way they look at friends and classmates. In that world, AI becomes a first‑class citizen in our society. With that in mind, we started asking what we can build today that moves us in that direction. One answer we kept coming back to was iMessage. In the United States, almost everyone uses iMessage every day. Millions of messages flow through it constantly. It might be the most natural and native interaction surface for agents in this era: the agent shows up in your conversation list like a friend, and even joins your group chats. So we decided to turn this idea into reality and build infrastructure that lets AI exist in a truly “human” way inside iMessage. That is how we arrived at imessage-kit - an open‑source TypeScript SDK for controlling iMessage. It lets developers send, receive, and orchestrate iMessage messages through code. Along the way, we had to work through a lot of technical constraints and ended up re‑imagining how AI can communicate with people. This blog focuses on the technical side of that journey: how iMessage works under the hood, what it takes to build a reliable SDK around it, and how that unlocks new interaction patterns for agents. We will save more speculative interaction design and UX experiments for future posts.

Interaction

Jan 7, 2026

Frontier Agent Interaction on iMessage: Tech Overview

At Photon, we keep asking ourselves a simple question: what should AI and agents actually look like in the future? Will we really open a browser, type in a URL, and use agents as if they were just another SaaS tool? Will we download yet another app just to “chat with an AI boyfriend or girlfriend”? This feels unexciting and it certainly does not match the futures we see in sci-fi scenes. We believe that in the world we are heading toward, AI should not appear as a “feature” or a “tool.” It should feel like a type form of life, deeply woven into our social structures. Our kids will not be surprised when they see AI as we were. They will not treat it as a cold, external program as we treat our macs and phones. They will look at AI the same way they look at friends and classmates. In that world, AI becomes a first‑class citizen in our society. With that in mind, we started asking what we can build today that moves us in that direction. One answer we kept coming back to was iMessage. In the United States, almost everyone uses iMessage every day. Millions of messages flow through it constantly. It might be the most natural and native interaction surface for agents in this era: the agent shows up in your conversation list like a friend, and even joins your group chats. So we decided to turn this idea into reality and build infrastructure that lets AI exist in a truly “human” way inside iMessage. That is how we arrived at imessage-kit - an open‑source TypeScript SDK for controlling iMessage. It lets developers send, receive, and orchestrate iMessage messages through code. Along the way, we had to work through a lot of technical constraints and ended up re‑imagining how AI can communicate with people. This blog focuses on the technical side of that journey: how iMessage works under the hood, what it takes to build a reliable SDK around it, and how that unlocks new interaction patterns for agents. We will save more speculative interaction design and UX experiments for future posts.

Weekly updates from the edge.

Weekly updates from the edge.

Weekly updates from the edge.