Tweet to @RadioTagBot with the name of a station (e.g. "radio 1", "Radio4", "#radio2", "bbc two", "Channel 4") and it will tweet back telling you what's on that channel now. For ±«Óãtv services it will also create a bookmark to the point in the programme on the RadioTagBot website.
Project from 2012 - present
![](https://ichef.bbci.co.uk/images/ic/400xn/p0fd5ypn.png)
What we are doing
RadioTagBot is a way to bookmark the current point in a programme that you're listening to (or watching) live, by using Twitter.
To create a bookmark, you send a message to and it will tweet back to you with the title of the programme and a link to the point in time on iPlayer at which it will (usually) appear.
If it's on Radio 1, 1x, 2, 3 or 6 Music, it will also attempt to reply with the music track playing. More information is in .
Why it matters
This work derives from which makes it possible to select a point in time on a channel on a physical internet-connected radio, and then connect that via the system to services that allow you to do something with that information. These services could be bookmarking something for later to resume playing, or to find out what was playing (or who was speaking) at the time, or something else. Currently can only be used using a few specific types of radio (with specific software), and only within our trial system.
For wide adoption it is important for us to know whether this type of service would actually be used, and what it would be used for. This Twitter version of it is a lightweight way for us to gather feedback on the ideas.
Our Goals
- To experiment with usecases and functionality for RadioTAG
- To find out if people want to 'tag' radio
- To find out why they tag it
Outcomes
What are the outcomes?
- Usage data from the site and the bot
How it works
This implementation is a relatively small change to the codebase used in , and uses the same backend infrastructure:
- A tagging web service, which uses an Solr-powered database of metadata about programmes, channels and iPlayer availability
- An authentication server
- A web site
The main difference is that the physical device authentication is not required. Instead, any tweet to is stored, and authentication only occurs when you log into the site to view your tags.
The other addition is code that connects to Twitter's API every 30 seconds, looks for messages directed at , parses those tweets looking for variants of radio and tv channel names, creating a tag and responding on Twitter if it finds a result.