Catch up on your favourite BBC radio show from your favourite DJ right here, whenever you like. Listen without limits with BBC Sounds.

I noticed a trend of people saying that to get better results from Google Veo you should write prompts using more complex, machine-optimised (JSON) formatting; the one that looks something like this: "shot": { "composition": "four-way split-screen (2×2), full-body head-to-toe eye-level, 35 mm", "camera_motion": "static", "film_grain": 5 } That didn't seem right to me because at the core of Veo is a large language models; it comprehends natural human language, so structuring the prompt in machine readable code felt like it would make no difference at all.

These two stories, saved next to each other in my feed reader, are directly related: From Content and Community, by Ben Thompson: So, are existing publishers doomed? Well by-and-large yes, but that's because they have been doomed for a long time. People using Al instead of Google or Google using Al to provide answers above links - make the long-term outlook for advertising-based publishers worse, but that's an acceleration of a demise that has been in motion for a long time.