Journal
Notes from running internet radio.
Longer pieces on audio delivery, live handovers, moving platforms and using AI with a person in charge. We say what we tested and where the limits are.
Follow by RSSAI + operations · 8 min read
Radio automation with human approval: what agents should—and should not—put on air
The useful question is not whether an agent can automate a radio station. It is where assistance should stop, who reviews the result and which actions deserve an unmistakable human decision.
Read the articleMore from the Journal
Audio delivery · 10 min read
AAC vs MP3 for internet radio: choose the listener path, not the fashionable codec
Codec efficiency matters, but a station is only successful when listeners can press play. The right decision includes browsers, directories, embedded players, fallback behaviour and the audience’s actual devices.
Migration · 9 min read
Before migrating an internet radio station, measure these seven things
A station migration is not an upload job. It is a controlled change to programming, live contribution and listener delivery, with the old service kept available until the new path is proven.
Live operations · 8 min read
When the live presenter disconnects: designing a clean return to AutoDJ
A live show is only half the workflow. The other half is what the station does when the encoder stops, the presenter loses connectivity or the source disappears without a tidy sign-off.
MCP + integration · 9 min read
What an MCP server for internet radio should actually do
A useful radio MCP server is not a chat wrapper around every API endpoint. It gives assistants a small, legible set of tools that match real station jobs and preserve operator control.
Run your radio station from one desk.
Private beta. No card needed. We reply within two business days.