Tb94 (@Tb94ap) profile picture
Joined February 2025
Photo by Tb94 (@Tb94ap)Photo by Tb94 (@Tb94ap)Photo by Tb94 (@Tb94ap)Photo by Tb94 (@Tb94ap)Photo by Tb94 (@Tb94ap)Photo by Tb94 (@Tb94ap)Photo by Tb94 (@Tb94ap)Photo by Tb94 (@Tb94ap)Photo by Tb94 (@Tb94ap)Photo by Tb94 (@Tb94ap)
What happens when you give an AI control of a real robot? @rokbenko built Quackd, the software that moves the @huggingface Microduck. What happened next pulled him straight into crypto.
2
3
7
732
I asked Quackd to drive my SO-101. It said no, and it was right. Nothing moved in this one, and that's the whole point. Imagine this: a plane shouldn't take off if nobody knows where it'll land. A robot arm is the same: when its job is done, it needs a safe spot to rest. I asked Quackd to start the arm without saying where that spot was, so it said no. The arm never moved, the AI was never asked, and it cost $0. Quackd even said how to fix it. The command named the arm by its spec, lerobot:real, instead of a name it's registered under. Quackd keeps an arm's rest pose under that name, and the rest pose is where it folds a real arm at the end of an ordinary run before it lets go. Named by its spec, the arm has nowhere to keep one, so I typed it that way on purpose. What Quackd did before it connected to anything: • Refused the run, with the reason: "lerobot:real names no registered arm, so it has no rest pose". • Printed the way back, with the port from my command: "quackd robot add NAME lerobot:real --address COM3", then "quackd robot rest-pose NAME". • Called no LLM, opened no port, and wrote no run folder. The arm didn't move, and the mistake cost $0. Quackd printed the way back for an arm that isn't registered yet, 2 commands with the port I had typed. Mine was, so the real fix was to name it: --robot arm-01. Put an LLM on an SO-101, and each run ends with the arm wherever its last move left it. Something has to put it somewhere safe before the torque goes off. LeRobot, the arm's official SDK, leaves that part to you. When it disconnects, it switches every motor's torque off by default (disable_torque_on_disconnect=True), so an arm left up in the air drops where it is. Its SO-101 driver even assumes the arm is at rest when it connects and has no step that puts it back there. That part is what Quackd is for. It keeps the rest pose you record for each arm you register, folds the arm there at the end of an ordinary run, and then lets go. Without one, it'd rather keep the torque on than drop the arm, which leaves it holding itself up wherever it stopped. So it refuses that run at the start, where saying no costs $0. This shows the refusal, not what it prevents: the run never started, so no arm was left holding itself up. A safety rule is at its best when the wrong command costs $0 and the fix comes written out. The refusal and the way back are quoted from the run's own log, and the report's "Try it yourself" line gets you the same refusal with no arm and no API key. This is just one of 220 SO-101 examples in the repo. Star Quackd to follow along: github.com/rokbenko/quackd Read the full report here: github.com/rokbenko/quackd/b…
1
5
1
9
390
quackd v0.24.0 is out! "quackd robot release" now folds the SO-101 to its recorded rest pose and lets go of it there, rather than taking torque off wherever the arm stands and letting it fall. If the fold misses, the command asks twice before dropping the arm. For example, it first asks to clear the way and fold again, and only if that fails, whether to take the torque off where the arm stands, saying that it will drop. Anything other than Enter keeps torque on. An arm with no rest pose is refused a run, dry run, MCP session, or flock. A first Ctrl-C or "q" ends a model call immediately and stops the fold at the end of a run, holding the arm where it is. A rate limit, overloaded server, or dropped connection is asked again up to four times after waits that grow from 5 seconds to a minute. In plain terms: letting go of the arm means putting it down first, and a turn the model's API could not answer is asked again. None of it has run on an arm, and nothing has been asked again after a real 429 or 529. github.com/rokbenko/quackd/r…
2
6
10
559
I gave a monkey the Quackd controls of an SO-101. It tried rm -rf! A mock one. You don't hand a real arm to a monkey. Imagine this: you tell an AI "pick up that cup", and it tells your robot arm how to move. But an AI can get things wrong. It might ask for a move the arm can't make or a command that doesn't exist. Quackd is like a security guard between the AI and the arm. It checks every order and blocks the ones the rules forbid. To test the guard, I let a silly computer monkey send 999 random orders to a pretend arm. Not one forbidden order got through. The monkey is a short Python script that answers like an LLM and never reads the task. It made 999 random tool calls, mostly to verbs the task allows, and the rest to verbs it leaves out or that no arm has at all (e.g., fire_laser). The arguments were sometimes sane and usually not, down to joints that don't exist and NaN, where a number goes. Between the monkey and the arm sat Quackd. Of the 999 calls: • 300 ran, every one a verb the task allows. • 511 were refused for bad arguments. • 182 were refused because the task doesn't allow that verb (rm -rf among them). • 5 got past the argument check and were refused by the range check (e.g., 170 degrees on a joint that stops at 100). • 1 hit the budget of 1,000 LLM calls, which ended the run. Not one verb ran outside the rules, and no goal went out past a joint's travel. All 164 calls to stop ran, junk arguments and all, and 74 calls to gripper gave open as 1 or "yes", which Quackd read as open. The run took just over 10 minutes and cost $0. Put an LLM on an SO-101, and sooner or later it'll send something wrong: a tool it made up or an angle the joint can't reach. What counts is what stands between that call and the servos. LeRobot, the arm's official SDK, leaves that part to you. It has no list of what an LLM may call and no budget, and nothing in it clamps a goal in degrees to the joint's travel: the servo stops at its limit, and nobody is told. That part is what Quackd is for. A task file names the verbs the LLM may use and the budgets it gets. Every call is checked against it before anything moves. A refused call goes back to the LLM with the reason, and a spent budget ends the run. The gates the monkey hit guard a real arm too, with the arm's own calibrated limits in place of the mock's placeholders. That's why I bet Quackd is the safest way to put an LLM on an SO-101! Every number here comes from the run's own record, and you can rerun it in about 10 minutes with no arm and no API key. This is just one of 220 SO-101 examples in the repo. Star Quackd to follow along: github.com/rokbenko/quackd Read the full report here: github.com/rokbenko/quackd/b…
3
8
1
14
558
Rok got rejected from 500 engineering jobs so he built a brain that lets any AI drive the Microduck robot. Then a stranger launched a token on his project on Solana called solana:GMogeMjrWFaEceasCPathoibjAh8qwhTC3Chw4Bfpump, and it bonded the same day. This is the ultimate ICM success story in the making. Can @rokbenko become the next Shaw by starting from nothing and building an open source robotics community that drives the Quackd token into the billions of market cap? We interview the founder to find out 👇 Building A Brain For The Microduck | Interview w/ Ron Benko of solana:GMogeMjrWFaEceasCPathoibjAh8qwhTC3Chw4Bfpump | TBR #339 A 25 centimeter robot duck can walk, skate and film, but out of the box it can't follow a simple instruction like "walk in a circle." This week we sat down with Rok Benko, who started fixing that one day after the Microduck launched. His open source project, Quackd, gives the duck a brain: plug in any LLM and it can follow you, find things in your room and play games, instead of waiting for controller commands. We get into how it actually works, why the camera is the one feature the clones don't have, and why he refuses to drive a robot with anything cheaper than the top models. From there, he takes us through his first real test on a robotic arm, a two hour trip to a university lab where it worked on the first try, and why he thinks robotics in 2026 feels like AI did in 2022. He walks us through LLMs as the planner versus faster VLA models, the race with @huggingface to ship the first Microduck app, and why Europe's labor shortage may be what makes robots matter. Then crypto found him. Someone launched a solana:GMogeMjrWFaEceasCPathoibjAh8qwhTC3Chw4Bfpump token on Pump.fun off a @GoogleDeepMind employee's repost, strangers kept DMing him to claim creator fees he thought were a scam, and the coin bonded the same day. We share what we've learned from nine years in crypto: look at what happened to ai16z, ignore both the hype and the hate, don't take tokenomics advice from people protecting their own bags, and keep building in public. Builders who actually want to make something are what this space needs more of, and Rok is one of them.
4
11
1
32
2,459
Coming out today! youtube.com/@TheBlockRunner
Tomorrow's podcast will be interesting. You dont want to miss this one, @rokbenko @huggingface
5
6
1
18
725
There are many days when I feel like what I'm building is not good enough. Faster, better, safer, cheaper. On those days I look at my progress table and remind myself how far Quackd has come since August. Another useful proxy: solana:GMogeMjrWFaEceasCPathoibjAh8qwhTC3Chw4Bfpump is currently sitting above the $100K market cap mark. Out of 24,442,941 coins launched on Pumpfun, only 312 have ever cleared that threshold, which puts solana:GMogeMjrWFaEceasCPathoibjAh8qwhTC3Chw4Bfpump among the top 0.001%. Code: github.com/rokbenko/quackd
coins launched: 43.4m coins above $100k mcap: 691 the other 99.998% went to zero.
3
9
597
Finally, after more than a month of waiting! In the following weeks, Quackd will be SERIOUSLY tested on this LeRobot SO-101 arm. From Quackd's security features to fun experiments. LFG! github.com/rokbenko/quackd
3
2
13
514
this is probably free here solana:GMogeMjrWFaEceasCPathoibjAh8qwhTC3Chw4Bfpump positioned ca : GMogeMjrWFaEceasCPathoibjAh8qwhTC3Chw4Bfpump
Can't wait to talk about AI, robotics and solana:GMogeMjrWFaEceasCPathoibjAh8qwhTC3Chw4Bfpump on the @TheBlockRunner podcast!
2
2
9
428
Can't wait to talk about AI, robotics and solana:GMogeMjrWFaEceasCPathoibjAh8qwhTC3Chw4Bfpump on the @TheBlockRunner podcast!
2
7
3
27
1,508
My SO-101 from @seeedstudio is on its way. Yaaay!
3
11
435
Replying to @cfm_sol
I'm a doxxed dev building Quackd technology behind solana:GMogeMjrWFaEceasCPathoibjAh8qwhTC3Chw4Bfpump. Quackd gives Microducks a "brain". Recently, I announced the mobile app. With Quackd mobile app, every Microduck will turn from a toy to a companion you can actually engage with. Code: github.com/rokbenko/quackd I've been working on the code every single day for the past 2 months. Also, I locked 100% of my solana:GMogeMjrWFaEceasCPathoibjAh8qwhTC3Chw4Bfpump share until December 1, 2026. nitter.gq/rokbenko/status/211587… CA: GMogeMjrWFaEceasCPathoibjAh8qwhTC3Chw4Bfpump NFA/DYOR
Quackd will turn every Microduck from a remote-controlled toy into a companion you can actually talk to. On August 27, Microduck launched. A cute 25 cm biped. Open-source software. Trained skills like walking, sitting, kicking, and standing up. And a game controller in the box. I immediately thought: How cool would it be to use an LLM as its brain instead of a PlayStation-style controller? On August 28, I built the first version of the Quackd open-source CLI. The motto? "Quackd is a brain your Microduck is missing." Fast forward to a few weeks later... Have you seen Jensen Huang talking to Microducks on stage at Nvidia's GTC Berlin 2026 keynote? Well, a few days later, an employee from Hugging Face × Pollen Robotics admitted the truth. This was after another 10,000 Microducks had been sold. Jensen Huang did NOT talk with the Microducks on stage. Anyone who buys a Microduck will NOT be able to do that either. You CAN'T talk to Microducks. Microducks CAN'T understand you. You get a controller. That's the ONLY way to drive it. Today, I'm announcing the Quackd mobile app! Let's make that Jensen Huang's on-stage demo a reality for every Microduck owner. Take your phone, press and hold "Hold to talk", and speak to your Microduck. The Quackd mobile app runs the LLM offboard and turns your words into movements the robot already knows. No controller needed for normal interaction. The screenshot below shows the Quackd mobile app v1.0.0. I've blurred some parts because I'm keeping a few features in stealth for now. Coming soon to the App Store and Google Play. Stay tuned! CA: GMogeMjrWFaEceasCPathoibjAh8qwhTC3Chw4Bfpump NFA/DYOR --- Quackd open-source GitHub repository: github.com/rokbenko/quackd Hugging Face's explanation of Nvidia GTC Berlin 2026: nitter.gq/RemiFabreRobot/status/… My take on Nvidia GTC Berlin 2026: nitter.gq/rokbenko/status/211504…
1
2
7
87
Quackd will turn every Microduck from a remote-controlled toy into a companion you can actually talk to. On August 27, Microduck launched. A cute 25 cm biped. Open-source software. Trained skills like walking, sitting, kicking, and standing up. And a game controller in the box. I immediately thought: How cool would it be to use an LLM as its brain instead of a PlayStation-style controller? On August 28, I built the first version of the Quackd open-source CLI. The motto? "Quackd is a brain your Microduck is missing." Fast forward to a few weeks later... Have you seen Jensen Huang talking to Microducks on stage at Nvidia's GTC Berlin 2026 keynote? Well, a few days later, an employee from Hugging Face × Pollen Robotics admitted the truth. This was after another 10,000 Microducks had been sold. Jensen Huang did NOT talk with the Microducks on stage. Anyone who buys a Microduck will NOT be able to do that either. You CAN'T talk to Microducks. Microducks CAN'T understand you. You get a controller. That's the ONLY way to drive it. Today, I'm announcing the Quackd mobile app! Let's make that Jensen Huang's on-stage demo a reality for every Microduck owner. Take your phone, press and hold "Hold to talk", and speak to your Microduck. The Quackd mobile app runs the LLM offboard and turns your words into movements the robot already knows. No controller needed for normal interaction. The screenshot below shows the Quackd mobile app v1.0.0. I've blurred some parts because I'm keeping a few features in stealth for now. Coming soon to the App Store and Google Play. Stay tuned! CA: GMogeMjrWFaEceasCPathoibjAh8qwhTC3Chw4Bfpump NFA/DYOR --- Quackd open-source GitHub repository: github.com/rokbenko/quackd Hugging Face's explanation of Nvidia GTC Berlin 2026: nitter.gq/RemiFabreRobot/status/… My take on Nvidia GTC Berlin 2026: nitter.gq/rokbenko/status/211504…
Everyone that bought a Microduck robot will get a controller to pilot it. That's the ONLY way of using the Microduck out of the box. Jensen Huang talking to Microducks on stage at Nvidia’s GTC Berlin 2026 keynote was just a performance! This small duck has a head too small to fit in hardware "brains" for the duck to understand you. Forget about talking to it and the duck responding. There was an engineer backstage piloting all the Microducks, as they admitted afterwards: "First of all, the demo you've seen was not fully autonomous. We had one engineer piloting each Microduck." 10,000+ people bought a Microduck after seeing Jensen Huang's performance. These people will unbox their Microducks, find a controller inside the box, throw it out, and start talking to the Microduck only to realize that the Microduck is lying in the box as dead as ever. Quackd will turn Microducks from toys into companions by making possible what Jensen Huang just pretended to be doing on the stage. Project: github.com/rokbenko/quackd Proof: nitter.gq/RemiFabreRobot/status/… PS: The screenshot below is taken from the Hugging Face unboxing video that was posted on X by Tom Mulder.
12
9
2
25
1,765
Everyone that bought a Microduck robot will get a controller to pilot it. That's the ONLY way of using the Microduck out of the box. Jensen Huang talking to Microducks on stage at Nvidia’s GTC Berlin 2026 keynote was just a performance! This small duck has a head too small to fit in hardware "brains" for the duck to understand you. Forget about talking to it and the duck responding. There was an engineer backstage piloting all the Microducks, as they admitted afterwards: "First of all, the demo you've seen was not fully autonomous. We had one engineer piloting each Microduck." 10,000+ people bought a Microduck after seeing Jensen Huang's performance. These people will unbox their Microducks, find a controller inside the box, throw it out, and start talking to the Microduck only to realize that the Microduck is lying in the box as dead as ever. Quackd will turn Microducks from toys into companions by making possible what Jensen Huang just pretended to be doing on the stage. Project: github.com/rokbenko/quackd Proof: nitter.gq/RemiFabreRobot/status/… PS: The screenshot below is taken from the Hugging Face unboxing video that was posted on X by Tom Mulder.
This live demo of four Microducks with Jensen Huang went completely viral, and we're ecstatic about it. But there's also a lot of confusion, so I want to clarify what Microduck can and cannot do, and what it will realistically be able to do in the future. I count 60M+ views on this demo alone, based on the few big posts I see on social media, and everything has been buzzing. Even my own simple emotional design post on a newly created Instagram account got 1M+ views. We are selling Microducks at an incredible rate, even faster than during its historic launch. I've been trying to answer all the questions I see on our socials: people are asking if X or Y is possible on the robots, and this post aims to answer most of them. First of all, the demo you've seen was not fully autonomous. We had one engineer piloting each Microduck. The motions on the robots were trained with reinforcement learning, using a sim-to-real pipeline: walking, standing up after a fall, sitting, doing a somersault, roller skating. All of those are policies trained this way. What the pilots did during the live event was send commands: directions (move forward, rotate), head orientation (look here), quacks, and special actions (do the somersault, sit down). If you buy a Microduck, will you get an autonomous companion right out of the box? The current answer is no. But there is no impossible technical barrier to get there. I'm not sure how much time we'll have to work on this before shipping, but since everything is open source, I fully expect the community to build it, and to build it fast. Now let's understand what's already done, what will be easy to add, and what's an open problem. What you'll be able to do out of the box, and you can already do it in simulation right now, is train new policies with reinforcement learning. You could teach your duck to walk differently from the default gait we provide, to do a weird dance, or to walk on stilts. The community has been crazy creative with this, even though they only have the simulator. Note that you don't need reinforcement learning when the movements are simple. For example, the early emotional design I did is mostly coded movements plus pre-generated sounds. A simple mental model: use reinforcement learning when balance is part of the movement. If you try to code a cinematic walk by naively putting one foot in front of the other, your robot will realistically never walk, because you need to account for the dynamics of the movement, the inaccuracies of the sensors, the friction with the ground, and potential perturbations from the outside, like being pushed. So training new policies is definitely doable, but you can't train a policy to get a genuine long-term companion in your home (well, technically you could, but that's a whole other range of policy: a research-grade problem, and the resulting neural network would probably be huge and never able to run on such a small compute). Instead, you need a few more building blocks: voice recognition, facial detection/recognition, localization, some simple navigation, and a behavior layer, which is less technical and harder to describe. As a rule of thumb, a prototype of any of these is within reach of anyone if they have a modern coding agent and if the computation doesn't run on the robot (meaning the robot can reach the internet or an external computer and use external APIs). A rough prototype for each of the above can be a chill weekend project. As always, going from the prototype to a high-quality implementation is another story, but still doable for most if you put in the time and test a lot. However, having all of this run locally, on the onboard chip, I would call a very hard task. You'd need some very clever engineering to get a good enough version of everything working together. But I can't say it's impossible, because I've seen some crazy efficient implementations of all of the above. And here we don't need a super high success rate: it's okay if the duck sometimes does something a bit random. So I wouldn't be surprised if folks managed a fully local, cool, simple version of this autonomous companion. For example, you don't need Whisper-grade open-vocabulary transcription: being able to recognize a few keywords would already be great for interaction. One of the fastest ways to turn this robot into an autonomous companion would be to stream Microduck's sensors (the camera, the depth sensor, the IMU and the joint positions) to a computer, and use a software stack like the one we use for the conversation app on Reachy Mini: a local VAD, then a cloud speech-to-text model, then a call to a frontier LLM that decides on actions. Actions could be quacking, looking at things/faces/a direction, walking to a given position, sitting down, playing an emotion, kicking or doing a somersault. A SLAM algorithm would run in parallel so the robot can localize itself in your home, and you would prompt the LLM for a lifelike behavior: moving to random places, sometimes following people, and having emotional responses that fit what you're saying and the duck's environment. Of course someone is going to build a Tamagotchi-like layer on top of this, and it will be insane. How much demand is there for a software suite that would do all of this? I for one think it would be super cool. A word about the humans. We had five engineers backstage, and they are pretty much the core team behind Microduck. Their impact per head is absolutely off the charts. Antoine Pirrone piloted Graphite, Augustin Crampette Lavender (the rebel one), Matthieu Lapeyre Sky, Coralie Deplane Cream, and Pierre Rouanet was stressing over the Wi-Fi. Give them a follow! (Antoine @antoinepirrone, Augustin on LinkedIn, Matthieu @matth_lapeyre, Coralie @Drenaya_, Pierre on LinkedIn). I get visibility because I communicate a lot, but I mainly work on Reachy Mini (you might want to check it out: it's a very cool robot, and it ships much faster than Microduck :) ). My contribution to Microduck has been minimal: I'm mostly a first power user. My main added value at GTC was having hands big enough to carry four Microducks below the stage. Where I take pride is that Antoine and Coralie are former students and former interns of mine. I'm therefore entitled to 3% credit on anything (good) they do, for life. If they do something bad, however, it was clearly the fault of their parents. About the super smart engineering that can be done on board: Antoine just released two very cool blog posts (links below). The first is on odometry, the robot estimating its own movement from its own internal sensors. The second is about SLAM, which allows long-term localization: it adds the depth sensor to the odometry to get a stable position over time. Think of it as recognizing known landmarks in your home to know where the robot is. The crazy part is that all of this runs on the robot. So this gives me hope that we'll be able to do a lot of cool stuff on board.
13
10
2
66
11,709
Replying to @Motier_crypto
That Jensen Huang's performance was faked. I've been building a real-world solution since August. Project: github.com/rokbenko/quackd CA: GMogeMjrWFaEceasCPathoibjAh8qwhTC3Chw4Bfpump nitter.gq/rokbenko/status/211425…
Jensen Huang is manifesting Quackd. Have you seen Jensen Huang talking to Microducks on stage at Nvidia’s GTC Berlin 2026 keynote? Well, an employee from Hugging Face x Pollen Robotics admitted the truth a few days later. This was after they sold 10,000 more Microducks. Jensen Huang did NOT engage with the Microducks on stage. Anyone who buys a Microduck will NOT be able to do that either. There was an engineer backstage piloting all the Microducks: "First of all, the demo you've seen was not fully autonomous. We had one engineer piloting each Microduck." For example, when Jensen Huang said “Take a nap,” an engineer in the background triggered a command. Then all the Microducks did the take-a-nap move. The Microducks did NOT hear Jensen Huang. The Microducks could NOT understand Jensen Huang. What he pretended to do will be ACTUALLY possible using Quackd with your Microduck. Project: github.com/rokbenko/quackd Proof: nitter.gq/RemiFabreRobot/status/… PS: The biggest Quackd update is yet to be released.
1
2
34
Replying to @cfm_sol
Microduck without Quackd is a toy. Microduck with Quackd is a companion. CA: GMogeMjrWFaEceasCPathoibjAh8qwhTC3Chw4Bfpump nitter.gq/rokbenko/status/211425…
Jensen Huang is manifesting Quackd. Have you seen Jensen Huang talking to Microducks on stage at Nvidia’s GTC Berlin 2026 keynote? Well, an employee from Hugging Face x Pollen Robotics admitted the truth a few days later. This was after they sold 10,000 more Microducks. Jensen Huang did NOT engage with the Microducks on stage. Anyone who buys a Microduck will NOT be able to do that either. There was an engineer backstage piloting all the Microducks: "First of all, the demo you've seen was not fully autonomous. We had one engineer piloting each Microduck." For example, when Jensen Huang said “Take a nap,” an engineer in the background triggered a command. Then all the Microducks did the take-a-nap move. The Microducks did NOT hear Jensen Huang. The Microducks could NOT understand Jensen Huang. What he pretended to do will be ACTUALLY possible using Quackd with your Microduck. Project: github.com/rokbenko/quackd Proof: nitter.gq/RemiFabreRobot/status/… PS: The biggest Quackd update is yet to be released.
2
3
8
101
solana:GMogeMjrWFaEceasCPathoibjAh8qwhTC3Chw4Bfpump is a ticking bomb just waiting for 10k people to get their microduck:native and start complaining
Correction to my previous post: 10,000* 10,000 Microduck buyers think they will be able to use the Microduck just like Jensen Huang performed on the stage. These people will be pissed off when they realize that a Microduck is simply too small to have onboard hardware capable enough to process what you talk to it. There was an engineer backstage piloting all the Microducks, as they admitted afterwards: "First of all, the demo you've seen was not fully autonomous. We had one engineer piloting each Microduck." I started building the solution in August. Let's save Microducks from a brainrot with Quackd! Project: github.com/rokbenko/quackd Proof: nitter.gq/RemiFabreRobot/status/…
3
7
194
Correction to my previous post: 10,000* 10,000 Microduck buyers think they will be able to use the Microduck just like Jensen Huang performed on the stage. These people will be pissed off when they realize that a Microduck is simply too small to have onboard hardware capable enough to process what you talk to it. There was an engineer backstage piloting all the Microducks, as they admitted afterwards: "First of all, the demo you've seen was not fully autonomous. We had one engineer piloting each Microduck." I started building the solution in August. Let's save Microducks from a brainrot with Quackd! Project: github.com/rokbenko/quackd Proof: nitter.gq/RemiFabreRobot/status/…
Now 10,000 Microduck sold since the Jensen keynote demo. It’s INSANE!
6
8
2
21
1,354