Levi | still learning retweeted
Today we’re out of stealth, and we’ve raised a $40m seed round co-led by @creandum and @usv, to bring Instant Robot Learning to life.
For the past few months, we‘ve been busy building a new company.
Machenta.
This follows results from a new kind of robot foundation model we’ve ited to share with you today!
Usually, it takes hours/days of data collection and training to teach a robot.
We’ve built a model that learns tasks instantly: one demonstration, no further training.
A model trained entirely in simulation, without a single pixel of real-world data.
A model where teaching robots is so quick and easy, it feels like physical vibe coding.
A model for robots that learn like humans do, from someone like you.
Welcome to the era of Instant Robot Learning.
Thank you @Kathi_Wilhelm, @rebeccakaden, @hkanji, @jonno_evans and all of our angels for your support!
@Machenta_
Learn more: machenta.com/blog/instant-r…
See below for what you can do with Instant Robot Learning!
For the past few months, we‘ve been busy building a new company.
Machenta.
This follows results from a new kind of robot foundation model we’ve ited to share with you today!
Usually, it takes hours/days of data collection and training to teach a robot.
We’ve built a model that learns tasks instantly: one demonstration, no further training.
A model trained entirely in simulation, without a single pixel of real-world data.
A model where teaching robots is so quick and easy, it feels like physical vibe coding.
A model for robots that learn like humans do, from someone like you.
Welcome to the era of Instant Robot Learning.
Thank you @Kathi_Wilhelm, @rebeccakaden, @hkanji, @jonno_evans and all of our angels for your support!
@Machenta_
Learn more: machenta.com/blog/instant-r…
See below for what you can do with Instant Robot Learning!
191
137
1,496
247,663
Levi | still learning retweeted
This is Genie 4, our most realistic and interactive world model yet. 🌐
Explore dynamic environments in real time to see how the scene responds, sounds, and how the people in it move, react, and speak.
Explore dynamic environments in real time to see how the scene responds, sounds, and how the people in it move, react, and speak.
960
2,604
23,630
3,352,079
Levi | still learning retweeted
The coding interview is dead, at least for my team at Anthropic. I've seen enough to know that it no longer provides signal. I removed it from loops this month.
I have a spicy, optimistic take - I think there's an opportunity for junior engineers: felixrieseberg.com/hunger-beats-t…
I have a spicy, optimistic take - I think there's an opportunity for junior engineers: felixrieseberg.com/hunger-beats-t…
599
1,400
14,249
2,217,799
Levi | still learning retweeted
Many of you don't understand how serious this is, so let me break it down.
In computer science there is a famous kind of puzzle called 3-SAT. You are given a long list of yes-or-no switches and a set of rules about how they must be arranged, and you have to find a combination that satisfies every rule. The obvious way to solve it is to try every combination, but each new switch doubles the number of possibilities, so a puzzle with a few hundred switches would take longer than the age of the universe to brute force.
For decades, the smartest people in the field found clever tricks that made this a little faster, but every trick still hit the same wall: the time required kept exploding as the puzzle grew.
About 25 years ago, two computer scientists, Russell Impagliazzo and Ramamohan Paturi, working with Francis Zane, turned that wall into a formal idea.
They proposed the Exponential Time Hypothesis, which says this explosion is not a failure of human cleverness but a law of nature. No algorithm, however brilliant, will ever solve 3-SAT without the time blowing up exponentially. Nobody could prove it, but almost everyone believed it, and it became one of the foundations of modern computer science.
Researchers used it as a measuring stick. If you could show that solving some other problem quickly would also crack 3-SAT quickly, you had shown that problem was hopelessly hard too. Hundreds of papers, across scheduling, graphs, logic and much more, rest on this one assumption.
Now an internal AI model at OpenAI claims to have broken it. It says it found an algorithm that solves these puzzles meaningfully faster than the hypothesis allows, and it has checked the proof in a computer verification system called Lean.
And here is the remarkable part: the very people who proposed the hypothesis, Impagliazzo and Paturi, along with MIT's Ryan Williams, are now leading the public review of whether a machine has disproved their own idea.
So what happens next? If the disproof holds, a large part of theoretical computer science has to be revisited.
Every result that said "this problem cannot be solved faster, assuming ETH" loses its foundation, and researchers will have to work out which of those walls were real and which were simply where we stopped looking. It does not mean everything becomes easy. The new algorithm is still slow in absolute terms and this is not the famous P versus NP problem being solved.
But it means our map of what is possible was wrong in a place we were very confident about, and it was an AI that redrew it. If the disproof fails, the hypothesis survives and the field breathes out, but we will still have watched an AI produce serious, checkable work on one of the deepest questions in the discipline, closely enough that the founders of the idea had to take it seriously. Either way, something has shifted.
In computer science there is a famous kind of puzzle called 3-SAT. You are given a long list of yes-or-no switches and a set of rules about how they must be arranged, and you have to find a combination that satisfies every rule. The obvious way to solve it is to try every combination, but each new switch doubles the number of possibilities, so a puzzle with a few hundred switches would take longer than the age of the universe to brute force.
For decades, the smartest people in the field found clever tricks that made this a little faster, but every trick still hit the same wall: the time required kept exploding as the puzzle grew.
About 25 years ago, two computer scientists, Russell Impagliazzo and Ramamohan Paturi, working with Francis Zane, turned that wall into a formal idea.
They proposed the Exponential Time Hypothesis, which says this explosion is not a failure of human cleverness but a law of nature. No algorithm, however brilliant, will ever solve 3-SAT without the time blowing up exponentially. Nobody could prove it, but almost everyone believed it, and it became one of the foundations of modern computer science.
Researchers used it as a measuring stick. If you could show that solving some other problem quickly would also crack 3-SAT quickly, you had shown that problem was hopelessly hard too. Hundreds of papers, across scheduling, graphs, logic and much more, rest on this one assumption.
Now an internal AI model at OpenAI claims to have broken it. It says it found an algorithm that solves these puzzles meaningfully faster than the hypothesis allows, and it has checked the proof in a computer verification system called Lean.
And here is the remarkable part: the very people who proposed the hypothesis, Impagliazzo and Paturi, along with MIT's Ryan Williams, are now leading the public review of whether a machine has disproved their own idea.
So what happens next? If the disproof holds, a large part of theoretical computer science has to be revisited.
Every result that said "this problem cannot be solved faster, assuming ETH" loses its foundation, and researchers will have to work out which of those walls were real and which were simply where we stopped looking. It does not mean everything becomes easy. The new algorithm is still slow in absolute terms and this is not the famous P versus NP problem being solved.
But it means our map of what is possible was wrong in a place we were very confident about, and it was an AI that redrew it. If the disproof fails, the hypothesis survives and the field breathes out, but we will still have watched an AI produce serious, checkable work on one of the deepest questions in the discipline, closely enough that the founders of the idea had to take it seriously. Either way, something has shifted.
An internal model at OpenAI has produced a claimed refutation of ETH! Russell Impagliazzo, Mohan Paturi, and I have been asked to help organize an open and independent examination of this claim. 1/4
335
1,619
17,026
1,444,780
Levi | still learning retweeted
Security Alert: U.S. Mission Saudi Arabia (October 27, 2026)
Effective October 23, 2026, the Department of State ordered non-emergency U.S. government employees and U.S. government employee family members to leave Saudi Arabia due to safety risks.
Iranian-supported Houthis have against Saudi Arabia, including attacks on civilian airports and other critical infrastructure resulting in civilian casualties and severe travel disruptions. The hostilities have the potential to escalate rapidly beyond that immediate area.
U.S. government employees working in Saudi Arabia require special authorization from Chief of Mission to use any airport in Saudi Arabia following recent missile and UAV attacks on airports in the Kingdom.
- King Khalid International Airport (RUH) in Riyadh announced a partial reopening as of October 23 for domestic flights and some international flights operated by national carriers. A limited number of flights normally based at RUH are operating out of Qassim-based Prince Naif bin Abdulaziz International Airport (ELQ).
- Operations at King Abdulaziz International Airport in Jeddah (JED) are operational with some delays and cancellations.
- Operations at King Fahd International Airport in Dammam (DMM) are operational with some delays and cancellations.
U.S. citizens should be aware of potential attacks on airports, airspace closures, flight cancellations, and travel disruptions. Please take extreme caution if you choose to use airports in Saudi Arabia. We recommend checking your flight departure status directly with the airline and with the airport.
Read more: sa.usembassy.gov/security-alert…
Effective October 23, 2026, the Department of State ordered non-emergency U.S. government employees and U.S. government employee family members to leave Saudi Arabia due to safety risks.
Iranian-supported Houthis have against Saudi Arabia, including attacks on civilian airports and other critical infrastructure resulting in civilian casualties and severe travel disruptions. The hostilities have the potential to escalate rapidly beyond that immediate area.
U.S. government employees working in Saudi Arabia require special authorization from Chief of Mission to use any airport in Saudi Arabia following recent missile and UAV attacks on airports in the Kingdom.
- King Khalid International Airport (RUH) in Riyadh announced a partial reopening as of October 23 for domestic flights and some international flights operated by national carriers. A limited number of flights normally based at RUH are operating out of Qassim-based Prince Naif bin Abdulaziz International Airport (ELQ).
- Operations at King Abdulaziz International Airport in Jeddah (JED) are operational with some delays and cancellations.
- Operations at King Fahd International Airport in Dammam (DMM) are operational with some delays and cancellations.
U.S. citizens should be aware of potential attacks on airports, airspace closures, flight cancellations, and travel disruptions. Please take extreme caution if you choose to use airports in Saudi Arabia. We recommend checking your flight departure status directly with the airline and with the airport.
Read more: sa.usembassy.gov/security-alert…
78
739
2,073
556,021
Levi | still learning retweeted
Some walk with you for a while…
Others stay in your sky forever…
Others stay in your sky forever…
728
8,586
57,206
16,074,282
Levi | still learning retweeted
I want to show you guys something really wild.
Claude Opus 5.5 basically one-shotted an explainer video for this paper, and it's incredible!
After watching the video, I feel like I have a decent understanding of how JEM works!
Check it out:
Claude Opus 5.5 basically one-shotted an explainer video for this paper, and it's incredible!
After watching the video, I feel like I have a decent understanding of how JEM works!
Check it out:
This paper went completely under the radar!
Meta researchers have developed a novel and simple self-supervised learning framework competitive with DINOv2 and DINOv3!
"Scalable Patch-Level Self-Supervised Learning"
The authors introduce JEM, a principled student-teacher method tch representations across different views. Additionally, it incorporates explicit regularization to ensure representations are informative and prevent structural collapse.
The framework outperforms DINOv2 in a controlled setting on dense tasks, and even beats the DINOv3 checkpoint despite it being trained on 12x less data.
34
57
616
32,868
Non technical persons sekarang sudah makin bisa bikin software kebutuhan mereka sendiri. Dan bukan aplikasi main2 lagi.
Gapnya akan semakin tipis dan tipis.
Saya rasa yang perlu benar2 dijagain sekarang (untuk majority type of software) tinggal: database design & product/user expen penting karena once itu salah, benerinnya headache. Product itu penting karena, 100 features yang dibikin AI itu akan gak guna kalau user juga gak tahu cara pakenya. Dan users ternyata perlunya cuma 3 features.
Role Software Engineers perlu berubah.
Tidak lagi zamannya menunggu PRD datang karena otherwise stakeholder akan prefer bikin sendiri (daripada lama nungguin). **SWE perlu ke lapangan**, cari problemnya, bikin solusinya, quickly validate, iterate.
Tidak lagi juga zamannya berlayer2 dan beragam dokumen untuk koordinasi. Jika multiple roles itu bisa ada pada 1 orang, tidak perlu kan berbagai macam dokumen itu.
Problems itu gak habis2 kok. Tinggal kita mau terjun mendekatkan diri ke problems atau tidak. Afterall, gap antara problem dan solusi itulah yang disebut impact.
Gapnya akan semakin tipis dan tipis.
Saya rasa yang perlu benar2 dijagain sekarang (untuk majority type of software) tinggal: database design & product/user expen penting karena once itu salah, benerinnya headache. Product itu penting karena, 100 features yang dibikin AI itu akan gak guna kalau user juga gak tahu cara pakenya. Dan users ternyata perlunya cuma 3 features.
Role Software Engineers perlu berubah.
Tidak lagi zamannya menunggu PRD datang karena otherwise stakeholder akan prefer bikin sendiri (daripada lama nungguin). **SWE perlu ke lapangan**, cari problemnya, bikin solusinya, quickly validate, iterate.
Tidak lagi juga zamannya berlayer2 dan beragam dokumen untuk koordinasi. Jika multiple roles itu bisa ada pada 1 orang, tidak perlu kan berbagai macam dokumen itu.
Problems itu gak habis2 kok. Tinggal kita mau terjun mendekatkan diri ke problems atau tidak. Afterall, gap antara problem dan solusi itulah yang disebut impact.
there is no moat
2
17
123
3,223
Saya sendiri masih jagain layer tengah2 itu sekarang. Tapi tidak dengan baca line by line, melainkan probing questions ke AI. Saya masih tahu architecturenya, apa manggil apa. Tapi melalui perantara AI yang menjelaskannya. Persis seperti ketika jadi Engineering Manager dulu.
Nah, tapi layer di tengah2 itu makin ke sini makin bisa dilihat blackbox. AI makin pintar. Ibarat jika sudah ada Staff Level engineers/Architect, tidak perlu lagi kan terlalu validate detailnya (walau seringkali masih kepo penasaran 😁)
Nah, tapi layer di tengah2 itu makin ke sini makin bisa dilihat blackbox. AI makin pintar. Ibarat jika sudah ada Staff Level engineers/Architect, tidak perlu lagi kan terlalu validate detailnya (walau seringkali masih kepo penasaran 😁)
0
0
1
308
Levi | still learning retweeted
i just re created kurzgesagt's entire channel in 10 minutes with claude opus
they have 0 competition because every video takes a full team of animators and 1200+ hours to make
i turned it into a claude prompt that im giving out for free
open claude code, paste the prompt, video is fully automated
thank me later ↓
<inputs>
Ask me for: one topic as a "what if" question (default: "What if the Sun vanished?"), the length (default 30 seconds), and whether I have an ElevenLabs key (if not, use a free local voice).
</inputs>
<direction>
A Kurzgesagt-style animated explainer at 1920x1080, 30fps, drawn entirely in code: one 2D canvas plus one WebGL canvas for planets.
Space: a vertical gradient #081d2c to #102348, five huge parallax nebula blobs (teal rgb 24,150,160 at 20%, blue 40,95,195 at 16%, coral 220,95,110 at 10%, indigo 60,70,175 at 15%), three star layers at parallax depths .12/.35/.6 that twinkle, 40% of the near stars drawn as 4-point sparkles.
The Sun: radius 300px, half off the left edge. A radial gradient #fff7dc to #ffc857 to #ff8f4a with an offset highlight, additive halo rings at 1.23/1.48/1.76/2.1x the radius, 18 faint rotating ray wedges, 28 drifting glowing granules on its surface.
Earth: an orthographic sphere in a fragment shader, 4x supersampled, from a 2048x1024 map painted from longitude/latitude polygons: land #5fc47a, forest #48ad6b, desert #f5c75f, rainforest #3a9d62, ice #f1f8ff, ocean gradient #4dc7eb to #1a66b8, white capsule clouds. Tilt .26 rad, spin .55 degrees per second. Day/night uses smoothstep(-.12, .24, N·L) with the light direction recomputed from Sun to Earth every frame. Navy night side with ~380 warm city lights, a coral band on the terminator, a cyan rim, ocean specular, an atmosphere halo that is stronger on the lit side.
A small astronaut mascot (~180px) built from rounded rectangles: suit #f3f7fb, orange #ff8f4a boots, a visor gradient #1f5a73 to #0a1c2c with glowing cyan eyes that look at whatever matters, a blinking antenna light, an idle bob, squash and stretch on every pose.
Type: Fredoka 600/700 only. Captions in caps with 3-6px letter spacing in teal #8fd8e6, gold #ffd98a or white, sitting in rounded pills of rgb(6,20,40) at 62%. Every line of text rises 1.3x its own height through a clip on an ease-out-quint.
Finish: a vignette to rgba(4,4,20,.45) and a 6% film grain re-randomized 24 times per second.
Banned: outlines, flares or loops on the Sun's edge, static infographic strips, full stops in on-screen text, text that fades in whole, AI images or AI video, Kurzgesagt's own characters, bird or music.
</direction>
<structure>
30 seconds, every line of narration gets a camera move or a transformation, nothing ever holds still.
Tight on the Sun at 2.25x (0s) → on the word "vanished" it swells 6% for 0.22s, collapses in 0.33s, then a white flash and a shockwave ring (1s) → pull back to 1x revealing Earth still lit and the astronaut staring at the empty spot (1.6-3s) → on "eight" an 8:20 countdown slams in from 1.7x to 1x and starts ticking, a "LAST LIGHT" label rides the edge of the growing dark disc (3.2s) → dive to 2.3x on Earth with light streaks flowing in (5.6s) → on "you" a YOU pin drops (7s) → on "left" a photon lands on the pin with "THIS LIGHT LEFT THE SUN / 8 MIN 20 SEC AGO" (7.5s) → on "play" the pin morphs into a play button, "YOU PRESSED PLAY / 15 SEC AGO" (8.8s) → one pull-back from 2.4x to a 0.3x orbit view, "LAST LIGHT" and "GRAVITY" riding the ring (9.6-12.5s) → on "nothing" a dotted circle at the empty centre (13.4s) → on "hits" the darkness sweeps Earth in 0.7s, city lights pop on, the countdown turns gold at 0:00 (15.8s) → on "black" the background fades almost to black (17.4s) → Jupiter appears, "STILL SHINING FOR 1 HOUR+" (17.9s) → zoom out, a dashed tangent line, "30 KM/S" as Earth flies straight off (20.8s) → a thermometer counts 15 to -70°C while frost grows from the poles (22.8s) → a 0.8s rewind on a separate story clock (24.3s) → sunglasses drop onto the astronaut (25.2s) → a photon tagged "8:20 OLD", then the title (27.7s).
For any other topic, keep the same shape: the event happens on its word, pull back to show scale, dive in to make it personal ("you"), pull back out, the consequence with a live counter, an escalation, a funny beat with the mascot, a callback and the title.
</structure>
<build>
1. One HTML file. Every frame is a pure function of time: window.seek(t) draws frame t. No timers, no CSS animation.
2. Camera moves on easeInOutCubic, zoom is interpolated in log space, every pop is a damped spring (damping .42-.5, frequency 12-16).
3. Voice: ElevenLabs eleven_v4 with a designed voice (calm, warm, curious male, late 30s, crisp, light neutral European English), stability .5, similarity .75, generated with timestamps. Without a key, use kokoro-onnx locally and get word times with faster-whisper. Every animation event fires on its word. About 165 words per minute, 0.24s between sentences, a 0.36s beat before the big reveal.
4. The darkness front: any pixel within the front's radius from the Sun turns to night with a 30px soft edge. The front moves at ~47px/s and ramps to 700px/s near Earth.
5. Keep two clocks: ambient time for twinkle, spin and bob, and a separate story clock for events, so a rewind stays consistent.
6. Render with Playwright in headless Edge with the GPU: seek every frame at 30fps and blend 2 subframes (shutter 0.6) for motion blur, then encode with libx264 at CRF 16 for the master and CRF 20 for delivery.
7. Sound: a calm royalty-free space music bed 7dB under the voice, timed so its natural ending lands on the title, swelling 5dB under the title. One downloaded royalty-free sound effect per event kind (collapse, impact, pull-back whoosh, countdown tick, dive, pin tap, photon land, play click, light hit, reveal, frost, rewind), each peak-aligned to its frame and 4-10dB under the voice. Master with gain plus a limiter to -14 LUFS, -2.2dB true peak.
</build>
<gotchas>
Make the WebGL globe canvas at least 2 x radius x zoom x 1.18 pixels or the sphere clips flat in close-ups. Never draw prominences on the Sun's edge, they read as white hooks. Never pad the voice to fit the visuals, tighten the read instead. Speed the darkness front up near Earth or it takes 13 seconds to cross the planet. Show me a contact sheet of every beat before rendering.
</gotchas>
<start>
Ask me the inputs, write the narration with the beat each word triggers, show it to me, then build and render the video.
</start>
they have 0 competition because every video takes a full team of animators and 1200+ hours to make
i turned it into a claude prompt that im giving out for free
open claude code, paste the prompt, video is fully automated
thank me later ↓
<inputs>
Ask me for: one topic as a "what if" question (default: "What if the Sun vanished?"), the length (default 30 seconds), and whether I have an ElevenLabs key (if not, use a free local voice).
</inputs>
<direction>
A Kurzgesagt-style animated explainer at 1920x1080, 30fps, drawn entirely in code: one 2D canvas plus one WebGL canvas for planets.
Space: a vertical gradient #081d2c to #102348, five huge parallax nebula blobs (teal rgb 24,150,160 at 20%, blue 40,95,195 at 16%, coral 220,95,110 at 10%, indigo 60,70,175 at 15%), three star layers at parallax depths .12/.35/.6 that twinkle, 40% of the near stars drawn as 4-point sparkles.
The Sun: radius 300px, half off the left edge. A radial gradient #fff7dc to #ffc857 to #ff8f4a with an offset highlight, additive halo rings at 1.23/1.48/1.76/2.1x the radius, 18 faint rotating ray wedges, 28 drifting glowing granules on its surface.
Earth: an orthographic sphere in a fragment shader, 4x supersampled, from a 2048x1024 map painted from longitude/latitude polygons: land #5fc47a, forest #48ad6b, desert #f5c75f, rainforest #3a9d62, ice #f1f8ff, ocean gradient #4dc7eb to #1a66b8, white capsule clouds. Tilt .26 rad, spin .55 degrees per second. Day/night uses smoothstep(-.12, .24, N·L) with the light direction recomputed from Sun to Earth every frame. Navy night side with ~380 warm city lights, a coral band on the terminator, a cyan rim, ocean specular, an atmosphere halo that is stronger on the lit side.
A small astronaut mascot (~180px) built from rounded rectangles: suit #f3f7fb, orange #ff8f4a boots, a visor gradient #1f5a73 to #0a1c2c with glowing cyan eyes that look at whatever matters, a blinking antenna light, an idle bob, squash and stretch on every pose.
Type: Fredoka 600/700 only. Captions in caps with 3-6px letter spacing in teal #8fd8e6, gold #ffd98a or white, sitting in rounded pills of rgb(6,20,40) at 62%. Every line of text rises 1.3x its own height through a clip on an ease-out-quint.
Finish: a vignette to rgba(4,4,20,.45) and a 6% film grain re-randomized 24 times per second.
Banned: outlines, flares or loops on the Sun's edge, static infographic strips, full stops in on-screen text, text that fades in whole, AI images or AI video, Kurzgesagt's own characters, bird or music.
</direction>
<structure>
30 seconds, every line of narration gets a camera move or a transformation, nothing ever holds still.
Tight on the Sun at 2.25x (0s) → on the word "vanished" it swells 6% for 0.22s, collapses in 0.33s, then a white flash and a shockwave ring (1s) → pull back to 1x revealing Earth still lit and the astronaut staring at the empty spot (1.6-3s) → on "eight" an 8:20 countdown slams in from 1.7x to 1x and starts ticking, a "LAST LIGHT" label rides the edge of the growing dark disc (3.2s) → dive to 2.3x on Earth with light streaks flowing in (5.6s) → on "you" a YOU pin drops (7s) → on "left" a photon lands on the pin with "THIS LIGHT LEFT THE SUN / 8 MIN 20 SEC AGO" (7.5s) → on "play" the pin morphs into a play button, "YOU PRESSED PLAY / 15 SEC AGO" (8.8s) → one pull-back from 2.4x to a 0.3x orbit view, "LAST LIGHT" and "GRAVITY" riding the ring (9.6-12.5s) → on "nothing" a dotted circle at the empty centre (13.4s) → on "hits" the darkness sweeps Earth in 0.7s, city lights pop on, the countdown turns gold at 0:00 (15.8s) → on "black" the background fades almost to black (17.4s) → Jupiter appears, "STILL SHINING FOR 1 HOUR+" (17.9s) → zoom out, a dashed tangent line, "30 KM/S" as Earth flies straight off (20.8s) → a thermometer counts 15 to -70°C while frost grows from the poles (22.8s) → a 0.8s rewind on a separate story clock (24.3s) → sunglasses drop onto the astronaut (25.2s) → a photon tagged "8:20 OLD", then the title (27.7s).
For any other topic, keep the same shape: the event happens on its word, pull back to show scale, dive in to make it personal ("you"), pull back out, the consequence with a live counter, an escalation, a funny beat with the mascot, a callback and the title.
</structure>
<build>
1. One HTML file. Every frame is a pure function of time: window.seek(t) draws frame t. No timers, no CSS animation.
2. Camera moves on easeInOutCubic, zoom is interpolated in log space, every pop is a damped spring (damping .42-.5, frequency 12-16).
3. Voice: ElevenLabs eleven_v4 with a designed voice (calm, warm, curious male, late 30s, crisp, light neutral European English), stability .5, similarity .75, generated with timestamps. Without a key, use kokoro-onnx locally and get word times with faster-whisper. Every animation event fires on its word. About 165 words per minute, 0.24s between sentences, a 0.36s beat before the big reveal.
4. The darkness front: any pixel within the front's radius from the Sun turns to night with a 30px soft edge. The front moves at ~47px/s and ramps to 700px/s near Earth.
5. Keep two clocks: ambient time for twinkle, spin and bob, and a separate story clock for events, so a rewind stays consistent.
6. Render with Playwright in headless Edge with the GPU: seek every frame at 30fps and blend 2 subframes (shutter 0.6) for motion blur, then encode with libx264 at CRF 16 for the master and CRF 20 for delivery.
7. Sound: a calm royalty-free space music bed 7dB under the voice, timed so its natural ending lands on the title, swelling 5dB under the title. One downloaded royalty-free sound effect per event kind (collapse, impact, pull-back whoosh, countdown tick, dive, pin tap, photon land, play click, light hit, reveal, frost, rewind), each peak-aligned to its frame and 4-10dB under the voice. Master with gain plus a limiter to -14 LUFS, -2.2dB true peak.
</build>
<gotchas>
Make the WebGL globe canvas at least 2 x radius x zoom x 1.18 pixels or the sphere clips flat in close-ups. Never draw prominences on the Sun's edge, they read as white hooks. Never pad the voice to fit the visuals, tighten the read instead. Speed the darkness front up near Earth or it takes 13 seconds to cross the planet. Show me a contact sheet of every beat before rendering.
</gotchas>
<start>
Ask me the inputs, write the narration with the beat each word triggers, show it to me, then build and render the video.
</start>
kurzgesagt has 25M subs and they still go viral with 15M+ views on every single video for years
nobody copies them because every video takes a full studio of animators and months of work
i rebuilt their format with opus 5.5, 100% code for $0 per video, on the left is my own robably averages $150k+ earning per video
9 years ago he posted how he makes 1 video in 1200 hours, i re created this in literally 10 minutes for free (check in comments)
would u guys be interested if i turned this into a free claude skill you can use?
177
189
3,060
246,222
Levi | still learning retweeted
Saya kasih satu lagi slide paparan saya di PKU, Beijing. Semoga pemerintah bisa introspeksi. It's clear that the public and the government are reading from different agendas.
@ardi_tama1kin bersikeras tanpa merevisi skema MBG, approval beliau malah makin drop. Mending diubah skemanya menjadi lebih targeted, bukan kayak sekarang bersifat universal dan sangat costly. Akibatnya banyak program lain yg lebih dibutuhkan rakyat yg jadi trade-offnya. Saya udah jelaskan pas diwawancara Reuters di reuters.com/world/asia-pac…
28
247
616
44,160
Berpendapat serupa, kok suram masa depan dunia Internet di era AI ini
Defensive itu lebih susah daripada attacking
Bayangkan Internet diisi oleh sekian juta AI agents yang roaming cari celah keamanan apapun yang terconnect ke Internet. Kemudian auto attack. Mulai dari banking hingga personal devices, semua tidak aman.
Belum lagi buzzer2/bot2 yang berinteraksi dengan kita seolah2 mereka manusia.
Defensive itu lebih susah daripada attacking
Bayangkan Internet diisi oleh sekian juta AI agents yang roaming cari celah keamanan apapun yang terconnect ke Internet. Kemudian auto attack. Mulai dari banking hingga personal devices, semua tidak aman.
Belum lagi buzzer2/bot2 yang berinteraksi dengan kita seolah2 mereka manusia.
@ismailfahmi by then internet is dead, both from AI and cybersecurity nightmares, common people don’t trust it anymore
6
15
70
4,860
Levi | still learning retweeted
holy f*ck…he is right
229M views in 12 days 😭
229M views in 12 days 😭
okay i'll be honest i was doomscrolling
and accidentally found a 1M view format
i was contemplating on sharing this
but fuck it
the format is a very specific formula
→ two animated characters
→ they roleplay a real situation
→ the app shows up once shortly
→ no pitch, no eople watch it like a show
it's TikTok slideshows, but animated
slideshows were easier to make
and significantly cheaper
so everyone ran to those
but now that's changed
i just created 12 different animation styles
now just deciding on the winner
with Rork Max i built my app in days
now the distribution will take just a few more
you might not even realize how blessed
you are to live in these times
so much opportunity
20
165
1,896
124,225
Waduh
..... :P
..... :P
despite the unfortunate timing, we take disclosures seriously at @typesafeai
at approximately 6:49PM this Friday evening, we became aware of a massive unauthorized leak of ALL customer noul outputs
in effort to maximize transparency, here is the link: gist.github.com/diogo149/81003…
0
0
1
433
Levi | still learning retweeted
K3.1 Pro works directly in the tools used by the 3D modeling and game industries - Blender, Unreal Engine, Godot, and CAD.
On BenchCAD, which tests 3D reconstruction from multi-view renderings through CAD code generation, it scores 92.7% with tools, approaching Claude Opus 5.5 (95.9%).
K3.1 Pro can deliver a fairly complete project, from asset construction to scene assembly, animation, and rendering.
On BenchCAD, which tests 3D reconstruction from multi-view renderings through CAD code generation, it scores 92.7% with tools, approaching Claude Opus 5.5 (95.9%).
K3.1 Pro can deliver a fairly complete project, from asset construction to scene assembly, animation, and rendering.
17
72
1,978
156,615