Actually, you know what, I have a bone to pick with you. It just occurred to me.

Awesome. I want you to fix a problem. You're not going to fix because you shouldn't.

You're really making a good case for yourself there.

I wanted to listen under the radar. When I went out for my run earlier today, and if you recall,

I run with watch and AirPods only. And I went to run overcast on my watch, which worked.

But the episode wasn't there because you had just released it like four and a half minutes prior.

I want streaming or some sort of manual, please, sir. Can I have it updated now?

Button. And you're not going to do it and you're probably right not to do it, but I want it.

I would love to offer that. I would love if there was a way that I could reliably initiate a

transfer that would happen immediately to the watch. There isn't.

No, but this is a cellular watch, man. Go to the internet.

Well, okay. I could do that. It would basically require a significantly different pipeline for

that file to get into the watch for it to be processed and synced. You would be dependent on

whatever the bitrate and format of the audio would be, which could be awfully large and

complicated for the watch to handle. Oh, and I wouldn't get smart speed. What do I?

You definitely wouldn't get smart speed. The watch is not fast enough to pre-process it.

And the API doesn't exist to do it live. It would basically be a really terrible experience.

Now, that being said, if there's something you want to listen to that isn't already on your watch

and you want to sync it over immediately and watch who I just isn't syncing it, that's also a

terrible experience. But fixing it like that's the kind of thing that I assume. And maybe after

this many years, this might be a bad assumption, but I assume that that's the kind of thing that

apples likely to fix sometime, whereas the complexity of having these two different ways for a file

...