The error said megabytes
Julia ships the first Zero to Ellipsis episode through a gauntlet of lying error messages: an upload blocked by a silently skipped terms-of-service box, and a thumbnail rejected for '30 MB max' when the real problem was 3000 by 3000 pixels.
// trace: where this idea came from
- ↳ video diary @ 3:42 (el rechazo que hablaba de megabytes)
- ↳ video diary @ 4:44 (la causa real: píxeles)
- ↳ video diary @ 1:55 (el checkbox saltado en silencio)
Publishing the first podcast episode turns into a catalog of interfaces that report the wrong problem. Bug one: Spotify refuses the channel image over and over, “no se puede, no se puede”, and the actual cause is a terms-of-service acceptance Julia had skipped, because the form offered a skip button for a step that, evidently, “no debería ser skipado” ▸ 1:55. The UI let her pass a mandatory gate and then punished her downstream, silently.
Bug two is the entry’s title. The thumbnail bounces with a clear message: maximum 30 MB ▸ 3:46. Her file is around one megabyte ▸ 4:26. The real limit, discovered only by clicking into the file’s properties, is dimensions: the image was 3000 by 3000 pixels ▸ 4:44. A Canva resize to 1000 by 1000 and it sails through ▸ 5:00.
cuando el error no cuadra con tu archivo, duda del mensaje, no del archivo →
Even the content had a ghost: the finished audio opened with a phrase Julia couldn’t find in any transcript, “welcome to… deep dive?” ▸ 5:18. She hunted the scripts; the answer was NotebookLM leaking its own default mode name, Deep Dive, into the show’s intro, fixed by telling the focus prompt “the podcast is called Zero to Ellipsis” ▸ 6:51. The debugging rule that survives the day: when the message contradicts the evidence, the message is describing the wrong constraint. Trust the file you can measure over the sentence someone else wrote. And then, one step from publishing, the daily NotebookLM credits ran out ▸ 7:18, tomorrow, then…
// continued in
no entry has continued this idea yet: the arc is still open