<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet title="XSL_formatting" type="text/xsl" href="/blogs/shared/nolsol.xsl"?>

<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>

<title>
BBC Internet Blog
 - 
Ian Hunter
</title>
<link>https://bbcstreaming.pages.dev/blogs/bbcinternet/</link>
<description>Staff from the BBC&apos;s online and technology teams talk about BBC Online, BBC iPlayer, and the BBC&apos;s digital and mobile services. The blog is reactively moderated. Posts are normally closed for comment after three months. Your host is Eliza Kessler. </description>
<language>en</language>
<copyright>Copyright 2012</copyright>
<lastBuildDate>Thu, 24 May 2012 16:24:35 +0000</lastBuildDate>
<generator>http://www.sixapart.com/movabletype/?v=4.33-en</generator>
<docs>http://blogs.law.harvard.edu/tech/rss</docs> 


<item>
	<title>Privacy and Cookies</title>
	<description><![CDATA[<p>Today I want to introduce some changes we are making on BBC Online so that it is easier for you to manage the cookies we use. This is in response to changes in the regulations about cookies which <a href="https://bbcstreaming.pages.dev/blogs/bbcinternet/2011/05/cookie_laws_changes.html">my colleague Kate Leece last blogged about in May 2011</a>.</p>
<p>She explained how the regulations were changing and the steps we were taking to meet the new rules. The UK implementation of the new regime is led by the Information Commissioner&rsquo;s Office (ICO) and <a href="http://www.ico.gov.uk/for_organisations/privacy_and_electronic_communications/the_guide/cookies.aspx">more information can be found on the ICO website</a>.</p>
<p>The principle behind the changes is that users of websites should be given more information about the cookies set on their computers or other devices by those websites, and the means to set their own preferences.</p>
<p>At the same time, both regulators and publishers are keen to find a way to do this that is not intrusive and does not unduly disrupt a user&rsquo;s normal experience of a site. We have made a number of changes to the BBC website to ensure that we give users more control over the types of cookies they accept.</p>]]><![CDATA[<p>Our <a href="https://bbcstreaming.pages.dev/privacy/cookies">cookies pages</a> have been rewritten and given a separate link from the bottom of every page.</p>
<p>We have built a new&nbsp;feature which <a href="https://bbcstreaming.pages.dev/privacy/cookies/managing/cookie-settings.html">allows you to turn off any of the three classes of cookies on the BBC&rsquo;s website</a>, which are not in the category of "Strictly Necessary Cookies", as explained in the section on different types of cookies below, if you wish to do so. This functionality will be on the international website bbc.com soon.<span style="text-decoration: line-through;">&nbsp;is also available on the international website, bbc.com.&nbsp;</span></p>
<p class="imgCaptionCenter" style="text-align: center; display: block; "><img class="mt-image-center" style="margin: 0 auto 5px;" src="https://bbcstreaming.pages.dev/blogs/bbcinternet/2012/05/23/cookiesettingschange_595.png" alt="" width="595" height="282" />
<p>The new feature enables users to turn off cookies that are not strictly necessary</p>
</p>
<p>The pages also explain how users can <a href="http://www.live.bbc.co.uk/corporate/privacy/cookies/managing">manage the cookies set by the Adobe Flash Player</a>.</p>
<p>From today users of BBC Online will be presented with a banner telling them about the use of cookies and how they can change their settings at any time, on first use of their chosen browser (e.g. Internet Explorer, FireFox etc).</p>
<p>At the present time it is not technically possible for us to allow you to carry your settings with you between your browsers and devices so you will need to change these settings from each browser you use.</p>
<p class="imgCaptionCenter" style="text-align: center; display: block; "><img class="mt-image-center" style="margin: 0 auto 5px;" src="https://bbcstreaming.pages.dev/blogs/bbcinternet/2012/05/23/cookiesettingsalert_595.png" alt="" width="595" height="88" />
<p>&nbsp;</p>
</p>
<p>Users will be offered three options:</p>
<ul>
<li>to find out more about cookies</li>
<li>to change their settings</li>
<li>or to continue their journey, either by clicking on Continue or by clicking elsewhere on the page</li>
</ul>
<p>Users who subsequently decide to change their settings can do so at any time by clicking on the link to Cookies in the footer of every page.</p>
<p>The&nbsp; ICO&rsquo;s guidance defines four different types of cookie:</p>
<p><strong>Strictly Necessary Cookies</strong>, few in number, are those which are essential to enable you to move around the website and use its essential features. Without them a user&rsquo;s normal expectations cannot be met. One example is the cookie that allows you to automatically sign in to the BBC website for a service which you have previously registered for.</p>
<p>The second category is <strong>Functionality Cookies</strong>. These cookies allow the website to remember a user&rsquo;s preferences in terms of look and feel, language or location. One example is to enable you to set your preferred location to receive your local news and weather forecast.</p>
<p><strong>Performance Cookies</strong> collect information, usually anonymised, about the areas of the site visited by a user, frequency of visits and any errors experienced, inter alia. This information helps publishers to improve their services by helping them to understand user behaviour and experience in the mass.</p>
<p>Finally, <strong>Advertising Cookies</strong> gather information which helps to ensure that the advertisements served to a user are relevant. In the BBC&rsquo;s case these <strong>only</strong> apply to users who access our services from outside the UK via the BBC&rsquo;s international site, bbc.com, which is advertising funded. This data is also anonymised. There is <a href="https://bbcstreaming.pages.dev/privacy/cookies/international">more on this&nbsp;on our cookies pages</a>.</p>
<p><em>Ian Hunter is Managing Editor, BBC Online</em></p>
<p><em>Other useful links:</em></p>
<ul>
<li><a href="http://www.allaboutcookies.org/"><em>allaboutcookies.org</em></a></li>
<li><a href="http://www.aboutcookies.org/"><em>aboutcookies.org</em></a></li>
<li><a href="http://en.wikipedia.org/wiki/HTTP_cookie"><em>"cookie" at Wikipedia</em></a></li>
</ul>
<p><em>Correction (cookie management on bbc.com) 11:38 Fri 25 May</em></p>]]></description>
         <dc:creator>Ian Hunter 
Ian Hunter
</dc:creator>
	<link>https://bbcstreaming.pages.dev/blogs/bbcinternet/2012/05/privacy_cookies_ico.html</link>
	<guid>https://bbcstreaming.pages.dev/blogs/bbcinternet/2012/05/privacy_cookies_ico.html</guid>
	<category>BBC Online</category>
	<pubDate>Thu, 24 May 2012 16:24:35 +0000</pubDate>
</item>

<item>
	<title>BBC Online and &apos;deleting&apos; websites</title>
	<description><![CDATA[<p>There's been a lively discussion on the issues around archiving websites this week that kicked off with <a href="http://adactio.com/journal/4336/">an initial post </a>from Adactio blogger Jeremy Keith. He suggested that the BBC's plans to halve its top level directories were cultural vandalism. This was <a href="http://twitter.com/#!/bengoldacre/status/34942533649833984">picked up </a>(though later <a href="http://twitter.com/#!/bengoldacre/status/34975374412619777">clarified</a>) by @bengoldacre and many others. The tenor of the criticism was the same - that the BBC is failing in its duty to preserve a record of its online past.<br /><br />On Friday <a href="http://www.metro.co.uk/tech/855220-fan-saves-bbc-websites-from-deletion-for-2-50">Metro reported </a>on a 'BBC fan' who has captured for posterity a record of the 170 sites it's suggested we'll be deleting for efficiency reasons.</p>
<p>And many have claimed this is only the latest failure, after the wiping (or worse) of programmes in the sixties which are seen as classics today. This is not, and never was, part of the plan.</p>
<p><a href="https://bbcstreaming.pages.dev/blogs/bbcinternet/2011/01/putting_quality_first_halving.html">My post last month</a> explained that we were exploring a range of options for managing legacy content. "Deleting the lot" was not one of them, though offline storage is. The debate is quite complex. For example, one of our oldest sites <a href="https://bbcstreaming.pages.dev/otr/">www.bbc.co.uk/otr</a> is still accessible but you could argue that it is a travesty of what its makers intended. Over time various features (for example, search) have ceased to function. You could argue that the BBC should spend money bringing this site up to date every time technology moves on, but would that be money well spent? The site still offers a number of transcripts of political interviews of the time and we may make it part of the news product. But there still may come a time when people interested in the site are better served by careful offline storage. We are also looking to apply this approach to <a href="https://bbcstreaming.pages.dev/politics97">www.bbc.co.uk/politics97. </a><br />Many have argued that <a href="https://bbcstreaming.pages.dev/ww2peopleswar">www.bbc.co.uk/ww2peopleswar </a>should remain accessible to a wide audience. Again, this is an example of a site we are looking to consolidate into a bigger product - in this case the history section of knowledge and learning.</p>
<p>Similarly, assets from many of the 170 sites will be re-presented in forms which can be more easily kept up to date. For instance, <a href="https://bbcstreaming.pages.dev/hamlet">www.bbc.co.uk/hamlet </a>has been superseded by <a href="https://bbcstreaming.pages.dev/programmes/b00pk71s">https://bbcstreaming.pages.dev/programmes/b00pk71s</a> and placed into a format which will allow the data and assets to be refreshed or editorially changed going forward. The same has been done with <a href="http://www,bbc.co.uk/annefrank">www.bbc.co.uk/annefrank</a>.</p>
<p>This is similar to what a site like the Guardian does when it updates its look and feel. A story from 1999 is still viewable but much of its context has gone, at least in the form which is most accessible, online <a href="http://www.guardian.co.uk/news/1999/dec/03/guardianobituaries?INTCMP=SRCH">http://www.guardian.co.uk/news/1999/dec/03/guardianobituaries?INTCMP=SRCH</a></p>
<p>This means that if we wish to preserve a full record of what we have published, context as well as content, we need to explore a range of options including offline storage.</p>
<p>To restate our intentions: we are moving towards a rational content lifecycle for our websites as practiced by many other sites across the web. The aim is consistent high quality everywhere on the site. We have a number of stand-alone websites which will in due course become obsolete and need to be managed. Some will be consolidated into bigger, persistently managed, content offerings. Others will be moved offline to be preserved.</p>
<p>As our plan develops we'll keep you informed.</p>
<p><em>Ian Hunter is Managing Editor, BBC Online</em></p>
<p><em><strong>Editor's note: <strike>Some people seem to be experiencing difficulties commenting on this post. This is a technical problem or bug which is being investigated. Apologies and please bear with us.</strike> Update 1 p.m. - this bug has now been fixed and comments are now open again. Apologies.</strong></em></p>]]></description>
         <dc:creator>Ian Hunter 
Ian Hunter
</dc:creator>
	<link>https://bbcstreaming.pages.dev/blogs/bbcinternet/2011/02/bbc_online_and_deleting_websit.html</link>
	<guid>https://bbcstreaming.pages.dev/blogs/bbcinternet/2011/02/bbc_online_and_deleting_websit.html</guid>
	<category>BBC Archive</category>
	<pubDate>Mon, 14 Feb 2011 16:36:08 +0000</pubDate>
</item>

<item>
	<title>Delivering Quality First: Halving the number of top level domains on BBC Online</title>
	<description><![CDATA[<p>In March last year <a href="https://bbcstreaming.pages.dev/blogs/bbcinternet/2010/03/bbc_onlines_top_level_director.html">Erik Huggers noted </a>that one symptom of the way BBC Online had grown over the years was the proliferation of TLDs that made up the site. </p>

<p>A challenge we set ourselves was to reduce the number from over 400 to under 200. This is a progress report. </p>

<p>The challenge had two parts. First, it made us ask which parts of the site really delivered in terms of audience benefit and therefore should be kept and built on. They formed part of our "fewer things, better" approach. </p>

<p>It is also true that some sites, for example, <a href="https://bbcstreaming.pages.dev/news/">/news</a> naturally absorbed older content into its online archive, allowing people to follow stories back in time. Our <a href="https://bbcstreaming.pages.dev/programmes">/programmes </a>site also works in this way, designed to provide a long term record of BBC broadcast output. However, where a site was more stand alone and its content no longer attracted users, was becoming unreliable, or video and audio assets unplayable, it was easy enough to earmark it for closure. </p>

<p>Second, we had to decide how best to manage the legacy content. Even sites which had become out of date were likely to have some historical interest. We looked into possible online archiving solutions but none fitted the bill. So we have decided to store the core content from our older websites offline, allowing interested parties in future to be able to recreate at least some of the experience they offered. </p>

<p>A number of sites which previously had their own TLDs will become absorbed into BBC Online's new products. Their assets, therefore, will continue to be available. </p>

<p>For others, a typical lifecycle is emerging. </p>

<p>This goes from live to a "mothball" state, where the content still has value but is no longer updated, for example <a href="https://bbcstreaming.pages.dev/palin/">/palin</a>.</p>

<p>At some stage mothballed content becomes stale or potentially damaging and it needs to be taken offline. At that stage a <a href="https://bbcstreaming.pages.dev/celebdaq/closed.shtml">"tombstone" </a>tells users what has happened and may offer alternatives.This also avoids breaking the user's journey. The material taken offline is stored for future reference, or deleted altogether. </p>

<p>For the record, <a href="https://bbcstreaming.pages.dev/blogs/bbcinternet/img/tld_review.xls">here is our current list of TLDs</a> which are earmarked for closure before the end of the year.</p>

<p><em>Ian Hunter is Managing Editor, BBC Online</em></p>]]></description>
         <dc:creator>Ian Hunter 
Ian Hunter
</dc:creator>
	<link>https://bbcstreaming.pages.dev/blogs/bbcinternet/2011/01/putting_quality_first_halving.html</link>
	<guid>https://bbcstreaming.pages.dev/blogs/bbcinternet/2011/01/putting_quality_first_halving.html</guid>
	<category>BBC Online</category>
	<pubDate>Mon, 24 Jan 2011 16:50:39 +0000</pubDate>
</item>

<item>
	<title>Delivering Quality First on BBC Online: Social Media</title>
	<description><![CDATA[<p>Following today's <a href="https://bbcstreaming.pages.dev/blogs/aboutthebbc/2011/01/delivering-quality-first.shtml">announcement about the re-shaping of BBC Online </a>, including the decision to close 606, Video Nation and the BBC iPlayer message board, and the disposal of h2g2,  I wanted to share some of our thinking around social media. </p>

<p>Central to the new strategy is a tighter focus on the BBC's editorial priorities to make the service better, and a 25% reduction in BBC Online's budget. Both will affect our approach to social media. </p>

<p>We believe there are three fundamental ways social media can enhance BBC Online.<br />
 <br />
First, to enrich our content. Drawing on the collective knowledge and experience of our users can improve what we publish, for everyone. One recent example of this was <a href="https://bbcstreaming.pages.dev/ahistoryoftheworld/">A History of the World</a>. Another is comments on <a href="https://bbcstreaming.pages.dev/blogs/">blogs</a> which often illuminate or extend or challenge a post in interesting ways. </p>

<p>Second, to bring more people to our content. When a user recommends something to his or her network of friends that is more likely to interest them than when the BBC makes the recommendation. More eyes on the same content means better value for money. </p>

<p>Third, to better engage audiences. Engaged users come back more frequently, increasing the value of the service to them. Richer connections with the user can help us be more open, transparent and accountable.</p>

<p>The next phase of our approach to social will be to move from a site which offers a few fairly circumscribed social experiences to one which is more social everywhere. </p>

<p>We recognise that contributions made off BBC Online can also add value to the content we publish, so we want to converge onsite and offsite contributions better than we do now. You can see the beginnings of this <a href="https://bbcstreaming.pages.dev/blogs/bbcinternet/2010/09/reflecting_online_buzz_around.html">via Buzz </a>and in our coverage of live events like the recent <a href="http://news.bbc.co.uk/sport1/hi/cricket/8296225.stm">Ashes cricket</a> or <a href="https://bbcstreaming.pages.dev/blogs/thearchers/2011/01/the_archers_60th_anniversary_live.html">the Archers 60th anniversary</a>.</p>

<p>Similarly, we are looking at the potential for broadening the interactions around some of our blogs by exposing a wider range of relevant social contributions. </p>

<p>The most notable changes are probably the closure of 606 and proposed disposal of H2G2. These sites are certainly social and in their own terms, successful. However, neither have strong links to the BBC's content. Ben Gallop on the <a href="https://bbcstreaming.pages.dev/blogs/sporteditors/">Sports Editors blog </a>explains more about the closure of 606, and its fit with the broader changes in Sport.  H2G2 is a unique community but it does not sit comfortably alongside anything else we do. The site has been created, and is sustained by, its users and our hope is to find a new owner who will nurture it in the coming years. In due course we plan to close the BBC iPlayer message board whose function is increasingly being taken on by new features within the product and BBC Online. </p>

<p>This isn't a sudden change in direction. Sites that have only a peripheral connection with our editorial purposes, don't significantly enhance our content or only engage small audiences can't any longer justify the resources they need. This is why we have <a href="https://bbcstreaming.pages.dev/blogs/radio/2010/10/changes_to_the_radio_4_messageboards.html">closed a number of message boards in the past year or so.</a> This process will continue, selectively. </p>

<p>How, then, can we make the whole of BBC Online more social? </p>

<p>In recent months we have experimented with enabling comments <a href="https://bbcstreaming.pages.dev/news/magazine-12247262">within some news pages</a>. We will be looking to extend this in the coming months, developing the editors' picks feature and the ability to rate other people's comments.</p>

<p>BBC iPlayer users are able to <a href="http://iplayerhelp.external.bbc.co.uk/help/using_bbc_iplayer/friends_feature">recommend programmes </a>(and add a comment) and have these posted to  their accounts in Facebook or Twitter. Again, this is a small start to something we plan to extend more widely.  Some programmes and networks will continue to experiment with, and improve, the official BBC pages we manage on Facebook (such as <a href="http://www.facebook.com/bbcradio1">BBC Radio 1</a> and <a href="http://www.facebook.com/pages/BBC-EastEnders/169383494938">Eastenders</a>) and Youtube. And we'll continue to explore collaborations like <a href="https://bbcstreaming.pages.dev/music/soundof/2011/artists/jamesblake/">Sound of 2011 </a>with social sites like Songkick and LastFM.</p>

<p>Much of this is standard practice across the web, of course, and we need to evolve to meet the changing expectations of our users. The size of BBC Online, the legacy systems on which it was built, our commitment to maintaining the highest editorial standards and to providing a safe social environment mean that the task is complex. And in a world where we have fewer people and less money we have to focus on doing the things which promise to offer the biggest benefits to all of our users. </p>

<p><em>Ian Hunter is Managing Editor, BBC Online</em></p>

<p><strong>Read Erik Huggers' post: <a href="https://bbcstreaming.pages.dev/blogs/aboutthebbc/2011/01/delivering-quality-first.shtml">"Reshaping BBC Online"</a></strong></p>

<p><strong>Read Ben Gallop's post: <a href="https://bbcstreaming.pages.dev/blogs/sporteditors/2011/01/changes_to_bbc_sport_online.html">"Changes to Sport Online".</a></strong></p>]]></description>
         <dc:creator>Ian Hunter 
Ian Hunter
</dc:creator>
	<link>https://bbcstreaming.pages.dev/blogs/bbcinternet/2011/01/delivering_quality_first_on_bb.html</link>
	<guid>https://bbcstreaming.pages.dev/blogs/bbcinternet/2011/01/delivering_quality_first_on_bb.html</guid>
	<category>BBC Online</category>
	<pubDate>Mon, 24 Jan 2011 11:00:46 +0000</pubDate>
</item>

<item>
	<title>BBC iPlayer Content Protection Enhancements</title>
	<description><![CDATA[<p>A number of our users <a href="https://bbcstreaming.pages.dev/blogs/bbcbackstage/2010/02/what-happened-to-iplayer-strea.shtml">have expressed concern about BBC iPlayer's recent content protection enhancements</a>. It's a complex area so I asked our techical team for an explanation of what has happened. Here it is:</p>

<p>We make iPlayer content available in a variety of media formats (WMV, H.264, 3GP, MPEG, etc) many of which are <a href="http://en.wikipedia.org/wiki/Open_source">open source</a>, or at least not tied to a particular company's products. </p>

<p>In order to respect the rights agreements that allow us to make the content available in the first place, we use a range of content protection techniques and technologies:</p>

<p>- for downloads, we use digital rights management systems (Windows Media, Adobe, and OMA)</p>

<p>- for streaming, we use systems like SSL, RTMP, RTSP, HTTP</p>

<p>Many of these content delivery methods are open-source.</p>

<p>We also implement a range of technologies that attempt to check that our content is being played out in iPlayer, and not in an unauthorised 3rd-party application. This is because we need to be as certain as we can be that our content rights restrictions are being respected. </p>

<p>This is the key to the concerns being expressed at the moment: before we allow a device to access our content we need to check that it is iPlayer and not an application which might break our rules - for example, by storing programmes beyond the 30 day limit, or playing them outside the UK.</p>

<p>We know that a number of applications have been making unauthorised use of some media types and we have tightened security accordingly - this was done for several of the formats and content delivery types, not just for Flash. The result was that some applications that 'deep link' to our content may no longer work.</p>

<p>It's important to note that this has nothing to do with Flash, and it's nothing to do with support for open-source. In fact we continue to make our content available as H.264 or SSL, both of them open standards that have nothing to do with Flash or with Adobe. It's simply that the first people to be affected by this change happened to be linking to our Flash streams, which now have similar protection levels to our open-source streams.</p>

<p>The discussion around this issue suggests that two different uses of the term "open source" are being conflated:</p>

<p>a) we continue to make our content available in a range of open-source formats</p>

<p>b) unfortunately <a href="http://www.theregister.co.uk/2010/02/24/iplayer_xbmc_adobe_swf_verification/">one of the applications that stopped working was XBMC</a>, an open-source media player.</p>

<p>But the two "open sources" are quite different to each other - we have no particular attachment to Flash over open-source formats. In fact most of iPlayer is built on open-source products. However, we do need to protect our content from applications that threaten to make unauthorised use of it, even if those applications are themselves open source.</p>

<p>To answer <a href="https://bbcstreaming.pages.dev/blogs/bbcinternet/2010/02/round_up_wednesday_24_february.html#P92928774">Mo's comment</a>, of course the BBC does not want people to download content illegally. That's precisely why we have built rights related constraints into BBC iPlayer. If an application becomes broken, people will be able to find alternatives which are legal and that we support. BBC iPlayer is already available on <a href="https://bbcstreaming.pages.dev/iplayer/where_to_get_iplayer/">many, many devices and platforms which are legal and supported </a>and in the coming year we will be adding as many new ones as we can. </p>

<p><em>Ian Hunter is Managing Editor, BBC Online</em></p>]]></description>
         <dc:creator>Ian Hunter 
Ian Hunter
</dc:creator>
	<link>https://bbcstreaming.pages.dev/blogs/bbcinternet/2010/03/bbc_iplayer_content_protection.html</link>
	<guid>https://bbcstreaming.pages.dev/blogs/bbcinternet/2010/03/bbc_iplayer_content_protection.html</guid>
	<category>iPlayer</category>
	<pubDate>Fri, 05 Mar 2010 13:13:38 +0000</pubDate>
</item>

<item>
	<title>Welcome to BBC iD</title>
	<description><![CDATA[<p><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><img alt="Blogs migration picture" src="https://bbcstreaming.pages.dev/blogs/bbcinternet/img/blogs_mig_cropped.jpg" width="300" height="174" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /></span>BBC iD is the new sign in system for <a href="https://bbcstreaming.pages.dev/">BBC Online</a>. It's currently being rolled out across all services that require a user to register or sign in. </p>

<p>On Monday November 2nd we'll be switching all of the <a href="https://bbcstreaming.pages.dev/blogs/">BBC's blogs</a> to BBC iD from the previous BBC membership system. And in the New Year our <a href="https://bbcstreaming.pages.dev/messageboards/newguide/">message boards</a> and other communities will be heading down the same route. </p>

<p>Those of you posting comments to the <a href="https://bbcstreaming.pages.dev/strictlycomedancing/">Strictly Social website</a> over the weekend may have been asked to upgrade your BBC membership to the new BBC iD system. And anyone who has contributed to the <a href="https://bbcstreaming.pages.dev/dna/mbiplayer/">BBC iPlayer message boards</a> in recent weeks will already have created a BBC iD. They'll also be aware of some of the teething problems we've had. These should by now have been ironed out. </p>

<p>By March 2010 BBC iD will be the single sign in for all BBC Online services. If you have an existing BBC membership account for blogs, message boards or other services at some point in the next few months you will be automatically prompted to upgrade to BBC iD.</p>

<p>We do need to replace the old system, but we don't underestimate the inconvenience the transition will represent for some of our users. We apologise for this and hope that you will find the service improvements that BBC iD will support over the coming months for example, working on mobiles - make it all worthwhile. </p>

<p>We've tried to answer the questions you may have about the new system <a href="https://id.bbc.co.uk/users/help">here</a>. </p>

<p>If we've missed anything, please let us know. Most users should be able to upgrade their account from a BBC membership to a BBC iD when prompted with a minimum of fuss. </p>

<p>We'll be keeping you up to date with the roll-out of BBC iD via the <a href="https://bbcstreaming.pages.dev/blogs/bbcinternet">BBC Internet blog</a>. </p>

<p><strong>NB: There's one thing you will need to think about if you have more than one BBC membership account:</strong><br />
If you have more than one BBC membership you'll only be able to upgrade one of those accounts to BBC iD using your preferred username and email address. That BBC iD account will retain links to your previous membership account and any comments and posts you made using it. So if you have more than one BBC membership, make sure you upgrade your favourite one.</p>

<p><br />
<em>Ian Hunter is Managing Editor, Internet Group, BBC Future Media and Technology.</em></p>]]></description>
         <dc:creator>Ian Hunter 
Ian Hunter
</dc:creator>
	<link>https://bbcstreaming.pages.dev/blogs/bbcinternet/2009/10/welcome_to_bbc_id.html</link>
	<guid>https://bbcstreaming.pages.dev/blogs/bbcinternet/2009/10/welcome_to_bbc_id.html</guid>
	<category>BBC iD</category>
	<pubDate>Thu, 29 Oct 2009 16:08:00 +0000</pubDate>
</item>

<item>
	<title>iPlayer Day: The blue-eyed boy</title>
	<description><![CDATA[<p>Today it's easy to forget how fraught a journey we had in the early stages of a project which I joined in the summer of 2006</p>

<p>By then the BBC iPlayer was well on its way from being the BBC's blue eyed boy to something more like a spectre at the feast.  Every month it seemed a rival broadcaster launched its own video on demand service. <a href="http://www.brandrepublic.com/InDepth/Opinion/670343/Andrew-Walmsley-digital-BBC-iPlayer-gets-off-crawling-start/">One commentator remarked</a> in July 2007 that the "the BBC has gone from market leader to market laggard". We worried that we would be too late.</p>

<p>Of course, we understood that we - the BBC and its partners at Siemens and Red Bee Media - were embarked on the heroic transformation of linear broadcasting... but who would care about that if the thing didn't work?</p>

<p>There were dark mutterings - some from BBC staff - about iPlayer's peer to peer download system and how it might mangle software and bankrupt the unwary. <a href="http://mou.me.uk/2007/08/25/woops-kontiki-did-it-again-kserviceexe-and-the-bbc-iplayer/">Had we chosen the wrong system</a>?</p>

<p>We also worried that it would work too well. Our initial projections suggested that if 40,000 people downloaded programmes at the same time the internet would grind to a halt. How could we monitor this - and what could we do? Now that daily streams easily top a million we've relaxed a bit.</p>

<p>We owe a huge debt of gratitude to the hundreds, then thousands, who signed up to iPlayer during its long months behind a walled garden. The early trialists were encouraging and, above all, patient. For three weeks in February 2007 we suspended the service entirely. Many of them were actively helpful - our operations team would eagerly scan the <a href="https://bbcstreaming.pages.dev/dna/mbiplayer">message board</a> to see if anyone had a solution for that day's problem.</p>

<p>By June 2007, 15000 had signed up though fewer stayed the course. A drawback of our first design was that it drew as much attention to the (all too many) programmes we didn't have as to those we did. Another was beginning with downloads rather than streaming. This brought more technical problems - with browsers, firewalls and the rest - and made it trickier to explain how to make iPlayer work.</p>

<p>By the Autumn, things were looking up and we began to grapple with more traditional editorial concerns. If there was no watershed on the web how could we warn users about grown up content? (Our <a href="http://iplayerhelp.external.bbc.co.uk/help/about_iplayer/set_up_pg">parental lock system</a>, built in record time.) Could we find a way to quickly edit programme descriptions that had errors? (Yes, but it took a long time to enable that.) Would millions of people call our helpdesk team and bankrupt the BBC? (Not so far.)</p>

<p>And then we were free! <a href="https://bbcstreaming.pages.dev/blogs/bbcinternet/anthony_rose/">Anthony Rose </a>and the team sorted out streaming and much else. What looked like a high risk Christmas Day launch was smooth as cream. iPlayer was being talked about everywhere, and everywhere was being praised. The blue eyed boy had returned...</p>

<p><a href="http://www.flickr.com/photos/bbccouk/3099405083/" title="iplayerbillboard by bbccouk, on Flickr"><img src="http://farm4.static.flickr.com/3273/3099405083_c677a070b5_o.jpg" width="430" height="322" alt="iplayerbillboard" /></a></p>

<p>In all this, however, the thing that brought home the transformation most powerfully was sitting on a bus one night in London with my wife. Behind us were two Russians in enthusiastic conversation in their native language. In mid sentence came the English words "BBC iPlayer". I think they liked it.</p>

<p><em>Ian Hunter is Managing Editor, Internet Group, BBC Future Media and Technology.</em></p>]]></description>
         <dc:creator>Ian Hunter 
Ian Hunter
</dc:creator>
	<link>https://bbcstreaming.pages.dev/blogs/bbcinternet/2008/12/iplayer_day_the_blueeyed_boy.html</link>
	<guid>https://bbcstreaming.pages.dev/blogs/bbcinternet/2008/12/iplayer_day_the_blueeyed_boy.html</guid>
	<category>iPlayer</category>
	<pubDate>Fri, 12 Dec 2008 11:00:00 +0000</pubDate>
</item>

<item>
	<title>A More Helpful Help Site</title>
	<description><![CDATA[<p><a href="https://bbcstreaming.pages.dev/help/"><img alt="bbc_help.png" src="https://bbcstreaming.pages.dev/blogs/bbcinternet/img/bbc_help.png" width="134" height="104" /></a>Last week, we launched a new version of the <a href="https://bbcstreaming.pages.dev/help/">BBC Help</a> site. Previously, it was just a collection of bits of technical advice about using <a href="https://bbcstreaming.pages.dev/">bbc.co.uk</a>, and the most used section by far was about <a href="https://bbcstreaming.pages.dev/help/web/index.shtml#1">how to make a BBC page your homepage</a>. </p>

<p>The new site draws on the wealth of Frequently Asked Questions (FAQ) and other information that exists across bbc.co.uk and tries to guide people more effectively towards the area most likely to actually help them. Sections include <a href="https://bbcstreaming.pages.dev/help/accessibility/">accessibility</a>, <a href="https://bbcstreaming.pages.dev/help/radio/">radio</a>, <a href="https://bbcstreaming.pages.dev/help/iplayer/">BBC iPlayer</a> and <a href="https://bbcstreaming.pages.dev/help/mobile/">mobile</a>. I think we've made it look a lot nicer, too.</p>

<p>This launch is part of a bigger project looking at how we can improve the way that we interact with our audience. Currently we get over 40,000 emails a month from users, and those are just the ones that we can count because they come through the "official" central route. There are many other routes which we don't record. </p>

<p>Because of the way the website <a href="https://bbcstreaming.pages.dev/blogs/bbcinternet/2007/12/brandons_history_of_bbc_on_the_2.html">evolved</a>  - bit by bit, with lots of small teams working on specific parts of the website - there are now over a hundred different routes on bbc.co.uk for sending <a href="https://bbcstreaming.pages.dev/feedback/">feedback</a>. This means that the way we deal with feedback can be inconsistent and, in the worst case, a "contact us" button can be left open when the programme team has moved on. </p>

<p><a href="http://news.bbc.co.uk/player/nol/newsid_7220000/newsid_7223200/7223286.stm?bw=bb&mp=rm&news=1&nol_storyid=7223286&bbcws=1#"><img alt="newswatch_ian_hunter.jpg" src="https://bbcstreaming.pages.dev/blogs/bbcinternet/img/newswatch_ian_hunter.jpg" width="175" height="98" /></a>This has led to some understandable grumbling and the <a href="https://bbcstreaming.pages.dev/bbctrust/">BBC Trust</a> has asked us to improve things. Ray Snoddy <a href="http://news.bbc.co.uk/player/nol/newsid_7220000/newsid_7223200/7223286.stm?bw=bb&mp=rm&news=1&nol_storyid=7223286&bbcws=1#">recently tackled me on this on Newswatch</a>, too. </p>

<p>Part of the solution is for us to agree some common standards for how feedback should be handled. We're writing some advice for teams at the moment, and will be publishing these as part of the <a href="https://bbcstreaming.pages.dev/guidelines/newmedia/">New Media Guidelines</a> later this year, so that our users know will know what to expect, too.</p>

<p>Another part of the solution is to improve the information that we provide on bbc.co.uk and make it easier to find. A huge proportion of those 40,000 emails (not to mention the ones that never get reported centrally) ask questions about our programmes or services. And the money we spend answering them comes out of the budget we have to spend on the programmes and services themselves. Feedback is valued and responding to it is an important part of the service we provide, but we do want to make is easier for people to find things for themselves. If we can provide better information on bbc.co.uk (through sites such as <a href="https://bbcstreaming.pages.dev/programmes/">BBC Programmes</a>), and help users to find it (through searchable and rateable FAQs like those on the <a href="http://iplayersupport.external.bbc.co.uk/cgi-bin/bbciplayer.cfg/php/enduser/home.php?p_sid=zs3CrK*i">BBC iPlayer help pages</a>), more people will be able to answer their own questions without having to send us an email.</p>

<p>The new Help site is another step on this journey. Any feedback is welcome!</p>

<p><em>Ian Hunter is Managing Editor, Internet, BBC Future Media and Technology</em></p>]]></description>
         <dc:creator>Ian Hunter 
Ian Hunter
</dc:creator>
	<link>https://bbcstreaming.pages.dev/blogs/bbcinternet/2008/04/a_more_helpful_help_site_1.html</link>
	<guid>https://bbcstreaming.pages.dev/blogs/bbcinternet/2008/04/a_more_helpful_help_site_1.html</guid>
	<category>BBC Online</category>
	<pubDate>Tue, 08 Apr 2008 12:37:39 +0000</pubDate>
</item>


</channel>
</rss>

 
