Reactions from ranked influencers
8 posts
Salute to Sunday folks 🫡 It is amazing as well as interesting to see how much solid engineering is needed for smooth and reliable deployment
We just hit a weird milestone: our model became more reliable than your average home WiFi. Just like everybody else, we thought cloud inference was the obvious choice. Yet 2 days into the ACT-2 eval, our mind completely changed. If our hero @ArpitKalla didn’t cook, this video wouldn’t exist 🧵
Fundamentally i do think it will be hard to be a cloud-based token merchant, in the openai and anthropic mould, with mcuh of robotics
@tonyzzhao we forgot to connect Memo to the wifi! Oh wait we don’t need it. We moved our robot policy to run completely on-device. Why? Because “works great until the WiFi hiccups” is not an acceptable failure mode for a robot operating in your home. Local inference: predictable latency, no surprises.
If you are thinking whether there will be a "model API" for home robotics, read this tweet from our CTO.
We just hit a weird milestone: our model became more reliable than your average home WiFi. Just like everybody else, we thought cloud inference was the obvious choice. Yet 2 days into the ACT-2 eval, our mind completely changed. If our hero @ArpitKalla didn’t cook, this video wouldn’t exist 🧵
Your laundry should not depend on your WiFi.
We just hit a weird milestone: our model became more reliable than your average home WiFi. Just like everybody else, we thought cloud inference was the obvious choice. Yet 2 days into the ACT-2 eval, our mind completely changed. If our hero @ArpitKalla didn’t cook, this video wouldn’t exist 🧵
Fundamentally i do think it will be hard to be a cloud-based token merchant, in the openai and anthropic mould, with mcuh of robotics
@tonyzzhao we forgot to connect Memo to the wifi! Oh wait we don’t need it. We moved our robot policy to run completely on-device. Why? Because “works great until the WiFi hiccups” is not an acceptable failure mode for a robot operating in your home. Local inference: predictable latency, no surprises.
"We realized that this problem only became visible once three things were true at the same time: 1. Memo was fully autonomous. 2. We were evaluating it in real, unseen homes. 3. The policy was reliable enough that network jitter became a dominant failure mode."