en Technology + Creativity at the Ö÷²¥´óÐã Feed Technology, innovation, engineering, design, development. The home of the Ö÷²¥´óÐã's digital services. Mon, 20 Feb 2023 14:33:13 +0000 Zend_Feed_Writer 2 (http://framework.zend.com) /blogs/internet Expanding Our Horizons With ChatGPT Mon, 20 Feb 2023 14:33:13 +0000 /blogs/internet/entries/1c6fd26f-fcd5-473f-9535-f3652ada92ca /blogs/internet/entries/1c6fd26f-fcd5-473f-9535-f3652ada92ca Bill Thompson Bill Thompson

I was a sceptic about the impact of the new tranche of generative AI tools until this week when two of my friends demonstrated how they could be used in genuinely transformative ways that go far beyond faking essays or acting as a search interface with poor boundaries and a tendency to invent things that look plausible.

Last week in his regular Exponential View newsletter Azeem Azhar described in detail how he had used ChatGPT to design a new board game that combined the characteristics of Ticket to Ride and Azul, shaping it around the idea of discovering elements, and designing selection of game characters based around historical chemists.

It's a subscriber-only post but .

Then another friend, , via GitHub Copilot, to write the code he needed to scrape a website as part of a project to build a podcast interface. As he wrote:

"Using GitHub Copilot to write code and calling out to GPT-3 programmatically to dodge days of graft actually brought tears to my eyes. I’ve coded, mostly as a hobby, my whole life – it’s a big creative outlet alongside writing – it’s so rarely felt like this. It feels like flying".

These examples brought home to me the real power of these new tools, not as generators of random boilerplate text for business letters or marketing blurb, or as complex and potentially misleading interfaces to search engines, but as collaborators in our creative activity, supporting idea generating, doing some of the low-level heavy lifting, and sitting on our shoulders like supportive angels. 

One of the things that also occurred to me reading Azeem's piece was that ChatGPT didn’t get tired.   For once, a line from the Terminator felt entirely appropriate to describe a current ML system: "It doesn't feel pity, or remorse, or fear. And it absolutely will not stop... ever, until you have finished your project!"

That’s not to say that these tools live up to the exaggerated claims being made for them, as the rather embarrassing error about the capabilites of the James Webb Space Telescope that Google made at the announcement of their Bard LLM – and the consequent $100bn drop in Alphabet’s value – demonstrated.

Of course, Bard wasn’t being malicious, or even foolish, because these tools don’t have any capacity for feeling. They can’t lie because lying is saying something false with intent, and – we can’t say this strongly enough – they have no intent. 

Pull the curtain away from GPT or Stable Diffusion and there’s no wizard, just a vast array of weightings running on a power-hungry set of GPUs. When ChatGPT engages with you it’s basically taking a drunkard’s walk through the forest of word frequencies, calling out the names of each tree as it leans on it before staggering onward. Like taking your own wine to an unlicensed restaurant with zero corkage, you bring the meaning – and because we are so good at projecting into the empty eyes of our machines (and pets.. but we can have that argument another time) we find all the profundity we’re looking for.  

Perhaps one day we will develop general AI and the machine will both know what it is saying and – crucially – know that it is a thing that is saying something to us. When that happens we’ll look back on the current fuss over LLMs the way astronomers consider astrology – there was some good data collection and analysis but the fundamental model was so disconnected from reality that it was dangerous.

But even with the current limitations, it’s clear that these tools already have a real role as well-resourced, untiring support for creativity and ideation, with the ability to smash concepts together and produce fascinating results, and that may be enough to change the way we all work, especially in the creative industries.  Just imagine what a hard-pressed producer looking for a new entertainment format could do with them.

]]>
0
Ö÷²¥´óÐã pages removed from Google search results: 2023 Sun, 01 Jan 2023 16:51:10 +0000 /blogs/internet/entries/403e0aff-b46f-4c03-80a8-c44bbf59ec92 /blogs/internet/entries/403e0aff-b46f-4c03-80a8-c44bbf59ec92 Clare Hudson Clare Hudson

In 2014 the that individuals can ask search engines to remove certain web pages from their results. Those pages usually contain personal information.

Google subsequently removed links from specific searches and continues to delist pages for some results. This includes some Ö÷²¥´óÐã pages. These pages are not removed from the Google index entirely, nor from Ö÷²¥´óÐã Online. The latest removals are listed below.

Read more on the Ö÷²¥´óÐã's archive policies and find lists of earlier removals.

One important caveat when looking through this list: we are not told who has requested the delisting. We should not leap to conclusions as to who is responsible. The request may not be from the apparent subject of a story.

February 2024
http://news.bbc.co.uk/2/hi/uk_news/scotland/glasgow_and_west/5181326.stm
/news/uk-scotland-tayside-central-45116064
/news/uk-scotland-tayside-central-45952162
/news/uk-23493106
/news/uk-england-gloucestershire-12251572
https://www.bbc.com/news/uk-england-gloucestershire-11998491
http://news.bbc.co.uk/2/hi/uk_news/england/london/8439854.stm
http://news.bbc.co.uk/2/hi/uk_news/england/2843343.stm
http://news.bbc.co.uk/2/hi/uk_news/england/2337425.stm
http://news.bbc.co.uk/2/hi/uk_news/england/london/7395940.stm
https://www.bbc.com/news/uk-england-sussex-12898744.amp
https://www.bbc.com/news/uk-england-sussex-13088655.amp
https://www.bbc.com/news/uk-england-hampshire-48297831
https://www.bbc.com/news/uk-scotland-south-scotland-29801856
/news/uk-scotland-south-scotland-30452017.amp
http://news.bbc.co.uk/2/hi/uk_news/england/cambridgeshire/3131626.stm
/news/uk-england-sussex-15675344.amp
https://www.bbc.com/news/uk-england-humber-33063118
https://www.bbc.com/news/uk-england-lincolnshire-42029190
http://news.bbc.co.uk/1/hi/england/manchester/8683064.stm
https://www.bbc.com/news/uk-england-birmingham-48123164
https://www.bbc.com/news/uk-england-gloucestershire-11317347
https://www.bbc.com/news/uk-northern-ireland-13286000.amp
https://www.bbc.com/news/uk-england-london-58467011
https://www.bbc.com/news/uk-england-london-60848804
/news/uk-scotland-north-east-orkney-shetland-46976523
https://www.bbc.com/cymrufyw/38168178
http://news.bbc.co.uk/2/hi/uk_news/england/6503619.stm
/news/uk-england-manchester-25563392.amp
/news/uk-scotland-north-east-orkney-shetland-46923229
/news/uk-wales-north-east-wales-12769447
/news/uk-wales-north-east-wales-33258564
http://news.bbc.co.uk/2/hi/uk_news/england/4683863.stm
/drama/hustle/episode6_series2_yourreviews.shtml
https://www.bbc.com/news/uk-wales-mid-wales-38983572
https://www.bbc.com/news/uk-scotland-tayside-central-39478204.amp
/news/uk-wales-34898071
/news/uk-wales-35864598
http://news.bbc.co.uk/1/hi/programmes/moneybox/8052580.stm
/news/uk-england-hampshire-46338545
/news/uk-england-16149258
/news/live/uk-england-tyne-36979890
/news/uk-wales-mid-wales-39339315
https://www.bbc.com/news/uk-england-kent-17769747.amp
/news/uk-england-oxfordshire-38610512.amp
/news/uk-england-oxfordshire-38655059.amp
http://news.bbc.co.uk/1/hi/england/wiltshire/7337337.stm
https://www.bbc.com/news/uk-wales-south-west-wales-38175443
https://www.bbc.com/news/uk-scotland-tayside-central-16276615

Jan 2024
/news/topics/cdnpj59gj1nt?page=7
http://news.bbc.co.uk/1/hi/northern_ireland/8621079.stm
https://www.bbc.com/portuguese/brasil-39521454
https://www.bbc.com/news/uk-england-merseyside-33992110
https://www.bbc.com/news/uk-scotland-south-scotland-29831224
https://www.bbc.com/mundo/ultimas_noticias/2012/04/120426_ultnot_panama_italia_vitola_bd
https://www.bbc.com/news/uk-wales-south-east-wales-38904521
https://www.bbc.com/news/uk-wales-south-east-wales-38969769
https://www.bbc.com/news/uk-wales-south-east-wales-38985265
https://www.bbc.com/news/uk-wales-south-east-wales-38985265.amp
http://news.bbc.co.uk/1/hi/england/2254460.stm
http://news.bbc.co.uk/1/hi/england/cambridgeshire/3536600.stm
http://news.bbc.co.uk/2/hi/uk_news/england/cambridgeshire/3532060.stm
http://news.bbc.co.uk/2/hi/uk_news/england/cambridgeshire/3940581.stm
http://news.bbc.co.uk/1/hi/wales/2197143.stm
https://www.bbc.com/news/uk-england-london-57674494
https://www.bbc.com/news/uk-england-london-61732805
http://news.bbc.co.uk/1/hi/england/west_midlands/4956636.stm
/cymrufyw/38981445
/cymrufyw/38981445.amp
/news/uk-wales-south-east-wales-38904521
/news/uk-wales-south-east-wales-38904521.amp
/news/uk-wales-south-east-wales-38920336
/news/uk-wales-south-east-wales-38920336.amp
/news/uk-wales-south-east-wales-38969769
/news/uk-wales-south-east-wales-38969769.amp
/news/uk-wales-south-east-wales-38985265
/news/uk-wales-south-east-wales-38985265.amp
http://news.bbc.co.uk/2/hi/uk_news/england/2822209.stm
http://news.bbc.co.uk/1/hi/england/sussex/6427183.stm
http://news.bbc.co.uk/1/hi/england/sussex/7192780.stm
http://news.bbc.co.uk/1/hi/england/sussex/7196792.stm
http://news.bbc.co.uk/1/hi/england/sussex/7230638.stm
http://news.bbc.co.uk/2/hi/england/sussex/7514636.stm
/lancashire/content/articles/2007/10/12/faith_eid_daniyah_hafiz_explains.shtml
/news/uk-england-dorset-47282560
http://news.bbc.co.uk/2/hi/uk_news/scotland/4510127.stm
/news/uk-england-hampshire-24840376
https://www.bbc.com/news/uk-england-hampshire-24840376
http://news.bbc.co.uk/1/hi/england/2822209.stm
https://www.bbc.com/news/uk-england-london-55355531
/news/av/uk-england-york-north-yorkshire-40276141
/news/uk-england-york-north-yorkshire-40276137
https://www.bbc.com/news/health-57318424
http://news.bbc.co.uk/2/hi/europe/8372080.stm
https://www.bbc.com/news/uk-england-essex-49436377
https://www.bbc.com/news/uk-england-manchester-39306738
/news/uk-northern-ireland-43372972
/news/uk-northern-ireland-43736292
https://www.bbc.com/news/uk-england-lincolnshire-43669950
/news/uk-england-manchester-37120215
http://news.bbc.co.uk/2/hi/middle_east/1873518.stm
/cymrufyw/38168178
/cymrufyw/38168178.amp
/news/uk-wales-south-west-wales-38175443
/news/uk-wales-south-west-wales-38175443.amp
https://ichef.bbci.co.uk/news/976/cpsprodpb/1212D/production/_92792047_fiddling_violinist_11.jpg.webp
https://ichef.bbci.co.uk/news/976/cpsprodpb/28B3/production/_92791401_bethandociviolinst3.jpg.webp
https://ichef.bbci.co.uk/news/976/cpsprodpb/5C74/production/_92786632_bethandociviolinist2.jpg.webp

December 2023
/news/uk-england-london-29956787
/news/health-57318424
/news/uk-england-27204293
https://ichef.bbci.co.uk/news/222/mcs/media/images/74510000/jpg/_74510508_10b1d6ea-1597-45de-9e94-f4777b3e1354.jpg
/news/av/uk-england-birmingham-58508557
/news/av/uk-england-leeds-51333461
/news/av/uk-england-wiltshire-50578578
https://www.bbc.com/news/av/uk-england-sussex-47674613
http://news.bbc.co.uk/2/hi/uk_news/england/sussex/7514636.stm
http://news.bbc.co.uk/1/hi/england/london/6918712.stm
http://news.bbc.co.uk/2/hi/uk_news/england/7388519.stm
http://news.bbc.co.uk/2/hi/uk_news/england/london/6918712.stm
https://ichef.bbci.co.uk/images/ic/1024x576/p074bzff.jpg
https://www.bbc.com/news/av/uk-england-coventry-warwickshire-60700014
/news/av/uk-england-nottinghamshire-48091523
/news/av/world-us-canada-48834691
https://www.bbc.com/news/av/world-us-canada-47871463
/news/av/uk-england-birmingham-60946722
/news/av/uk-england-coventry-warwickshire-60700014
/news/av/uk-england-kent-48506190
/news/av/uk-wales-57095274
/news/av/world-us-canada-47871463
/news/uk-england-leicestershire-55264724
http://news.bbc.co.uk/2/hi/uk_news/england/oxfordshire/8052109.stm
https://ichef.bbci.co.uk/news/976/cpsprodpb/15BFA/production/_125328098_josepholswang.jpg
https://www.bbc.com/news/world-latin-america-29361452
/news/uk-england-berkshire-59943881
https://www.bbc.com/news/uk-england-berkshire-59871751
https://www.bbc.com/news/uk-england-berkshire-59896099
https://www.bbc.com/news/uk-england-berkshire-60001525
https://www.bbc.com/news/uk-56834722
http://news.bbc.co.uk/2/hi/uk_news/england/cambridgeshire/3555396.stm
https://www.bbc.com/news/uk-wales-23993139
https://www.bbc.com/news/uk-wales-23993139?tblang=english
https://www.bbc.com/news/uk-wales-north-east-wales-33258564
/news/uk-england-sussex-15674782.amp
http://www.bbc.co.uk/news/uk-england-bristol-25725115
https://www.bbc.com/news/av/uk-england-hampshire-27532746
https://www.bbc.com/news/uk-england-bristol-41499605
https://ichef.bbci.co.uk/news/976/cpsprodpb/164A8/production/_98140319_mediaitem98140318.jpg
http://news.bbc.co.uk/1/hi/england/7859215.stm
/news/live/uk-england-devon-41817853
https://ichef.bbci.co.uk/images/ic/400xn/p0cm602x.jpg
http://news.bbc.co.uk/1/hi/scotland/4091636.stm
http://news.bbc.co.uk/1/hi/scotland/4510127.stm
http://news.bbc.co.uk/2/hi/uk_news/scotland/4091636.stm
https://www.bbc.com/news/uk-england-essex-49757611
https://www.bbc.com/news/uk-england-essex-58632294
https://www.bbc.com/news/av/uk-politics-18186936
https://www.bbc.com/news/uk-england-manchester-19561273
https://ichef.bbci.co.uk/news/304/mcs/media/images/62826000/jpg/_62826872_mcbride.jpg
https://ichef.bbci.co.uk/news/640/mcs/media/images/62826000/jpg/_62826872_mcbride.jpg
http://news.bbc.co.uk/2/hi/uk_news/england/2256707.stm
/news/uk-england-leicestershire-39232287
/news/technology-18672068
https://www.bbc.com/news/uk-northern-ireland-37717937
https://www.bbc.com/news/uk-england-nottinghamshire-37957208.amp

November 2023
http://news.bbc.co.uk/1/hi/england/sussex/7182331.stm
http://news.bbc.co.uk/2/hi/uk_news/england/london/4084193.stm
/news/uk-england-berkshire-59871751?pinned_post_locator=urn:bbc:cps:curie:asset:73ffc4ed-87c0-4081-854f-ef6c5ab6c11d&pinned_post_asset_id=59871751&pinned_post_type=share
/news/uk-england-berkshire-59896099?at_medium=RSS&at_campaign=KARANGA
/news/uk-northern-ireland-35896174
/news/uk-northern-ireland-37646103
/news/uk-northern-ireland-37717937
https://www.bbc.com/news/technology-18672068
https://www.bbc.com/portuguese/internacional-36802927
/news/av/uk-england-hampshire-27532746
/news/uk-27563906
/news/uk-england-bristol-41499605
/news/uk-england-oxfordshire-36738656
http://news.bbc.co.uk/2/hi/uk_news/7048304.stm
http://news.bbc.co.uk/1/hi/england/2896639.stm
http://news.bbc.co.uk/1/hi/business/7663475.stm
https://www.bbc.com/news/uk-scotland-north-east-orkney-shetland-11206289
/news/uk-scotland-north-east-orkney-shetland-11589805
http://news.bbc.co.uk/sport2/hi/football/teams/d/dundee/9015786.stm
/news/uk-wales-south-east-wales-38893376
https://www.bbc.com/travel/article/20130802-in-brief-the-case-of-the-disappearing-hexapus
/news/uk-england-south-yorkshire-37308710
http://news.bbc.co.uk/1/hi/england/2254941.stm
http://news.bbc.co.uk/1/hi/uk/3099108.stm
https://ichef.bbci.co.uk/news/976/cpsprodpb/104EF/production/_98799766_hi031018906.jpg.webp
https://ichef.bbci.co.uk/news/976/mcs/media/images/83512000/jpg/_83512851_seanhenderson.jpg
http://news.bbc.co.uk/1/hi/england/cambridgeshire/3555396.stm
http://news.bbc.co.uk/1/hi/england/cambridgeshire/3563356.stm
http://news.bbc.co.uk/2/hi/uk_news/england/sussex/7294499.stm
http://news.bbc.co.uk/1/hi/england/2256707.stm
http://www.bbc.co.uk/news/uk-england-gloucestershire-11317347
http://www.bbc.co.uk/news/uk-england-gloucestershire-11998491
http://news.bbc.co.uk/1/mobile/england/london/8421535.stm
https://www.bbc.com/news/10422008
http://news.bbc.co.uk/1/hi/england/cambridgeshire/3166561.stm
http://news.bbc.co.uk/1/hi/england/cambridgeshire/3166809.stm
http://news.bbc.co.uk/1/hi/england/cambridgeshire/3555396.stm
http://news.bbc.co.uk/1/hi/england/cambridgeshire/3555660.stm
http://news.bbc.co.uk/2/hi/uk_news/england/cambridgeshire/3166561.stm
http://news.bbc.co.uk/1/hi/england/2260284.stm
http://news.bbc.co.uk/1/hi/england/cambridgeshire/3538816.stm
http://news.bbc.co.uk/1/hi/uk/3099108.stm
http://news.bbc.co.uk/media/images/38254000/jpg/_38254666_policepaedo150.jpg
/news/uk-england-south-yorkshire-37108036
http://news.bbc.co.uk/1/hi/uk/7048304.stm
https://www.bbc.com/news/uk-england-south-yorkshire-37108036
/news/uk-england-lincolnshire-42029190
/news/uk-england-lincolnshire-43669950
/news/uk-england-york-north-yorkshire-24385557
/news/uk-england-essex-16661062
/news/uk-england-cornwall-35383743.amp
https://www.bbc.com/news/uk-england-birmingham-46280539.amp
/news/uk-england-kent-19627049
/news/av/health-61544423
/news/uk-21442040
http://news.bbc.co.uk/2/hi/uk_news/england/london/8421535.stm
https://ichef.bbci.co.uk/images/ic/1920x1080/p0c8d854.jpg

October 2023
/news/uk-england-berkshire-59896099.amp
/news/uk-england-berkshire-60001525.amp
https://www.bbc.com/news/uk-england-berkshire-59943881
https://www.bbc.com/news/uk-england-berkshire-59943881.amp
https://ichef.bbci.co.uk/news/976/cpsprodpb/7947/production/_113274013_e9e7f0da-2ffb-4456-bc68-2f44734fdc33.jpg
/news/20417755
https://www.bbc.com/news/20417755.amp
http://news.bbc.co.uk/1/hi/uk/6107780.stm
http://news.bbc.co.uk/2/hi/uk_news/england/2254460.stm
http://news.bbc.co.uk/2/hi/uk_news/england/cambridgeshire/3166809.stm
http://news.bbc.co.uk/2/hi/uk_news/england/cambridgeshire/3538816.stm
http://news.bbc.co.uk/2/hi/uk_news/england/cambridgeshire/3555660.stm
http://news.bbc.co.uk/media/images/38252000/jpg/_38252171_stevens300.jpg
https://www.bbc.com/news/uk-northern-ireland-47388359
/news/uk-northern-ireland-47359354
/news/uk-northern-ireland-47480106
/news/live/uk-england-tyne-48888823
/news/uk-england-essex-49436377
https://www.bbc.com/news/world-latin-america-38328490.amp
/news/uk-northern-ireland-47388359
/news/uk-northern-ireland-48253078
/news/uk-northern-ireland-48266241
/news/uk-england-essex-49436377.amp
https://www.bbc.com/news/uk-england-11479831
https://www.bbc.com/news/uk-england-kent-19627049
http://news.bbc.co.uk/2/hi/uk_news/england/leicestershire/4376405.stm
https://www.bbc.com/news/uk-england-coventry-warwickshire-47232767
/news/uk-england-manchester-39306738

September 2023
http://news.bbc.co.uk/2/hi/uk_news/scotland/glasgow_and_west/8079133.stm
/news/uk-england-coventry-warwickshire-47232767
https://www.bbc.com/news/uk-wales-22819018

/news/uk-wales-47697807
/news/live/uk-england-hampshire-41888664
/news/uk-england-lincolnshire-13199762
/news/uk-england-lincolnshire-14481049
/news/uk-england-humber-25588665
http://news.bbc.co.uk/1/hi/england/sussex/7294499.stm
http://news.bbc.co.uk/1/hi/england/sussex/7514636.stm
/news/uk-scotland-edinburgh-east-fife-31064709
/news/uk-northern-ireland-30505142
/news/uk-northern-ireland-30899735
http://news.bbc.co.uk/2/hi/uk_news/england/3640199.stm
/news/uk-england-south-yorkshire-56539901.amp
/news/uk-england-south-yorkshire-57442903.amp
https://www.bbc.com/news/uk-england-essex-58656979
/programmes/b00z8hwl/episodes/guide
https://www.bbc.com/news/uk-england-london-23137474.amp
/news/uk-england-london-23137474
/news/uk-england-essex-58632294
/news/uk-england-essex-58656979
http://news.bbc.co.uk/2/hi/uk_news/england/london/7814292.stm
https://ichef.bbci.co.uk/news/1024/branded_news/7D22/production/_120643023_hi070761921.jpg
/news/uk-england-essex-58641721
https://www.bbc.com/news/uk-england-essex-58641721
https://www.bbc.com/news/uk-scotland-edinburgh-east-fife-32504804
https://ichef.bbci.co.uk/news/624/mcs/media/images/81804000/jpg/_81804660_waswas.jpg
/news/live/uk-england-kent-45132268/page/2
https://www.bbc.com/news/uk-england-essex-58927034
https://ichef.bbci.co.uk/news/660/cpsprodpb/7D22/production/_120643023_hi070761921.jpg
https://ichef.bbci.co.uk/news/976/cpsprodpb/2D4B/production/_120659511_hi070761921.jpg
/news/uk-northern-ireland-48269441
/news/uk-england-bristol-40113476
/news/uk-england-essex-49757611
/news/uk-wales-south-east-wales-28254024
http://news.bbc.co.uk/welsh/low/newsid_3080000/newsid_3087000/3087069.stm
/news/uk-scotland-edinburgh-east-fife-31992069
/news/uk-scotland-edinburgh-east-fife-32504804
http://news.bbc.co.uk/2/hi/uk_news/england/berkshire/4649948.stm
https://www.bbc.com/news/uk-england-manchester-23534373

August 2023
https://www.bbc.com/news/uk-scotland-south-scotland-30452017
/news/health-51269237.amp
/news/topics/clw2pz3mx17t?page=3
https://www.bbc.com/news/uk-england-lancashire-55171223
/news/uk-england-lancashire-55171223
https://ichef.bbci.co.uk/news/976/mcs/media/images/69086000/jpg/_69086573_kinyeti_x7.jpg
/news/uk-england-manchester-23534373
/news/uk-england-manchester-23534373.amp
https://www.bbc.com/news/uk-england-london-48439863
/news/uk-england-essex-58927034
https://www.bbc.com/news/uk-england-beds-bucks-herts-45144941
/news/uk-england-beds-bucks-herts-45144941
/news/uk-england-beds-bucks-herts-45144941.amp
https://ichef.bbci.co.uk/news/976/cpsprodpb/D521/production/_102916545_bedspolice1.jpg.webp
/programmes/p00fffqk
/programmes/b00z6dw3
https://www.bbc.com/news/uk-northern-ireland-20807843
https://www.bbc.com/news/uk-northern-ireland-57720152
https://ichef.bbci.co.uk/news/1024/branded_news/1747B/production/_119255359_vanishingindex.jpg
https://ichef.bbci.co.uk/news/304/mcs/media/images/65028000/jpg/_65028055_toryman.jpg
https://ichef.bbci.co.uk/news/640/cpsprodpb/E168/production/_119240775_nevillepreshohousefrompier.jpg
https://ichef.bbci.co.uk/news/640/mcs/media/images/65028000/jpg/_65028057_torymanagain.jpg
https://www.bbc.com/news/uk-england-london-13880599
http://news.bbc.co.uk/2/hi/uk_news/england/london/7625127.stm
/news/uk-england-coventry-warwickshire-19354621
https://www.bbc.com/indonesia/berita_indonesia/2010/04/100422_yoyohtrial
https://www.bbc.com/indonesia/berita_indonesia/2010/11/101106_verdictindonesianmaid
/news/uk-scotland-glasgow-west-45483960.amp
/news/live/uk-england-merseyside-33827608
/news/uk-england-36054273
/news/uk-england-merseyside-33992110
/news/uk-england-merseyside-34074294
https://www.bbc.com/news/uk-england-merseyside-34074294
/news/uk-england-london-55355531
/sport/football/60200001
https://www.bbc.com/news/uk-england-coventry-warwickshire-19354621
https://www.bbc.com/news/uk-england-london-48558259
https://www.bbc.com/indonesia/berita_indonesia/2010/04/100422_yoyoh.amp
/news/live/uk-england-sussex-45645720
/news/uk-england-surrey-45764290
http://news.bbc.co.uk/2/hi/uk_news/england/6246595.stm

July 2023

/news/uk-england-london-25320376
https://www.bbc.com/mundo/noticias-42382189
/news/uk-england-stoke-staffordshire-37449283
https://www.bbc.com/news/uk-england-norfolk-20898593
https://www.bbc.com/news/uk-england-norfolk-21005999
https://www.bbc.com/ukchina/simp/48676842
https://ichef.bbci.co.uk/news/640/cpsprodpb/11698/production/_104402317_a7d33515-636e-4dc2-89d5-be97bd3ba0bc.jpg
https://ichef.bbci.co.uk/news/640/cpsprodpb/A550/production/_104402324_e041f539-1010-43c1-9571-7e61c81deeeb.jpg
/news/uk-wales-56581156
/news/uk-wales-north-east-wales-21877747.amp
https://www.bbc.com/news/uk-england-essex-12153788
http://news.bbc.co.uk/2/hi/uk_news/england/6522251.stm
https://www.bbc.com/news/uk-england-sussex-19001100
https://www.bbc.com/news/uk-england-sussex-19050281
https://www.bbc.com/news/uk-england-sussex-19067651
https://ichef.bbci.co.uk/news/304/mcs/media/images/61831000/jpg/_61831180_dacosta.jpg
/news/uk-england-stoke-staffordshire-37449283.amp
/news/uk-scotland-edinburgh-east-fife-60023868
/news/uk-wales-22819018
https://www.bbc.com/news/uk-england-berkshire-41917724.amp
/news/uk-england-berkshire-41917724
https://www.bbc.com/news/uk-england-devon-12194168
/news/uk-england-tyne-44521763
/news/uk-england-essex-12153788

June 2023

/news/uk-scotland-glasgow-west-22399390.amp
https://www.bbc.com/news/uk-scotland-glasgow-west-22399390
https://www.bbc.com/news/uk-scotland-glasgow-west-22399390.amp
/news/uk-england-35574470
https://www.bbc.com/indonesia/berita_indonesia/2010/04/100422_yoyohtrial
https://www.bbc.com/news/uk-northern-ireland-19055332
/news/uk-england-manchester-37612054
https://www.bbc.com/news/uk-england-manchester-30231863
http://news.bbc.co.uk/2/hi/uk_news/wales/mid_/6334815.stm
/news/uk-england-london-65632912
http://news.bbc.co.uk/2/hi/uk_news/northern_ireland/8433951.stm
/news/live/uk-england-leicestershire-43646963
http://news.bbc.co.uk/2/hi/uk_news/4253442.stm
http://news.bbc.co.uk/1/hi/england/london/6293178.stm
http://news.bbc.co.uk/1/hi/england/4319942.stm
/news/uk-northern-ireland-19055332
/news/uk-england-london-53185174?intlink_from_url=&link_location=live-reporting-story
https://ichef.bbci.co.uk/news/976/cpsprodpb/10F77/production/_112359496_mediaitem112359495.jpg.webp
https://ichef.bbci.co.uk/news/976/cpsprodpb/A884/production/_112604134_mediaitem112604133.jpg.webp
https://www.bbc.com/news/uk-england-gloucestershire-58930085
/news/uk-england-tyne-44521763.amp
http://news.bbc.co.uk/1/hi/england/london/7625127.stm
/news/uk-scotland-glasgow-west-24901020.amp
http://news.bbc.co.uk/2/hi/8427790.stm
/news/uk-england-london-52879900
/news/uk-england-london-53185174
https://www.bbc.com/news/uk-england-london-52727025
https://www.bbc.com/news/uk-england-london-53185174
/news/uk-england-hampshire-49824786.amp
http://news.bbc.co.uk/1/hi/england/london/6223992.stm
https://www.bbc.com/news/uk-england-london-48439863.amp
http://news.bbc.co.uk/1/hi/england/merseyside/7960271.stm
http://news.bbc.co.uk/2/hi/uk_news/england/london/4027033.stm
http://news.bbc.co.uk/2/hi/uk_news/7196454.stm
https://ichef.bbci.co.uk/news/304/mcs/media/images/71585000/jpg/_71585550_troll.jpg
/news/uk-scotland-glasgow-west-25267902

May 2023

/news/world-europe-42974298
http://news.bbc.co.uk/1/hi/northern_ireland/8433951.stm
https://ichef.bbci.co.uk/news/464/mcs/media/images/51207000/jpg/_51207520_drugscourierscomposite466by.jpg
/news/uk-england-london-48444823.amp
https://www.bbc.com/portuguese/internacional-43553566
http://news.bbc.co.uk/2/hi/europe/8484890.stm
http://news.bbc.co.uk/2/hi/business/1938820.stm
https://www.bbc.com/news/uk-england-20626475
http://news.bbc.co.uk/1/hi/england/london/4027033.stm
http://news.bbc.co.uk/1/hi/wales/4762707.stm
http://www.bbc.co.uk/news/uk-england-lincolnshire-31848810
http://news.bbc.co.uk/1/hi/england/wear/8355878.stm
http://www.bbc.co.uk/news/world-asia-india-20264241
http://news.bbc.co.uk/1/hi/uk/4938574.stm
http://www.bbc.co.uk/news/uk-england-nottinghamshire-39459045
http://www.bbc.co.uk/manchester/content/articles/2006/12/14/child_blogger_feature.shtml
http://www.bbc.com/news/uk-england-london-22892221
http://news.bbc.co.uk/sport2/hi/football/eng_conf/9675881.stm
http://www.bbc.co.uk/news/mobile/uk-england-gloucestershire-13294692
http://www.bbc.co.uk/news/uk-england-gloucestershire-13294692
http://www.bbc.co.uk/news/uk-england-gloucestershire-13795825
http://news.bbc.co.uk/1/hi/wales/south_east/7098099.stm
http://news.bbc.co.uk/1/hi/scotland/north_east/6906934.stm
http://news.bbc.co.uk/1/hi/scotland/north_east/6913725.stm
http://news.bbc.co.uk/1/hi/scotland/north_east/7226819.stm
http://news.bbc.co.uk/1/hi/scotland/north_east/7228722.stm
http://news.bbc.co.uk/1/hi/scotland/north_east/7322579.stm
http://news.bbc.co.uk/2/hi/entertainment/1107823.stm
http://news.bbc.co.uk/1/hi/england/tees/4007827.stm
http://news.bbc.co.uk/2/hi/uk_news/england/tees/4007827.stm
http://news.bbc.co.uk/2/hi/uk_news/england/tees/6188934.stm
http://www.bbc.com/indonesia/berita_indonesia/2010/04/100422_yoyoh
http://www.bbc.com/news/uk-scotland-north-east-orkney-shetland-10739740
http://www.bbc.co.uk/news/mobile/10435066
http://news.bbc.co.uk/2/hi/uk_news/scotland/highlands_and_islands/8037799.stm
http://news.bbc.co.uk/2/hi/uk_news/scotland/north_east/8479312.stm
http://news.bbc.co.uk/1/hi/scotland/north_east/8037799.stm
http://news.bbc.co.uk/1/hi/scotland/north_east/8479312.stm
http://news.bbc.co.uk/1/hi/uk/622199.stm
http://news.bbc.co.uk/1/hi/uk/619621.stm
http://news.bbc.co.uk/2/hi/uk_news/6644465.stm
http://news.bbc.co.uk/1/hi/wales/north_east/3610885.stm
http://news.bbc.co.uk/1/hi/wales/north_east/3697238.stm
http://news.bbc.co.uk/1/hi/wales/north_east/3701130.stm
http://news.bbc.co.uk/2/hi/uk_news/england/manchester/3172724.stm
http://news.bbc.co.uk/2/hi/uk_news/england/manchester/3175724.stm
http://news.bbc.co.uk/2/hi/uk_news/magazine/8091028.stm
http://news.bbc.co.uk/1/hi/england/manchester/7109168.stm
http://news.bbc.co.uk/1/hi/england/southern_counties/4209030.stm
http://www.bbc.co.uk/news/uk-northern-ireland-13856865
http://news.bbc.co.uk/2/hi/uk_news/england/merseyside/4986438.stm
http://news.bbc.co.uk/2/hi/uk_news/england/merseyside/6199819.stm
http://news.bbc.co.uk/2/hi/uk_news/england/merseyside/6236550.stm
http://www.bbc.co.uk/news/mobile/business-16509679
http://news.bbc.co.uk/1/hi/uk/273824.stm
http://www.bbc.co.uk/news/uk-scotland-north-east-orkney-shetland-12129231
http://www.bbc.co.uk/news/uk-scotland-north-east-orkney-shetland-12354790
http://www.bbc.com/news/uk-scotland-tayside-central-12577581
http://www.bbc.com/news/uk-england-lancashire-22570334
https://www.bbc.com/mundo/lg/participe/2009/09/090909_entrevista_interactiva_forlan_rg.shtml
http://www.bbc.com/mundo/participe/2009/09/090909_entrevista_interactiva_forlan_rg.shtml
http://news.bbc.co.uk/1/hi/uk_politics/6252007.stm
http://news.bbc.co.uk/2/hi/business/708271.stm
http://news.bbc.co.uk/1/hi/sci/tech/7385615.stm
http://news.bbc.co.uk/1/hi/england/merseyside/6199819.stm
http://news.bbc.co.uk/1/hi/uk/7196454.stm
http://news.bbc.co.uk/1/hi/uk/7634313.stm
http://news.bbc.co.uk/2/hi/uk_news/7047931.stm
http://news.bbc.co.uk/1/hi/uk/7047931.stm
http://www.bbc.com/news/av/uk-england-london-29167444/award-winning-george-eliot-primary-school-investigated
http://www.bbc.com/news/av/uk-england-london-29167444/award-winning-george-eliot-primary-school-investigated
http://www.bbc.co.uk/news/av/uk-england-london-29167444/award-winning-george-eliot-primary-school-investigated
http://news.bbc.co.uk/1/shared/spl/hi/pop_ups/04/uk_do_you_feel_safe_on_the_tube0/html/1.stm
http://news.bbc.co.uk/1/hi/uk/817015.stm
http://www.bbc.co.uk/news/uk-northern-ireland-28270216
http://www.bbc.co.uk/news/uk-northern-ireland-28482986
http://www.bbc.co.uk/news/uk-scotland-south-scotland-33677754
http://www.bbc.co.uk/news/uk-scotland-south-scotland-33725385
http://www.bbc.co.uk/news/uk-england-10839121
http://www.bbc.co.uk/news/uk-england-10840334
http://news.bbc.co.uk/2/hi/uk_news/3206355.stm
http://www.bbc.com/news/uk-england-tees-32759584
http://news.bbc.co.uk/1/hi/northern_ireland/4465109.stm
http://news.bbc.co.uk/2/hi/uk_news/northern_ireland/4465109.stm
http://news.bbc.co.uk/1/hi/scotland/north_east/8251042.stm
http://news.bbc.co.uk/1/hi/england/devon/6741159.stm
http://news.bbc.co.uk/1/hi/england/devon/6753933.stm
http://www.bbc.co.uk/news/10230780
http://news.bbc.co.uk/1/hi/england/cambridgeshire/8531030.stm
http://news.bbc.co.uk/2/hi/talking_point/1948438.stm
http://news.bbc.co.uk/1/hi/world/europe/jersey/4753921.stm
http://news.bbc.co.uk/1/hi/scotland/edinburgh_and_east/7398426.stm
http://news.bbc.co.uk/1/hi/scotland/2339803.stm
http://news.bbc.co.uk/1/hi/health/2976592.stm
http://news.bbc.co.uk/1/hi/programmes/panorama/3005483.stm
http://news.bbc.co.uk/2/hi/programmes/panorama/3008433.stm
http://www.bbc.com/news/uk-england-coventry-warwickshire-27346990
http://www.bbc.co.uk/news/world-europe-guernsey-17287180
http://news.bbc.co.uk/1/mobile/england/devon/7575533.stm
http://www.bbc.co.uk/news/uk-england-northamptonshire-10854820
http://www.bbc.co.uk/news/uk-england-london-12236887
http://www.bbc.co.uk/news/uk-england-london-13962703
https://www.bbc.com/mundo/noticias/2014/05/140523_espana_tuiteros_indeseables_jgc
https://www.bbc.com/news/uk-england-surrey-11702376
http://www.bbc.co.uk/news/uk-england-manchester-16709925
http://www.bbc.co.uk/news/uk-england-manchester-19050911
http://news.bbc.co.uk/1/hi/england/5278210.stm
http://www.bbc.com/news/uk-england-cambridgeshire-26821303
http://www.bbc.co.uk/news/uk-england-cambridgeshire-27315548
http://news.bbc.co.uk/1/hi/scotland/4903556.stm
http://news.bbc.co.uk/2/hi/uk_news/scotland/4903556.stm
http://news.bbc.co.uk/2/hi/uk_news/england/norfolk/6731515.stm
http://www.bbc.co.uk/programmes/b00nj737
http://www.bbc.co.uk/news/uk-northern-ireland-22477166
http://www.bbc.co.uk/news/uk-northern-ireland-28991271
http://www.bbc.com/news/uk-northern-ireland-22084732
http://news.bbc.co.uk/1/hi/england/2246888.stm
http://news.bbc.co.uk/1/hi/england/berkshire/4649948.stm
https://www.bbc.com/news/uk-northern-ireland-35135027.amp
http://www.bbc.co.uk/news/uk-england-22050049
https://www.bbc.com/news/technology-38315793
http://news.bbc.co.uk/1/hi/uk/7047931.stm
http://news.bbc.co.uk/1/hi/uk/7634313.stm
http://news.bbc.co.uk/1/hi/uk/5283630.stm
http://www.bbc.co.uk/news/uk-england-northamptonshire-34933345
http://www.bbc.co.uk/news/uk-england-northamptonshire-34933347
http://www.bbc.co.uk/news/uk-england-northamptonshire-35744590
http://www.bbc.co.uk/news/uk-england-northamptonshire-37288206
http://www.bbc.co.uk/news/av/uk-england-northamptonshire-34933347/dashcam-captures-lorry-shunting-car-on-m1
http://news.bbc.co.uk/2/hi/uk_news/8625446.stm
http://news.bbc.co.uk/1/shared/spl/hi/pop_ups/08/uk_politics_the_hutton_inquiry_queue/html/2.stm
http://www.bbc.com/mundo/noticias-38468488
http://www.bbc.com/news/world-latin-america-38328490
http://www.bbc.com/news/uk-scotland-tayside-central-11391906
https://www.bbc.com/news/uk-politics-eu-referendum-35799469
/news/uk-england-london-46099553
/news/uk-england-london-47201012
/news/uk-england-london-48439863
https://www.bbc.com/news/uk-england-cambridgeshire-21433429
https://www.bbc.com/news/uk-england-hampshire-19886569
/news/uk-england-sussex-19050281
/news/uk-england-sussex-19164904
https://www.bbc.com/igbo/afirika-53256430
/news/uk-england-birmingham-48269501
https://www.bbc.com/news/uk-scotland-edinburgh-east-fife-38750125
https://www.bbc.com/news/uk-scotland-edinburgh-east-fife-39042586
/news/uk-england-london-51756194
/news/uk-england-london-54384692
/news/uk-england-coventry-warwickshire-38501003.amp
http://news.bbc.co.uk/2/hi/uk_news/england/somerset/4745180.stm
/news/uk-england-sussex-19001100
https://www.bbc.com/news/uk-scotland-north-east-orkney-shetland-43114674

April 2023

https://www.bbc.com/news/world-europe-18179818
https://www.bbc.com/news/uk-england-birmingham-46266120
/news/uk-england-london-64942934.amp
http://news.bbc.co.uk/1/hi/scotland/glasgow_and_west/7869695.stm
http://news.bbc.co.uk/1/hi/scotland/glasgow_and_west/7988085.stm
http://news.bbc.co.uk/2/hi/uk_news/scotland/glasgow_and_west/8033517.stm
http://news.bbc.co.uk/2/hi/uk_news/scotland/glasgow_and_west/8112798.stm
http://news.bbc.co.uk/1/hi/england/somerset/4745180.stm
http://news.bbc.co.uk/1/hi/scotland/glasgow_and_west/8033517.stm
https://www.bbc.com/news/live/uk-england-tyne-56295615/page/27
https://www.bbc.com/news/live/uk-england-tyne-56295615/page/28
/news/live/uk-england-tyne-55102691/page/25
/news/live/uk-england-tyne-55276229/page/28
/news/live/uk-england-tyne-56536403/page/28
/news/uk-northern-ireland-20807843
/news/uk-wales-48749328
https://www.bbc.com/news/uk-scotland-glasgow-west-40050834
https://www.bbc.com/news/uk-41697913
/news/uk-england-gloucestershire-58930085
https://www.bbc.com/news/business-25349240
/news/uk-england-manchester-17853559.amp
/news/uk-northern-ireland-57720152
/news/special/2015/newsspec_10259/content/english/convicted.html?v=7.0.32
https://ichef.bbci.co.uk/news/976/cpsprodpb/5C48/production/_85942632_tokyoyork.jpg
https://www.bbc.com/news/uk-england-gloucestershire-30178386
https://ichef.bbci.co.uk/news/400/mcs/media/images/79230000/jpg/_79230140_rodley.jpg
/news/technology-37385555
/news/uk-england-coventry-warwickshire-23544913
https://www.bbc.com/news/uk-england-merseyside-30493708.amp
/news/technology-38879969
http://news.bbc.co.uk/2/hi/uk_news/england/staffordshire/3945089.stm
/news/uk-england-merseyside-33721010
/news/uk-england-40412399
/news/uk-wales-south-east-wales-15160873
https://www.bbc.com/news/uk-england-31642075
https://www.bbc.com/news/uk-england-lincolnshire-34285598.amp
http://news.bbc.co.uk/2/hi/uk_news/england/lancashire/8438561.stm
/news/10371624.amp
/news/uk-england-36393977
/news/uk-england-birmingham-53361549
https://www.bbc.com/news/uk-england-birmingham-48131922
https://ichef.bbci.co.uk/news/976/cpsprodpb/86D5/production/_106771543_may2-mir1.jpg
https://ichef.bbci.co.uk/news/976/cpsprodpb/D4F5/production/_106771545_may2-mir2.jpg
https://www.bbc.com/cymrufyw/36596472
https://ichef.bbci.co.uk/news/976/cpsprodpb/4A29/production/_90058981_hunlunplismon.jpg
https://ichef.bbci.co.uk/news/976/cpsprodpb/4A29/production/_90058981_hunlunplismon.jpg.webp
/romanian/news/story/2007/09/printable/070909_romania_sua_extradare.shtml
/news/uk-england-birmingham-46280539
https://www.bbc.com/news/uk-england-beds-bucks-herts-36201713.amp
http://news.bbc.co.uk/1/hi/scotland/glasgow_and_west/5181326.stm
/news/uk-england-gloucestershire-58876169
/news/uk-england-birmingham-46266120
/news/uk-england-birmingham-46280539
/news/uk-scotland-edinburgh-east-fife-31064709.amp
https://www.bbc.com/news/uk-england-cornwall-20516042
/news/uk-scotland-glasgow-west-22399390

March 2023

/news/uk-england-birmingham-48131922
https://www.bbc.com/news/uk-england-birmingham-48113851
/news/topics/cdnpj59gj1nt?page=5
https://www.bbc.com/news/uk-politics-52553229
http://news.bbc.co.uk/1/hi/england/london/7546810.stm
https://www.bbc.com/news/uk-northern-ireland-35555465
https://ichef.bbci.co.uk/news/976/cpsprodpb/1A5B/production/_87774760_orlao'hanlonon.jpg
http://news.bbc.co.uk/2/hi/uk_news/england/london/3569357.stm
https://www.bbc.com/news/uk-england-gloucestershire-30178386.amp
https://www.bbc.com/news/uk-england-london-43808943
https://www.bbc.com/news/uk-england-london-43928158
https://www.bbc.com/news/uk-england-london-43967366
https://www.bbc.com/news/uk-northern-ireland-35555465.amp
https://www.bbc.com/news/uk-scotland-glasgow-west-39220213
https://ichef.bbci.co.uk/news/1024/branded_news/1575E/production/_89120978_89120976.jpg
/cymrufyw/36596472
https://www.bbc.com/turkce/haberler/2014/03/140308_rengin_8mart
/news/uk-england-hampshire-24840376.amp
http://news.bbc.co.uk/1/hi/magazine/8285370.stm
http://news.bbc.co.uk/1/hi/england/4683863.stm
http://news.bbc.co.uk/1/hi/scotland/north_east/6214567.stm
http://news.bbc.co.uk/2/hi/uk_news/scotland/north_east/6216755.stm
http://news.bbc.co.uk/1/hi/scotland/north_east/6162327.stm
http://news.bbc.co.uk/1/hi/scotland/north_east/6216755.stm
http://news.bbc.co.uk/1/hi/scotland/north_east/6291899.stm
http://news.bbc.co.uk/1/hi/scotland/north_east/7085223.stm
http://news.bbc.co.uk/2/hi/uk_news/scotland/north_east/6214567.stm
http://news.bbc.co.uk/2/hi/uk_news/scotland/north_east/6291899.stm
http://news.bbc.co.uk/2/hi/uk_news/scotland/north_east/7085223.stm
/news/uk-england-beds-bucks-herts-36201713
/news/uk-england-kent-23574942
/news/newsbeat-11064589.amp
https://www.bbc.com/news/uk-scotland-tayside-central-35998732.amp
https://www.bbc.com/news/uk-england-nottinghamshire-37990652.amp
/news/uk-england-hampshire-22765041
/news/uk-england-cornwall-20516042
/news/uk-england-stoke-staffordshire-59312771
http://news.bbc.co.uk/1/hi/england/staffordshire/3945089.stm
http://news.bbc.co.uk/1/hi/scotland/1621052.stm
http://news.bbc.co.uk/1/hi/scotland/640499.stm
http://news.bbc.co.uk/1/hi/scotland/643873.stm
http://news.bbc.co.uk/1/hi/scotland/669546.stm
http://news.bbc.co.uk/olmedia/1620000/images/_1621793_fionacameron300.jpg
http://news.bbc.co.uk/olmedia/455000/images/_459190_sash150.jpg
http://news.bbc.co.uk/olmedia/640000/images/_643873_fionacameron150.jpg
http://news.bbc.co.uk/olmedia/640000/images/_643873_robertcameron150.jpg
http://news.bbc.co.uk/olmedia/640000/images/_643873_yellowribbon300.jpg
http://news.bbc.co.uk/olmedia/665000/images/_669989_balloons300.jpg
http://news.bbc.co.uk/olmedia/690000/images/_694696_sashacameron150.jpg
http://news.bbc.co.uk/olmedia/690000/images/_694696_sashacameronposter300.jpg
http://news.bbc.co.uk/olmedia/695000/images/_696504_sashacameronposter300.jpg
http://news.bbc.co.uk/2/hi/uk_news/scotland/north_east/7085223.stm
/news/uk-scotland-glasgow-west-35254521
https://www.bbc.com/news/uk-england-manchester-12541987
https://www.bbc.com/news/av/uk-31931370

]]>
0
The future of searching the past: Transitioning from Ö÷²¥´óÐã Redux to Archive Search Thu, 26 May 2022 12:05:14 +0000 /blogs/internet/entries/491df53c-c2ab-42b5-abed-b02dc40e9442 /blogs/internet/entries/491df53c-c2ab-42b5-abed-b02dc40e9442 Mary McCarthy Mary McCarthy

If you're relatively new to the Ö÷²¥´óÐã, you may not have heard of Ö÷²¥´óÐã Redux. However, for those of us who have been around for a while, Redux is legendary. The brainchild of Ö÷²¥´óÐã Research & Development's Chief Scientist, Brandon Butterworth, Redux recorded and stored all programmes broadcast on our national TV channels and radio stations since 2007. These programmes could be found and played back via the Redux website.

Archive Search is now the place to go to find archive content. From next week Archive Search will no longer use Redux to source content. More on that later.

Uses of Ö÷²¥´óÐã Redux

In 2007 it was difficult to get hold of audio and video content from the Ö÷²¥´óÐã archive in a digital format. Accessing archive content for research generally meant ordering and waiting for VHS tapes or DVDs to be delivered by a Ö÷²¥´óÐã mail van. Ö÷²¥´óÐã Redux allowed programme-makers to view a growing set of content immediately. It proved extremely popular.

Ö÷²¥´óÐã Research & Development also built Snippets - a hugely popular tool with programme-makers - which relied on the content held by Ö÷²¥´óÐã Redux. Snippets used the programme subtitles to allow users to search across the spoken word of the programme. Want a clip of Delboy saying, "This time next year, we'll be millionaires"? You got it!

"Ö÷²¥´óÐã REDUX has been an invaluable tool, quite revolutionary in its simplicity and comprehensiveness. I really appreciated how the system captured everything, especially the complete coverage of the Ö÷²¥´óÐã News Channel output – this has proved invaluable over the years, especially with the current fashion for using audio of news journalists to carry the narrative of many documentaries. The addition of searchable subtitles via Snippets was another great innovation that made it so much easier to interrogate the huge amount of material in the collection. The innovative and imaginative work of the Ö÷²¥´óÐã R&D team and their willingness to push forward and make REDUX and SNIPPETS available to all Ö÷²¥´óÐã employees is greatly appreciated, and I hope the spirit of that approach will continue to live on in R&D and elsewhere, even as REDUX itself comes to an end."

Stuart Robertson, Archive and Digital Lead, Current Affairs

Over the years, Ö÷²¥´óÐã Redux has met many and varying needs, including:

  • programme research - researching a person or topic as well as finding content suitable to re-use in a new programme
  • compliance - reviewing programmes in the event of a query or complaint
  • technical review - helping ensure that Ö÷²¥´óÐã broadcasts achieve the expected quality
  • content delivery in the required format for iPlayer Beta sites, e.g. Nintendo Wii
  • external online access to content - increasingly important as more of our content is made by independent production companies
  • education partnerships - enables schools, colleges and universities to make educational use of TV and Radio broadcasts as permitted by copyright law
  • research projects including academic partnerships, particularly in the field of machine learning

Why are we moving away from Ö÷²¥´óÐã Redux?

Since Ö÷²¥´óÐã Redux began, access to our archive has changed enormously. A large and ever-increasing proportion of our 100 years of archive is now digitised and available in broadcast quality to programme-makers inside and outside the Ö÷²¥´óÐã. This includes higher-quality copies of much of the content stored in Ö÷²¥´óÐã Redux. Since 2017 all pre-recorded programmes have been delivered for broadcast as digital files and automatically archived. Physical archive loans ceased in February 2021.

We now have  - a single place to search across approximately 75% of our archive. It will cover even more of the archive in future.

What will I do without Ö÷²¥´óÐã Redux?

The unique content recorded by Redux will continue to be available to play and clip in browse quality via Archive Search. New content will be available via Archive Search - just not recorded off-air by Redux.

Archive Search allows users to explore the spoken content of programmes using subtitles and machine-generated transcripts. Users can make clips of relevant parts of a programme, and for some content, they can even make broadcast-quality clips ready for inclusion in a new programme.

Our curators routinely update archive collections to support production teams, particularly in advance of upcoming events, anniversaries and seasons. These collections are shared on the Archive Search homepage.

Archive Search has allowed us to expand archives access for universities and schools. The entire digitised Ö÷²¥´óÐã broadcast archive is now available to students in formal education in the UK.

Ö÷²¥´óÐã staff can find training and information on accessing Archive Search by searching on Gateway. If you are working on a Ö÷²¥´óÐã commission at an independent production company that would benefit from archive access, your Ö÷²¥´óÐã contact can provide this information.

What next for Ö÷²¥´óÐã Archives access?

We will soon make Radio Digital Archive content available via Archive Search, giving access to an extensive archive of high-quality audio. We will also provide more programme information within Archive Search to help programme-makers make more informed choices and make re-use easier.

This year we celebrate the Ö÷²¥´óÐã's centenary. The Archives Technology & Services team look forward to seeing archive content play a key role in our celebration of and reflection on the Ö÷²¥´óÐã's first century.

]]>
0
Ö÷²¥´óÐã pages removed from Google search results: 2022 Sat, 01 Jan 2022 12:00:00 +0000 /blogs/internet/entries/6536da29-fc61-417a-ae1e-184b1a3705ef /blogs/internet/entries/6536da29-fc61-417a-ae1e-184b1a3705ef Clare Hudson Clare Hudson

In 2014 the that individuals can ask search engines to remove certain web pages from their results. Those pages usually contain personal information.

Google subsequently removed links from specific searches and continues to delist pages for some results. This includes some Ö÷²¥´óÐã pages. These pages are not removed from the Google index entirely, nor from Ö÷²¥´óÐã Online. The latest removals are listed below.

Read more on the Ö÷²¥´óÐã's archive policies and find lists of earlier removals.

One important caveat when looking through this list: we are not told who has requested the delisting. We should not leap to conclusions as to who is responsible. The request may not be from the apparent subject of a story.

September 2022

/programmes/p00l9dqf
/news/uk-england-tyne-56773168?at_custom4=F9530CEE-9EB8-11EB-ACC4-A0584D484DA4&at_custom1=link&at_campaign=64&at_medium=custom7&at_custom3=Regional+Ö÷²¥´óÐã+North+East+and+Cumbria&at_custom2=twitter
/news/live/uk-england-bristol-43277252/page/11
https://www.bbc.com/news/uk-scotland-highlands-islands-35530739
/news/uk-scotland-edinburgh-east-fife-29899602.amp
https://www.bbc.com/news/uk-scotland-highlands-islands-36711585
/news/uk-scotland-highlands-islands-35530739
http://news.bbc.co.uk/1/hi/england/southern_counties/6183823.stm
/news/uk-northern-ireland-43519611
https://www.bbc.com/news/uk-scotland-tayside-central-36652208
https://www.bbc.com/news/uk-england-essex-49209661
https://www.bbc.com/news/uk-28809134
https://www.bbc.com/news/uk-england-nottinghamshire-24061550
https://ichef.bbci.co.uk/news/224/mcs/media/images/69813000/jpg/_69813558_abdulchoudhuri.jpg
/news/uk-england-essex-39145271.amp
/news/uk-11359512
/news/uk-england-nottinghamshire-24061550
http://www.bbc.co.uk/news/topics/cxw7q5zm562t?page=29
https://www.bbc.com/news/topics/cxw7q5zm562t?page=29
https://ichef.bbci.co.uk/live-experience/cps/480/cpsprodpb/104E9/production/_101239766_christopherhenry.jpg

August 2022

/news/uk-england-south-yorkshire-49254431
/news/uk-england-south-yorkshire-49270570 http://news.bbc.co.uk/1/hi/magazine/3896213.stm /news/uk-england-norfolk-60706535 https://ichef.bbci.co.uk/news/640/cpsprodpb/12560/production/_123640157_5717d15d-8927-4c45-a016-67786bbf121c.jpg /birmingham/content/articles/2005/04/25/student_voters_feature.shtml http://news.bbc.co.uk/2/hi/uk_news/england/dorset/7837691.stm /news/uk-england-oxfordshire-11184865.amp /news/uk-england-35161550 /news/uk-england-suffolk-29723777.amp https://www.bbc.com/news/uk-england-oxfordshire-10924071 /news/uk-england-nottinghamshire-38413347 http://news.bbc.co.uk/2/hi/uk_news/england/cambridgeshire/8376918.stm https://www.bbc.com/news/uk-england-hampshire-44058417 /news/uk-41697913.amp /news/topics/cdnpj59gj1nt?page=4 /news/uk-england-berkshire-24173948 http://news.bbc.co.uk/2/hi/uk_news/england/leicestershire/3681580.stm /news/uk-england-birmingham-46536422.amp https://www.bbc.com/news/world-middle-east-23508749 /news/mobile/uk-england-sussex-11493124 https://www.bbc.com/news/uk-england-sussex-10779211 /search?q=farhad+tailor+leicestershire&page=1 http://news.bbc.co.uk/1/hi/england/leicestershire/3681580.stm http://news.bbc.co.uk/2/hi/uk_news/england/6666691.stm http://news.bbc.co.uk/2/hi/uk_news/northern_ireland/6228885.stm /news/uk-england-11479831

July 2022

/news/uk-england-hampshire-44058417
/news/uk-17731143
/news/uk-england-london-43127415
/news/uk-england-berkshire-59871751
/news/uk-england-berkshire-59896099
/news/uk-england-berkshire-60001525
https://www.bbc.com/news/av/uk-england-bristol-30182647
https://ichef.bbci.co.uk/news/1024/cpsprodpb/12EFE/production/_88766577_jamie_cox.jpg
https://ichef.bbci.co.uk/news/208/cpsprodpb/12EFE/production/_88766577_jamie_cox.jpg
https://ichef.bbci.co.uk/news/208/cpsprodpb/1523A/production/_87668568_jamie_cox.jpg
https://ichef.bbci.co.uk/news/560/cpsprodpb/12EFE/production/_88766577_jamie_cox.jpg
https://ichef.bbci.co.uk/news/660/cpsprodpb/12EFE/production/_88766577_jamie_cox.jpg
/news/uk-england-tees-27949058
/news/uk-england-merseyside-29208419
/news/uk-england-nottinghamshire-22901226.amp
/news/live/world-europe-jersey-39081285
/news/uk-scotland-glasgow-west-37159021
http://news.bbc.co.uk/2/hi/uk_news/england/manchester/5299758.stm
https://www.bbc.com/news/uk-scotland-glasgow-west-21033906.amp
https://www.bbc.com/news/uk-wales-42181453
/news/uk-england-tees-40125272
http://news.bbc.co.uk/2/hi/uk_news/england/kent/4014681.stm
/news/uk-wales-north-west-wales-21830227

June 2022

https://www.bbc.com/news/uk-scotland-50669012
https://www.bbc.com/news/uk-scotland-50669012.amp
/news/uk-england-cornwall-43056764
http://news.bbc.co.uk/2/hi/uk_news/england/southern_counties/3901899.stm
https://ichef.bbci.co.uk/news/640/cpsprodpb/0911/production/_110012320_mediaitem110012319.jpg
/news/uk-19409774
/news/uk-28809134
http://news.bbc.co.uk/1/hi/england/kent/3776543.stm
http://news.bbc.co.uk/1/hi/england/kent/4014681.stm
/news/uk-england-shropshire-41128838
https://ichef.bbci.co.uk/news/976/cpsprodpb/37AA/production/_96205241_comedine.jpg
/news/uk-england-stoke-staffordshire-59739404
/news/mobile/uk-scotland-glasgow-west-15377454
/news/uk-scotland-glasgow-west-15377454
/news/av/uk-33641034/anzac-day-terror-plot-blackburn-teenager-admits-terror-charge
/news/av/uk-34426846/blackburn-boy-used-smartphone-to-plan-anzac-terror-plot
/news/av/world-australia-33648097/nurse-s-return-to-australia-provides-first-test-for-terror-laws
/news/av/world-australia-35058732/teenager-and-man-arrested-in-sydney-over-terror-plans
/news/av/world-australia-35058734/sydney-terror-arrests-disturbing-to-see-teenage-children
/news/av/world-australia-40960013/far-right-senator-wears-burka-in-australian-parliament
https://ichef.bbci.co.uk/news/1024/branded_news/95D9/production/_97416383_p05clffn.jpg
https://ichef.bbci.co.uk/news/200/cpsprodpb/06B4/production/_85861710_85861708.jpg
https://ichef.bbci.co.uk/news/200/cpsprodpb/BAF1/production/_85875874_85875872.jpg
https://ichef.bbci.co.uk/news/200/media/images/80925000/jpg/_80925135_80925133.jpg
https://ichef.bbci.co.uk/news/200/media/images/82527000/jpg/_82527292_82527290.jpg
https://ichef.bbci.co.uk/news/270/cpsprodpb/155C/production/_86086450_86083759.jpg
https://ichef.bbci.co.uk/news/270/cpsprodpb/5D9A/production/_103626932_gettyimages-480035137.jpg
https://ichef.bbci.co.uk/news/270/cpsprodpb/990A/production/_103687193_a1.jpg
https://ichef.bbci.co.uk/news/640/cpsprodpb/12ED3/production/_87132577_87132576.jpg
https://ichef.bbci.co.uk/news/640/cpsprodpb/164BE/production/_84462319_015348540-1.jpg
https://ichef.bbci.co.uk/news/640/cpsprodpb/3FF9/production/_85877361_85877360.jpg
https://ichef.bbci.co.uk/news/640/cpsprodpb/8D1B/production/_87132163_87132162.jpg
https://ichef.bbci.co.uk/news/640/cpsprodpb/B5E4/production/_84446564_67276203-c123-478b-b832-7c4e943e22b8.jpg
https://www.bbc.com/news/av/uk-34426846/blackburn-boy-used-smartphone-to-plan-anzac-terror-plot
http://news.bbc.co.uk/1/hi/england/7839316.stm
/news/10369468
http://news.bbc.co.uk/2/hi/uk_news/wales/4526206.stm
/news/uk-england-london-38382128
/news/uk-england-london-41311807
https://www.bbc.com/news/uk-england-london-41161124
https://www.bbc.com/news/uk-england-london-41403296
http://news.bbc.co.uk/1/hi/wales/4526206.stm
https://www.bbc.com/news/health-11425435
http://news.bbc.co.uk/1/hi/england/6522251.stm
http://news.bbc.co.uk/1/hi/england/6666691.stm
/news/uk-northern-ireland-42272543
/news/uk-northern-ireland-43308664
https://www.bbc.com/news/uk-scotland-north-east-orkney-shetland-26739304.amp
https://www.bbc.com/news/uk-england-london-51204156
https://www.bbc.com/news/uk-scotland-glasgow-west-13861199
http://www.bbc.co.uk/news/mobile/uk-scotland-14857004
/pressoffice/pressreleases/stories/2010/09_september/28/apprentice3.shtml
/programmes/p00b8p2f
https://www.bbc.com/news/uk-41697913.amp
/news/uk-wales-16877006
/news/uk-wales-17677963
https://www.bbc.com/news/topics/c1xp19421ezt?page=14
/news/av/uk-2956080002
https://ichef.bbci.co.uk/live-experience/cps/480/cpsprodpb/129C5/production/_92592267_wns_211116_payday_loan_hacker_07.jpg
https://www.bbc.com/news/uk-england-kent-12224383
https://www.bbc.com/news/uk-england-kent-18287401
/news/uk-england-kent-18287401

May 2022

/news/uk-england-manchester-22600666
https://www.bbc.com/news/uk-england-birmingham-28289734.amp
https://www.bbc.com/news/uk-england-birmingham-27148367.amp
http://news.bbc.co.uk/2/hi/uk_news/scotland/glasgow_and_west/5165198.stm
http://news.bbc.co.uk/2/hi/uk_news/scotland/glasgow_and_west/5168912.stm
http://news.bbc.co.uk/2/hi/uk_news/scotland/glasgow_and_west/5191056.stm
http://news.bbc.co.uk/2/hi/uk_news/scotland/glasgow_and_west/5221032.stm
https://www.bbc.com/news/uk-scotland-glasgow-west-11644133
https://www.bbc.com/news/uk-scotland-glasgow-west-12008516
https://www.bbc.com/news/uk-scotland-glasgow-west-12059037
/news/uk-england-birmingham-27148367
/news/mobile/uk-scotland-glasgow-west-11644133
/news/uk-scotland-north-east-orkney-shetland-26739304.amp
http://news.bbc.co.uk/2/hi/health/8031921.stm
https://www.bbc.com/news/av/uk-23502792
http://news.bbc.co.uk/1/hi/wales/1773633.stm
/news/uk-england-birmingham-28289734.amp
https://www.bbc.com/news/uk-england-oxfordshire-50854629
https://www.bbc.com/news/uk-43331950
http://news.bbc.co.uk/1/hi/wales/4465622.stm
/news/uk-england-london-51204156
https://www.bbc.com/news/newsbeat-41807948
https://www.bbc.com/news/uk-england-manchester-12776109.amp
https://www.bbc.com/news/uk-england-lancashire-25887399
http://news.bbc.co.uk/1/hi/scotland/highlands_and_islands/7671861.stm
http://news.bbc.co.uk/1/hi/scotland/highlands_and_islands/7818119.stm
https://ichef.bbci.co.uk/news/1024/branded_news/EAAA/production/_93147006_p444-16gayther.jpg
http://news.bbc.co.uk/1/hi/wales/436234.stm
http://news.bbc.co.uk/1/hi/england/london/4701310.stm
http://news.bbc.co.uk/1/hi/england/london/4778113.stm
http://news.bbc.co.uk/1/hi/england/london/5181706.stm
http://news.bbc.co.uk/2/hi/uk_news/england/london/4701310.stm
http://news.bbc.co.uk/2/hi/uk_news/england/london/4778113.stm
http://news.bbc.co.uk/2/hi/uk_news/england/london/5181706.stm
https://www.bbc.com/news/uk-england-london-38442959
/news/uk-england-london-36402543
/news/live/uk-england-beds-bucks-herts-36164249
http://news.bbc.co.uk/1/hi/england/london/4339756.stm
/news/uk-43331950
http://news.bbc.co.uk/2/hi/americas/7110499.stm
https://www.bbc.com/news/uk-england-sussex-11493124
/news/uk-england-lancashire-25887399
/news/newsbeat-41807948
/sport/horse-racing/21085684
https://www.bbc.com/news/world-europe-23094320
https://www.bbc.com/news/world-europe-23138680
/news/uk-england-merseyside-31509727
https://www.bbc.com/news/uk-scotland-14464323
https://www.bbc.com/news/uk-scotland-14857004
http://news.bbc.co.uk/2/hi/uk_news/england/4277913.stm
https://www.bbc.com/news/uk-england-hampshire-18110688.amp
https://www.bbc.com/news/uk-england-stoke-staffordshire-29761637
https://www.bbc.com/news/newsbeat-12306735
https://www.bbc.com/news/uk-england-devon-11951297
http://news.bbc.co.uk/2/hi/uk_news/wales/4249354.stm
http://news.bbc.co.uk/1/hi/wales/4249354.stm
http://news.bbc.co.uk/1/hi/wales/4249354.stm

April 2022

http://news.bbc.co.uk/1/hi/wales/4249354.stm
/news/uk-scotland-glasgow-west-21859536
/caribbean/news/story/2006/01/060117_arubaholloway.shtml
/staticarchive/77e429a1e8e6fb216a96955ae20910519712e89a.jpg
/news/uk-scotland-tayside-central-36652208
http://news.bbc.co.uk/2/hi/uk_news/scotland/glasgow_and_west/7946620.stm
https://www.bbc.com/news/uk-scotland-tayside-central-35998732
https://www.bbc.com/news/uk-england-beds-bucks-herts-46986199
/news/live/uk-england-sussex-40523247/page/2
/news/10458875
/news/uk-england-sussex-11493124
/news/uk-england-beds-bucks-herts-46986199
/news/uk-scotland-tayside-central-35998732
/news/uk-northern-ireland-19601443.amp
https://www.bbc.com/news/uk-scotland-south-scotland-31622100
/news/av/uk-england-oxfordshire-22375046
/news/uk-england-oxfordshire-22365998
/news/uk-england-oxfordshire-24381219
http://news.bbc.co.uk/2/hi/uk_news/northern_ireland/3185653.stm
/news/live/uk-england-38937988
/news/live/uk-england-northamptonshire-34076313
/news/10458875.amp
https://www.bbc.com/news/uk-wales-48749328.amp
http://news.bbc.co.uk/2/hi/uk_news/england/southern_counties/4793034.stm
http://news.bbc.co.uk/1/hi/scotland/north_east/8113470.stm
http://news.bbc.co.uk/1/hi/scotland/north_east/8151367.stm
/programmes/p01s4xnd https://ichef.bbci.co.uk/images/ic/640x360/p01s4xm5.jpg
/news/uk-england-hampshire-31767113
/news/uk-scotland-edinburgh-east-fife-13602076
/news/uk-scotland-edinburgh-east-fife-14274596
https://ichef.bbci.co.uk/news/464/mcs/media/images/80735000/jpg/_80735183_80735178.jpg
http://news.bbc.co.uk/2/hi/uk_news/england/7595846.stm http://news.bbc.co.uk/2/hi/asia-pacific/3944355.stm https://www.bbc.com/news/uk-england-cumbria-11474494
https://www.bbc.com/news/uk-england-cumbria-11474494.amp

March 2022

http://news.bbc.co.uk/2/hi/uk_news/england/london/3158649.stm

http://www.bbc.co.uk/sport/0/horse-racing/21195955

/sport/horse-racing/19830682

/sport/horse-racing/20993671

/sport/horse-racing/21195955

/news/uk-scotland-edinburgh-east-fife-27941589

/news/uk-scotland-edinburgh-east-fife-27941589.amp

/news/uk-scotland-50669012

https://ichef.bbci.co.uk/news/976/cpsprodpb/0911/production/_110012320_mediaitem110012319.jpg

/news/live/uk-england-northamptonshire-38937991

/news/mobile/uk-england-cumbria-14401033

http://news.bbc.co.uk/1/hi/england/beds/bucks/herts/7410406.stm

https://www.bbc.com/news/10488360

https://www.bbc.com/news/uk-england-cumbria-14401033

http://news.bbc.co.uk/1/hi/wales/6907210.stm

/news/uk-england-cumbria-14401033

http://news.bbc.co.uk/2/hi/business/4397308.stm

/news/uk-england-cumbria-11474494

/news/uk-england-cumbria-14401033.amp

/news/uk-england-merseyside-21553420

/news/av/uk-politics-17089662

/news/uk-england-beds-bucks-herts-28939053

http://news.bbc.co.uk/1/hi/england/lancashire/4396914.stm

http://news.bbc.co.uk/2/hi/uk_news/england/lancashire/4396914.stm

/news/uk-wales-11043869

/news/uk-wales-north-west-wales-11115147

http://news.bbc.co.uk/1/hi/scotland/south_of_scotland/8599732.stm

https://www.bbc.com/news/uk-england-stoke-staffordshire-22338876

/news/uk-england-oxfordshire-22365998

http://news.bbc.co.uk/1/hi/northern_ireland/6228885.stm

http://news.bbc.co.uk/1/hi/scotland/glasgow_and_west/7946620.stm

http://news.bbc.co.uk/2/hi/americas/7306366.stm

https://www.bbc.com/news/uk-england-essex-24107045.amp

/insideout/south/series11/week4_otters.shtml

http://news.bbc.co.uk/1/hi/in_depth/sci_tech/2000/dot_life/1905044.stm

http://news.bbc.co.uk/1/hi/wales/8498132.stm

/news/uk-21417058

/programmes/b03tt7f5

https://ichef.bbci.co.uk/news/976/cpsprodpb/24DD/production/_106173490_khitish.jpg

/news/uk-wales-54784727

https://www.bbc.com/news/uk-wales-54784727

http://news.bbc.co.uk/1/hi/england/london/5219716.stm

http://news.bbc.co.uk/1/hi/england/london/5242934.stm

http://news.bbc.co.uk/2/hi/uk_news/england/london/5242934.stm

/news/uk-21320992

http://news.bbc.co.uk/2/hi/uk_news/england/2352535.stm

http://news.bbc.co.uk/2/hi/uk_news/england/2879989.stm

February 2022

/news/10488360

/news/uk-scotland-tayside-central-37287240

/news/uk-21737627

https://ichef.bbci.co.uk/news/660/cpsprodpb/15FDA/production/_85447009_85447008.jpg

https://www.bbc.com/news/10458875

/news/uk-england-berkshire-55045960

/news/uk-england-35292025

https://www.bbc.com/news/uk-england-essex-20162230

https://www.bbc.com/news/10353214

http://news.bbc.co.uk/1/hi/england/2877979.stm

/news/10353214

/news/10369468

http://news.bbc.co.uk/2/hi/uk_news/wales/mid_/4464402.stm

/news/uk-scotland-south-scotland-29801856

/news/uk-scotland-south-scotland-29831224

/news/uk-scotland-south-scotland-30452017

/news/uk-scotland-south-scotland-30820963

/news/uk-scotland-south-scotland-31622100

/news/uk-northern-ireland-foyle-west-29080069.amp

http://news.bbc.co.uk/1/hi/entertainment/2992593.stm

http://news.bbc.co.uk/cbbcnews/hi/tv_film/newsid_2993000/2993509.stm

/news/business-21844955

http://news.bbc.co.uk/1/hi/england/london/7761466.stm

http://news.bbc.co.uk/1/hi/england/london/7765042.stm

/news/uk-scotland-14464323

/news/uk-scotland-14857004

/news/uk-scotland-glasgow-west-13861199

https://www.bbc.com/news/uk-scotland-edinburgh-east-fife-41337735

https://www.bbc.com/news/uk-scotland-edinburgh-east-fife-41337735.amp

https://www.bbc.com/news/uk-scotland-edinburgh-east-fife-41337735

/news/av/technology-25962744

/news/av/uk-24283743

/news/av/uk-26353265

https://ichef.bbci.co.uk/news/1024/branded_news/F838/production/_97944536_mediaitem97944534.jpg

http://news.bbc.co.uk/1/hi/england/dorset/4437863.stm

https://www.bbc.com/news/uk-england-manchester-28253676

https://www.bbc.com/news/uk-england-manchester-28315024

http://news.bbc.co.uk/local/somerset/hi/people_and_places/newsid_8274000/8274272.stm

https://ichef.bbci.co.uk/news/976/cpsprodpb/118BA/production/_93166817_mediaitem93166816.jpg

https://www.bbc.com/news/uk-england-london-38458084

http://news.bbc.co.uk/1/hi/england/2826181.stm

http://news.bbc.co.uk/1/hi/england/london/4475139.stm

https://www.bbc.com/news/uk-scotland-glasgow-west-37083838

http://news.bbc.co.uk/1/hi/england/london/3158649.stm

http://news.bbc.co.uk/1/hi/england/wiltshire/7391885.stm

/news/av/technology-24282493

/news/av/technology-25962744

https://www.bbc.com/news/uk-scotland-north-east-orkney-shetland-28703590

http://news.bbc.co.uk/1/hi/uk/7771156.stm

https://www.bbc.com/news/uk-england-nottinghamshire-13863230

http://news.bbc.co.uk/2/hi/uk_news/england/wiltshire/7391885.stm

http://news.bbc.co.uk/2/mobile/uk_news/england/wiltshire/7391885.stm

January 2022

/news/av/business-24299900

/news/av/uk-24283743

/news/av/uk-26353265

/news/uk-england-merseyside-31524582

/news/uk-england-devon-18408831

/news/uk-england-devon-18600587

/news/uk-england-36057545

https://ichef.bbci.co.uk/news/640/cpsprodpb/183C3/production/_89176299_composite.jpg

https://www.bbc.com/news/uk-england-31628312

/news/uk-england-beds-bucks-herts-26029877.amp

/news/newsbeat-28768121

/news/uk-scotland-tayside-central-16276615

http://news.bbc.co.uk/1/hi/scotland/edinburgh_and_east/8126468.stm

https://www.bbc.com/news/uk-scotland-glasgow-west-39220213.amp

https://ichef.bbci.co.uk/news/1024/branded_news/10D08/production/_102827886_af21b11a-2547-4506-83bb-433e3d3acb4a.jpg

https://ichef.bbci.co.uk/news/976/cpsprodpb/1586D/production/_115537188_brownnewton.jpg

https://ichef.bbci.co.uk/news/976/cpsprodpb/9E28/production/_106488404_hi053468356.jpg

http://news.bbc.co.uk/2/hi/uk_news/england/tyne/7954901.stm

https://ichef.bbci.co.uk/news/1024/media/images/72766000/jpg/_72766690_000210240-1.jpg

/news/uk-england-nottinghamshire-48030669

/news/uk-england-nottinghamshire-55077562

https://www.bbc.com/news/uk-scotland-south-scotland-26047971

https://www.bbc.com/news/uk-scotland-tayside-central-20512644

http://news.bbc.co.uk/1/hi/england/merseyside/8504904.stm

/news/uk-england-nottinghamshire-45133578

https://www.bbc.com/news/uk-scotland-south-scotland-26047971.amp

/news/uk-england-nottinghamshire-48030669

/news/uk-england-nottinghamshire-54980153

/news/uk-england-nottinghamshire-55077562

https://ichef.bbci.co.uk/news/1024/branded_news/10D08/production/_102827886_af21b11a-2547-4506-83bb-433e3d3acb4a.jpg

https://ichef.bbci.co.uk/news/976/cpsprodpb/1586D/production/_115537188_brownnewton.jpg

https://ichef.bbci.co.uk/news/976/cpsprodpb/5B70/production/_102780432_de52-3.jpg

https://www.bbc.com/news/uk-scotland-glasgow-west-36017556

https://ichef.bbci.co.uk/news/976/cpsprodpb/9086/production/_96889963_queens_park.jpg

/news/uk-scotland-glasgow-west-36017556

https://www.bbc.com/news/uk-scotland-glasgow-west-40567314

https://www.bbc.com/news/world-europe-guernsey-25370759

https://www.bbc.com/mundo/ultimas_noticias/2014/02/

140205_ultnot_grecia_arresto_corrupcion_men

/news/uk-england-tyne-37616349

/news/uk-england-tyne-38520914

https://www.bbc.com/news/uk-scotland-edinburgh-east-fife-39305042

/news/uk-scotland-glasgow-west-39220213.amp

/news/uk-scotland-glasgow-west-40567314

https://www.bbc.com/news/uk-england-manchester-43782463

/programmes/b017ndrh

]]>
0
HTTPS is easy, just turn it on… Thu, 04 Nov 2021 14:51:30 +0000 /blogs/internet/entries/ca919719-f8a4-4304-bf58-f71e82d0a13c /blogs/internet/entries/ca919719-f8a4-4304-bf58-f71e82d0a13c Neil Craig Neil Craig

The HTTPS padlock icon on bbc.co.uk

Back in early 2015, I'd just started working at the Ö÷²¥´óÐã and whilst getting to know who's who and what's what, I discovered to my surprise that large parts of our main websites (www.bbc.co.uk and ) were only available over plaintext HTTP. My immediate thought was, "Well, here's something I can get stuck into immediately - how hard can it be to get to 100% HTTPS?".

We're now about six years on, and we're only just finishing the full migration to HTTPS. All you need for HTTPS is a vaguely modern CDN/traffic manager/server and a TLS cert plus a few changes to your HTML, right? Yeah, wouldn't it be great if things were that simple!

Setting the scene

At this stage, it probably helps to rewind a little to a circa 2015 context. It'd been about two years since the , which had helped to squash any remaining doubts as to the necessity of HTTPS. Around this time, the major web browsers began signalling their intentions to gradually ramp up the pressure on website operators to serve websites over HTTPS by restricting access to sensitive APIs to HTTPS contexts and also via changes in user interface (UI) indicators. Various platforms and services such as  were created or came to prominence, making it cheaper, easier, and faster to get TLS certificates and securely serve web content. The direction of travel for the web was clear - HTTPS was gradually replacing HTTP as the default transport, but we were nowhere near as far along the road as we are now.

The Ö÷²¥´óÐã websites share a common public 'web edge' traffic management service. The web edge is similar to a CDN in that it handles TLS termination (as well as routing, caching and so on), but behind that, there are individual stacks that are managed by our Product teams - these form our , , ,  sites amongst others. It's fair to say in 2015, the number of our Product team's websites served over HTTPS was quite mixed - as was true of much of the internet.

Our web edge already offered HTTPS 'for free' to our Product teams in 2015. To migrate to HTTPS, our Product teams had to do the engineering work for compatibility of their websites and opt-in to an 'HTTPS allowlist' - otherwise, our web edge would force their traffic to HTTP.

Raising the issue

The first formal thing I did towards 100% HTTPS was to present to a forum which most of the Ö÷²¥´óÐã Product architects attended to raise the issue and highlight why we should migrate to HTTPS and what was going to change soon in Chrome in terms of UI signals:

 

Screengrab of a presentation slide which highlights the drivers for HTTPS adoption.

The web browser UI signalling changes for plaintext HTTP were pretty new at the time and not as widely communicated as they are now. The planned UI changes were a really useful driver for our Product teams since they were a concrete change that would have direct user impact - something to galvanise the need for action and a timeline to work to. Our Product teams were, of course, all more than a little bit aware of HTTPS and those teams who hadn't migrated already intended to migrate as time allowed. However, this helped a few of them with a business case to make the change, and the discussion helped bring HTTPS further into the general conversation.

The h2 carrot

'HTTP/2 all the things!' meme on a presentation slide.

A year or so on from my initial presentation about HTTPS, we began to think in more detail about providing HTTP/2 (h2) on our web edge since the support in web browsers and servers/services was mature enough by then. We did the requisite planning work, the usual comms to our teams and then rolled h2 out. We had a bit of an issue with this, and there was a fair bit of work involved but before long, all our HTTPS web pages were also available over h2 - an added carrot to the teams who'd not yet migrated to HTTPS.

Product migrations

Our Product teams have done the bulk of work in migrating Ö÷²¥´óÐã websites to HTTPS on their individual stacks. As well as in-place updates, there has been some major re-platforming work which is moving our Product websites on to new, HTTPS native platforms such as Web Core for Ö÷²¥´óÐã Public Service, Simorgh for Ö÷²¥´óÐã World Service and new, dedicated platforms for Ö÷²¥´óÐã iPlayer and Sounds.

I didn't get involved specifically in any of these Product migrations, aside from the odd conversation and friendly badgering, so whilst it was a lot of work and absolutely vital, it's relatively well-understood work. So, for the remainder of this blog post, I'll focus more on the aspects of our migration that were perhaps less obvious (and often really quite awkward).

Content retention - 'The Archive'

The Ö÷²¥´óÐã has a content retention mandate which states:

13.3.8 Unless content is specifically made available only for a limited time period, there is a presumption that material published online will become part of a permanently accessible archive and should be preserved in as complete a state as possible.

During a re-platforming in circa 2013-14, the decision was taken to archive (rather than migrate to the new CMS) a lot of the older content, which our retention mandate demands we keep online. The archive was produced via a crawler which saved web pages to online object storage as flat HTML and asset files. We ended up with somewhere in excess of 150 million archived web pages across hundreds of retired Products - all of which were captured as plaintext HTTP.

 

An archived web page: Ö÷²¥´óÐã Sing.

Accurately migrating this many wildly differing static pages to HTTPS is not simple. Some quick maths and thinking-through eliminated the option of writing a crawler to run through the archive and update the HTML, JavaScript and CSS in-place - it's too risky, slow and expensive. Instead, I used our comprehensive access logging/analysis system, , to make sure that clients supported it then trialled allowing HTTPS on a section of the archive whilst adding the header to instruct clients to automagically upgrade HTTP links/asset loads to HTTPS.

The trial worked well, so we gradually rolled this out and monitored the effects via access logs, the CSP and  elements of the .

Robots.txt and friends

The final major hurdle we encountered was in serving global static assets - robots.txt, sitemaps, 3rd party authentication files and the like. We were still using our previous-generation traffic managers to host global static assets, and the configuration was unexpectedly coupled to our HTTPS allowlist logic. That wasn't a problem in itself, but it meant that when I asked one of our ops teams to remove the HTTPS allowlist, the serving of these static assets broke. Time for a rethink.

Our 24/7 support/ops team valiantly stepped in to build and run a new service that solved two problems in one - migrating the routing of global assets to our new traffic managers in a single-scheme fashion.

Removing the HTTPS allowlist

Once the robots.txt (et al.) problem was solved, we could finally remove the HTTPS allowlist, which meant that all content on www.bbc.co.uk was available over HTTPS. That was a really key step in this whole process.

HSTS

Once we had all our content on www.bbc.co.uk available over HTTPS, we began rolling out , which instructs to silently upgrade any plaintext HTTP links they come across for www.bbc.co.uk with HTTPS links. So that we can gain confidence and revert in a reasonable time if there are problems, we'll gradually increase the max-age on our HSTS header as follows:

  • Set to 10 seconds, then wait for 1 day (basic test for major issues)
  • Set to 600 seconds (10 minutes), then wait for 2 days (covers most page-to-page navigations)
  • Set to 3600 seconds (1 hour), then wait for 4 days (also covers most iPlayer/Sounds durations)
  • Set to 86400 seconds (1 day), then wait for 14 days (covers frequent users day-to-day)
  • Set to 2592000 seconds (30 days), then wait for 6 months (covers most users)
  • Set to 31536000 seconds (1 year)

To de-risk HSTS, as well as all the work above, progressing HSTS through our pre-live environments and some theoretical analysis, we used the Chrome net-internals facility to locally add HSTS for www.bbc.co.uk.

Assuming the HSTS rollout goes to plan, we'll look into for www.bbc.co.uk to avoid the ToFU (Trust on First Use) issue.

What's left to do?

Having jumped over most of the hurdles in our way, the last few jobs to do right now are:

  1. Use the "force HTTPS" feature in our traffic managers in conjunction with the already deployed CSP "upgrade insecure requests" on our archived web pages to ensure archived pages and their assets are loaded over HTTPS.
  2. Inform our Product teams that they can opt in to using the "force HTTPS" feature and therefore remove their own HTTP → HTTPS redirects in their origin services.
  3. Migrate the remaining couple of websites on www.bbc.com which are still plaintext HTTP, then roll out HSTS on www.bbc.com as well.
]]>
0
Fighting misinformation: An embedded media provenance specification Mon, 04 Oct 2021 15:51:46 +0000 /blogs/internet/entries/5d371e1b-54be-491f-b8ee-9e354bafb168 /blogs/internet/entries/5d371e1b-54be-491f-b8ee-9e354bafb168 Charlie Halford Charlie Halford

For the last few years, the Ö÷²¥´óÐã has had a project running in its technology division looking at technology solutions to various problems in the domain of news disinformation. Part of that effort, called , is working to make it easier to understand where the news you consume online really comes from so that you can decide how credible it is. You can find some history on this in Laura Ellis' excellent "Project Origin: one year on" blog.

Part of Project Origin has been working in collaboration with major media and tech companies, most recently, with the , which it helped form. This group recently released . This spec tackles the problem of missing, trusted provenance information in images / video / audio consumed on the internet. For example, where a video of elections in one country from 10 years ago is being presented as video from recent elections in another. This is an overview of how that specification is intended to work.

Embedding

The C2PA specification works primarily by defining mechanisms for embedding additional data into media assets to indicate their authentic origin. An essential aspect of this data is "assertions" - statements about when and where media was produced. The embedded information is then digitally signed so that a consumer knows who is making the statements.

While the C2PA specification also includes mechanisms for locating this provenance data remotely (e.g. hosted somewhere on the internet), I'll focus on the use case where all data is embedded directly in the asset itself.

Data model

The C2PA specification uses a few different mechanisms for embedding and storing data. Embedding is done with , a container format, and structured data storage is done with a combination of  and  (which is a binary format based on JSON).

Container - The "Manifest Store"

Similar to , the C2PA specification defines several embedding points in a selection of media formats to place a "Manifest Store" in JUMBF format, which is the container for the various pieces of provenance data. Once you've identified where and how a manifest store is embedded in your favourite media format, most of the specification is format-agnostic.

What is JUMBF?

JUMBF (JPEG universal metadata box format) is a binary container format initially designed for adding metadata to JPEG files, and it’s now used in other file formats too. It is structurally similar to the , an extensible container format that is used for many different types of media files. JUMBF "superboxes" are boxes that only contain other boxes. JUMBF "content type" boxes contain actual payload data, the serialisation of which should match the advertised content type of the box. All boxes have labels, which allow boxes to be addressed and understood when parsing. C2PA uses JUMBF in all the media formats it supports to provide the container format for the Manifest, Claims, Assertions, Verifiable Credentials and Signatures.

Each piece of embedded provenance data is called a “Manifest”. A manifest contains a part of the provenance data about the current asset, or the assets it was made from. Because an asset might have been created from multiple original sources or have been processed multiple times, we will often need to store several manifests to understand the complete history of the current asset.

Manifests are located in the "Manifest Store", which is a JUMBF superbox. The last manifest in the store is the "ActiveManifest", which is the provenance data about the current asset and it's the logical place for validation to start. The other manifests are the data for the "ingredients" of the active manifest - i.e. the assets that were a part of the creation of the active manifest. This is one of the key features of C2PA: each asset provides a graph of the history of editing and composition actions that went into the active asset, exposing as little or as much as the asset publisher wants.

Each manifest within the store is again its own JUMBF superbox. A manifest then consists of: a "Claim", an "AssertionStore", a "" and a "Signature". Manifests are signed by an actor (the “Signer”) whose credential identifies them to the user validating or consuming them.

Diagram of a Manifest box, without any VCs

Assertions

Assertions are the statements being made by the signer of a manifest. They are the bits of provenance data that consumers of that data are being asked to trust, for example, the date of image capture, the geographical location, or the publisher of a video.
In the spec, each assertion has its own data model. Some are published as "Standard Assertions" in the spec, some are adoptions of existing metadata specifications such as ,  and , and it is expected that implementers will extend the spec by defining their own as well.

Media metadata isn't new

For example, the EXIF standard is nearly universal in digital photographs, used to record location and camera settings. The fundamentally new thing that C2PA does is allow you to cryptographically bind that metadata (with hashes) to a particular media asset and then sign it with the identity credential of the origin of that data, ensuring that the result is tamper-proof and provable.

Assertions are contained in their own JUMBF Content Type Box in the assertion store superbox and are serialised in the format defined in the spec for that assertion. The C2PA-defined assertions are stored as CBOR, while most adopted assertions from other standards are JSON-LD.

Here's an example of an "Action" assertion (in ) which tells you what the signer thinks was done in creating the active asset:

{
  "actions": [
    {
    "action": "c2pa.filtered",
    "when": 0("2020-02-11T09:00:00Z"),
    "softwareAgent": "Joe's Photo Editor",
    "changed": "change1,change2",
    "instanceID": 37(h'ed610ae51f604002be3dbf0c589a2f1f')
    }
  ]
}

And here's an EXIF one (in JSON-LD) that contains location data:

{
  "@context" : {
    "exif": "http://ns.adobe.com/exif/1.0/",
  },
  "exif:GPSLatitude": "39,21.102N",
  "exif:GPSLongitude": "74,26.5737W",
  ...
}

The one critical assertion is the binding, something that binds the claim to an asset. In fact, the spec requires one. This ensures that claims are not applied to any asset other than the one they were signed against. This is important in helping to ensure that the consumer can trust that the C2PA data wasn't tampered with between the publisher and the consumer. There are currently two types of "hard bindings" available, a simple hash binding to an area of bytes in a file or a more complex one intended for ISO BMFF-based assets, which can use their box format to reference specific boxes that should be hashed.

Claim

The claim in a manifest exists to pull together the assertions being made, any "redactions" (removals of previous provenance data for privacy reasons), and some extra metadata about the asset, the software that created the claim, and the hashing algorithm used. Assertions are linked by their reference in the assertion store and a hash. The claim itself is another JUMBF box, serialised as a CBOR structure. This is the thing that is signed, and it provides a location to find the signature itself.

Signature

The signature in a manifest is a CBOR structure that signs the contents of the claim box. COSE is the CBOR version of the JOSE framework of specs, which includes JWT/JWS. The signature is produced using the credentials of the signer. The signer is the primary point of trust in the C2PA Trust Model, and consumers are expected to use the signer's identity to help them make a trust decision on the claim's assertions.

The only currently supported credentials for producing the signature are x.509 certs. The specification provides a profile that certificates are expected to adhere to (including key usages such as “id-kp-emailProtection”, which is a placeholder). The specification does not include any requirements on how validators & consumers assemble lists of trusted issuers, as it is expected that an ecosystem of issuers will develop around this specification. Instead, it simply requires that validators maintain or reference such a list of trust anchors. Alternatively, they can put together a trusted list of individual entity certificates provided out-of-band of the trust anchor list.

What now?

This is an overview and omits both the detail required to produce C2PA manifests and the breadth of some of the other components of the specification (e.g. ingredients, the use of Verifiable Credentials, the concept of assertion metadata, timestamping etc). I'd love to produce a worked example of how to extract and validate a C2PA manifest from an asset; watch out for that in the future. I will highlight an , and I know of other implementations in the works, too.

At the Ö÷²¥´óÐã, we can't wait for this specification to develop and gain adoption. We'd love to see it supported in production and distribution tools, web browsers, and on social media and messaging platforms. We really think it can make a difference to some of the harms done by mis- and disinformation.

]]>
0
Streaming Euro 2020 live at a record new scale Tue, 21 Sep 2021 13:38:10 +0000 /blogs/internet/entries/fe629b38-57af-49c8-8922-352174101511 /blogs/internet/entries/fe629b38-57af-49c8-8922-352174101511 Pierre-Yves Bigourdan Pierre-Yves Bigourdan

Summer 2021 offered a rich selection of events to sports enthusiasts: , and the , to name but a few. An ever-increasing proportion of the Ö÷²¥´óÐã’s audience has been moving from traditional broadcast to online consumption - the Euro 2020 Final, where Italy played England, set a new record for Ö÷²¥´óÐã iPlayer, with 7.1 million viewers streaming the match online.

In comparison, the 2018 World Cup Quarter Final, where Sweden opposed England, only attracted 3.1 million online viewers, yet our systems at the time became overwhelmed, leading to . Luckily enough, this happened at the very end of the match when the outcome was already settled. However, this incident did not go unnoticed by our engineers and triggered a significant redesign of our workflows.

How did we scale our live streaming architecture to reliably deliver media and allow audience figures to reach new heights?

From pull to push

To answer that question, let’s first review what happened in 2018. Many streaming platforms, including iPlayer at the time, operate with what is commonly described as a pull model. The player on your TV, phone or computer requests the media from a third-party . This forwards the request to the Ö÷²¥´óÐã’s routing and caching servers, which in turn send it on to the packager. The role of this last system is to transform encoded media by wrapping the raw video and audio into container files that are suitable for distribution to a variety of client devices.

You can view things as a funnel: multiple layers of caching and routing are present along the way to collapse millions of player requests every second down to a trickle of requests back to the origin media packager, each layer pulling the media from the next layer up. All of this occurs while trying to keep as close to the live time of the event as possible.

The 2018 pull model. Arrows represent the flow of media requests, from iPlayer on user devices all the way up to the packager.

Even though widely used, this pattern has some significant drawbacks, the best illustration being the major incident that hit the Ö÷²¥´óÐã during the 2018 World Cup quarter-final. Our routing component experienced a temporary wobble which had a knock-on effect and caused the CDN to fail to pull one piece of media content from our packager on time. The CDN increased its request load as part of its retry strategy, making the problem worse, and eventually disabled its internal caches, meaning that instead of collapsing player requests, it started forwarding millions of them directly to our packager. It wasn’t designed to serve several terabits of video data every second and was completely overwhelmed. Although we used more than one CDN, they all connected to the same packager servers, which led to us also being unable to serve the other CDNs. A couple of minutes into extra time, all our streams went down, and angry football fans were cursing the Ö÷²¥´óÐã across the country.

Ö÷²¥´óÐã iPlayer outage during the Euro 2018 quarter-final. Photo: Steve Hy

We did fix and mitigate the immediate performance issue. After running several long and deep root cause analysis sessions, we concluded that having our media servers exposed to a request load that was ultimately not in our control was not a safe position to be in.

We decided to re-architect the system by switching from a pull to a push model. The idea is quite simple: produce each piece of media once and publish it to a dedicated live origin storage service per CDN. From where we stand, the CDN acts as a pure ingest point and has no visibility on any of our servers. In other words, we alleviate any risk of the CDN overwhelming our systems: as more people view our streams, the load remains constant. We end up with a much cleaner separation of concerns, with the Ö÷²¥´óÐã accountable for producing all media in time and the CDN now solely responsible for caching it and making it available for download at scale.

The 2021 push model. Ö÷²¥´óÐã iPlayer on user devices simply downloads media that was previously published to a CDN.

Drilling down on the packager

Before they arrive at our packager, video and audio signals are encoded into formats appropriate for distribution to our audiences. The cloud-based encoder is also responsible for generating an adaptive bitrate set of outputs, in other words, a range of picture and sound qualities to cater for different network speeds and device capabilities.

The resulting encoded media is then sent to the packager. Its role is to prepare all the files which will be requested by devices to play a stream over an HTTP connection. The packager produces two types of streams:

- streams: in our case, the encoded media is packaged in fragmented containers. Apple devices and some older TVs use these.
- streams: in our case, the encoded media is packaged in fragmented containers (MPEG-4 part 12), commonly referred to as fragmented MP4. All other devices use these.

At a high level, the revised workflow is composed of four main components, the repackager, the distributor, the manifest generator, and the conductor:

A high-level architecture of the new push packager workflow.

All four components are designed as load-balanced fleets of microservices to support the load of dozens of Ö÷²¥´óÐã streams continuously flowing through them. These streams correspond to all our linear TV channels and their many regional variants, half a dozen World Service streams, and a variable number of event streams. The workflow is run in two independent cloud regions to allow for additional resiliency. Let’s delve into the role of each component.

The repackager

The upstream encoder produces video using and audio using . Both the video and audio are wrapped in TS containers, and the encoder continuously sends small container files which hold roughly 4s of content each. The repackager component receives these chunks of content via HTTP PUT requests. Conveniently, their format is suitable for HLS streaming: to make HLS available, the repackager can simply forward them untouched to the next component in the workflow, the distributor.

However, it additionally needs to transform the TS chunks in a format suitable for our DASH streams. The repackager’s task is to parse the TS container and extract the raw H.264/AAC data. Using information gathered by reading through this media data, it rewraps the pictures and sound in an MP4 container with all required metadata. The generated MP4 files are sent to the distributor alongside their TS counterparts.

Structured metadata from one of our generated MP4s, displayed in the mp4box.js viewer.

The distributor

The distributor component receives the MP4 and TS chunks sent by the repackager over HTTP, and in turn, publishes them to CDN storage locations so that our audiences can access them. Depending on the stream, one file may be published to several CDN endpoints for additional redundancy. The distributor can essentially be viewed as a one-to-many mapper, handling all authentication and retry behaviour when interacting with a CDN.

Additionally, for every TS chunk it receives, the distributor sends an HTTP request to the manifest generator, triggering the generation of a manifest corresponding to that chunk.

The manifest generator

Manifests are text documents. Their primary goal is to guide the player to download the different media chunks within a given stream. When the play button is pressed, the player first downloads the manifest, and using the information it contains, keeps on requesting small media files containing 4s of content. The downloaded files are rendered one after the other, allowing viewers to have a continuous and seamless playback experience. HLS and DASH define different types of manifests, and the manifest generator component is responsible for creating these variants. Generated manifests are sent to the distributor component over HTTP to be published to the CDN alongside the media chunks.

The conductor

The conductor provides several REST API endpoints to configure the behaviour of the other components in the workflow. For example, it is responsible for driving the automatic scaling of the microservices when additional streams are started, adjusting the monitoring, keeping track of start and end time of events, filtering encoder inputs, and a variety of other management tasks.

Paving the way to the future

Driven by a cross-departmental effort involving several teams, our push packager workflow has been successfully running in production since February 2021. Initially trialled with the Ö÷²¥´óÐã Two HD channel, it now continuously carries over 40 streams, with additional event streams soon to be migrated. Over a million new files are produced every hour, and billions of media chunks have successfully been uploaded to CDN storages since its inception. Across all summer 2021 sporting events, the system allowed us to reach a record 253 million play requests on Ö÷²¥´óÐã iPlayer and Ö÷²¥´óÐã Sport.

Even though the numbers shared here fit well within the realm of hyper-scale when it comes to data produced and network traffic, it is worth noting that online streaming is a small proportion of the Ö÷²¥´óÐã’s audience coverage. Linear broadcast TV still makes up the lion’s share. However, online consumption is steadily increasing, reaching about a quarter of all viewers during the summer events, and an IP-only future is fast approaching. With these efforts, we will be better placed to move forward: our new packager gives us the flexibility to adapt our content to take full advantage of improvements in specifications and allows us to reliably and cost-effectively serve millions more online viewers in the coming years.

Want to see our system in action? Open Ö÷²¥´óÐã iPlayer and simply press play on one of our live streams!

]]>
0
Introducing machine-based video recommendations in Ö÷²¥´óÐã Sport Tue, 14 Sep 2021 12:07:03 +0000 /blogs/internet/entries/f74ea410-5ec4-4add-9daa-a29d25176ccd /blogs/internet/entries/f74ea410-5ec4-4add-9daa-a29d25176ccd Robert Heap Robert Heap

From this week we are adding a new feature to our short form video pages on the Ö÷²¥´óÐã Sport website.

Related clips

On every video page in Ö÷²¥´óÐã Sport you’ll see a related links section. This is usually put together by our editorial colleagues, a routine task which can be time consuming. They have good knowledge about related content, but cannot know about everything, which means that the audience do not see some content that might be relevant.

Short Form Video & Datalab

With this in mind we have worked with Datalab (our in-house Ö÷²¥´óÐã machine learning specialists) to create an algorithm-based video recommendations engine which we hope will help our audience see more of the content they love whilst reducing the editorial overhead of creating a set of relevant links.

Algorithm-based recommendations

The engine works by combining content information about the clip with more information about user journeys from across the Ö÷²¥´óÐã. This combination of multiple sources should provide a more relevant list of videos for our audience to watch next. This is the first cross product engine supporting user journeys across News and Sport, which means that you may see news, sport or a combination of both in the module. This is the first version of the short form video recommender, there will be more improvements to come, as we continue to develop it.

Launching the new recommendations

The plan is to launch this new functionality on all American Football clips the week commencing 13 September to give the engine a trial with freshly published content and to give us the opportunity to measure its impact. Provided all is well, we will gradually release this feature across all Ö÷²¥´óÐã Sport videos. After that we will begin to roll out the same engine for Ö÷²¥´óÐã News. Beyond that we will continue to work with editorial colleagues to improve it over the coming months.

If you have any feedback on this new video experience, please leave your comments below.

]]>
0
Refreshed interface, extra features: new Ö÷²¥´óÐã Media Player launched for web browsers Thu, 02 Sep 2021 16:04:34 +0000 /blogs/internet/entries/65db5af7-1ec1-4ba5-9f09-4f3c5f632b03 /blogs/internet/entries/65db5af7-1ec1-4ba5-9f09-4f3c5f632b03 Oli Freke Oli Freke

We are pleased to announce the launch of our new web media player, codenamed Project Toucan. We have been working on the player over the last year, and it brings many benefits for audiences, including a refreshed user interface and additional features. The new player is already live on Ö÷²¥´óÐã Weather, Ö÷²¥´óÐã Food and Ö÷²¥´óÐã Motorsport for most browsers as it begins to incrementally roll out over the coming months – Safari and iPhones will be supported in due course.

New playback and skip forward and back controls in the new version of the media player.

Toucan is a significant update to our existing Standard Media Player (SMP) - which has been around in one form or another since the 2012 Olympics. The existing player has been continuously updated since then and is still used across the whole of the Ö÷²¥´óÐã website, from Ö÷²¥´óÐã iPlayer to Ö÷²¥´óÐã Sounds and from the World Service to Weather. Over the last twelve months, the player delivered over three billion streams to web browsers on desktop, tablet, and mobile phones.

Why introduce a new player?

The SMP dates from 2012 and has accumulated support for many older browsers and technologies, which are increasingly being deprecated or even no longer exist. One example is the use of iframes which is used to separate the player code from the embedding page code. This technique still works but is no longer the preferred method in the web development community. Additionally, we wanted to completely redesign the user interface (UI) and take a mobile-first approach. Building a brand new UI on top of an old codebase didn’t make sense due to the incompatible technologies we wanted to use. The advantage of a new player is that we can drop all the old code, rebuild more efficiently and be more able to add up to date features and technologies in the future.

Toucan, therefore, supports many modern features that audiences expect. These include 20-second skip forward/back buttons, variable speed playback, slicker animations, and a cleaner design with mobile use in mind. Accessibility is also vitally important and has been considered from the start of our development. The player now has keyboard control – press space to play and pause, arrow keys to seek forward and back, and F to go full screen.

The new volume slider in the latest Ö÷²¥´óÐã media player.

One major advantage we’ve brought to the new player is a componentised approach. This means that the UI is loaded separately from the main player and enables us to produce different UIs more easily if required and load the most appropriate one. For example, a child-friendly version with larger buttons or additional features could be created and used where necessary (and save download costs by not loading any UI which is not needed). Another advantage of the componentised UI is that we can build-once, use-everywhere, meaning we don’t waste effort building the same UI for multiple use-cases. The new UI that comes with the new player is already being used with the new Chromecast receiver, which has prevented exactly that kind of duplication. This UI can be seen now on your TV if you cast from iPlayer mobile (and shortly, iPlayer web and Sounds mobile).

New Chromecast receiver controls used in the iPlayer mobile app version of our updated player.

We have also updated to a more modern version of CSS and JavaScript, and the player continues to be built on , the open-source media playback component, which we contribute back to for the benefit of the Dash.js community. New releases of Dash.js are, of course, always fully tested before making it live in production.

There are performance gains from the smaller size and more efficient build practices of Toucan and benefits from not needing to support as many older browsers as the current player does - and will continue to do so.

It’s built using , which was recently released in browsers as a native way to produce a component that can easily be integrated in diverse situations. We’ve also dropped our use of iframes in favour of Web Components’ – this is leading to a significant decrease in player load times.

Now that we have launched the first version, we will be adding all the other features that audiences need in a modern player. This includes audio on-demand, podcasts, live video, live audio, variable speed playback and much more. This will take time, but keep your eyes peeled as we incrementally develop the player across the Ö÷²¥´óÐã’s digital services.

You will soon see the new player on all our web and mobile services that playback video and audio, including Ö÷²¥´óÐã Sport, Ö÷²¥´óÐã News, Ö÷²¥´óÐã iPlayer, Ö÷²¥´óÐã Sounds, World Service and many more over the coming months as the features that these services require are built and launched into the new player.

While Toucan is exciting and will eventually replace the current player, we won’t rush to switch off the SMP. It will be needed by the audience where they are using browsers that don’t support the necessary features that Toucan requires, and we are committed to making sure that people can enjoy the Ö÷²¥´óÐã wherever they happen to be and on whichever platform they choose to use.

But for browsers that do support Toucan - we hope you enjoy that experience. Do send feedback to us at mediaplayer@bbc.co.uk.

]]>
0
Hacking the future Wed, 28 Jul 2021 12:25:07 +0000 /blogs/internet/entries/f55340ea-bfbb-4224-8400-1380c058b3aa /blogs/internet/entries/f55340ea-bfbb-4224-8400-1380c058b3aa Bill Thompson Bill Thompson

The Ö÷²¥´óÐã is, famously, a creative organisation, and there has been no shortage of imaginative ways to help people feel connected to each other while many of us have been largely working from home. Online team meetings, social events including quizzes, pet shows, yoga and even cookalong sessions have all helped to bring us together, even if it's been via Zoom, Teams or Slack, and working practices for teams have adapted and continue to adapt to ensure that we can be effective.

One challenge has been to provide spaces to meet and collaborate with new people outside our usual teams when we're not in the same buildings. The recent Ö÷²¥´óÐã100 Hackathon was a great example of what can be achieved, pulling dozens of people from across the Ö÷²¥´óÐã's Technology and Product groups into small teams and getting them to work together on shared challenges.

Running across June and July, the hackathon was jointly organised by the Ö÷²¥´óÐã and Google Cloud and took place entirely online. It began with a series of online sessions to help people get familiar with Google Cloud services, as not everyone was using them. The main hack took place over two weeks, culminating in a judging day when every team got to present their ideas and get feedback.

As next year is the Ö÷²¥´óÐã's centenary, the teams were asked to consider how we could make the best use of our rich history and the material in the Ö÷²¥´óÐã's extensive archive to engage future generations, with a view to shaping the next hundred years. The world in 2022 is very different from 1922 when radio was in its infancy, so it felt like a good challenge and allowed participants to explore how modern tools like the BigQuery cloud data warehouse or the image classification capabilities of Vision AI could be used to deliver new Ö÷²¥´óÐã services.

Teams were asked to focus on one of four areas:

  • Education: How can the Ö÷²¥´óÐã support schools with educating future generations through the innovative use of technology?
  • Diversity & Inclusion: How can the Ö÷²¥´óÐã provide content and services that are more representative of the entire UK population?
  • Next-generation: How can the Ö÷²¥´óÐã blend broadcasting & digital in a way that enables different interactions with the future generation of the Ö÷²¥´óÐã?
  • Content: How can the Ö÷²¥´óÐã continue to provide unique, high impact content that's universal?

After the training sessions, each team spent at least two days working on their challenge in the two weeks of the hackathon, with full access to a range of Google Cloud services. However, the intention, as with any hack, was not to produce a fully-featured solution but to do just enough to demonstrate the feasibility of an interesting idea.

And they certainly did that. As one of the judges, along with Ö÷²¥´óÐã Chief Design Officer Ellie Runcie and Rich Radley from Google, I got to watch the presentations from the finalists, and it was impressive to see just how much the teams had embraced the challenge, thought through the problem areas, refined their thinking and then delivered a convincing walkthrough.

The winning team, made up of Matt Corbett, Chelsea Ballantyne, Michael O'Malley, Thomas Preece, Michael Maclean and Ben Fields, came from across the division and brought their complementary skills to bear on the pressing issue of encouraging younger audiences to explore more of the Ö÷²¥´óÐã's rich collection of programmes.

Their tool lets a viewer take an image from a programme, perhaps the thumbnail used in its programme page, and use the Cloud Vision API to extract as much data as possible about who is in the image, where it was taken, as well as any text. This is then used as the basis for a search across the Ö÷²¥´óÐã's collections. This is then used to drive a number of different navigation systems, for example, presenting the material on a timeline to encourage exploration of older material.

So, for example, someone could select a photograph of Stacey Dooley and be offered a range of programmes she has featured in. One possible extension the team discussed was also looking up future programmes and where it includes audience questions – for example, Question Time - letting the user submit questions directly. This connection between archive search, upcoming programmes, and audience interaction was especially imaginative.

As judges, this project impressed us in two ways. First, their idea was simple to describe – though complex to develop, as simple ideas so often are – and second, they had actually built a working end to end solution on top of the cloud services they had available so that we could see it in operation.

The team is now looking at how their idea might work with existing tagging and metadata systems, but the point of a hackathon like this is not to build a working tool but to explore ideas in a creative, stimulating and collaborative way. This certainly seems to have happened with all the teams involved here.

]]>
0
Philip 21 - an interactive story exploring race, love and modern Britain Tue, 20 Jul 2021 13:12:44 +0000 /blogs/internet/entries/7007a13e-2c58-4011-9d38-bfeef2c56cbc /blogs/internet/entries/7007a13e-2c58-4011-9d38-bfeef2c56cbc Joey Amoah Joey Amoah

Philip 21 is a brand new narrative object-based media (OBM) experience from that takes the premise of a date with a young black man and turns it into an introspective examination of race, love and modern Britain. In this blog post, we look at the techniques and mechanics that underpin this and other branching narrative experiences, examining how they keep audiences engaged compared to traditional media.

In this regard, two specific areas of the project need to be examined; the fabula and syzhuet of the authored experience; and the dual narrative created by having the outcome of the story that each audience member sees be dependent on the choices they make.

The 'fabula' is a literary term used to refer to the raw material of a story, what takes place and the chronology of events. It describes the skeleton of the experience, story beats and the audience journey. The 'syzhuet' describes how the story is organised and presented to audiences. It covers everything from the perspective the story is told from to the arrangement of actors and the cinematography of a scene.

In traditional media, the audience is passive and cannot interact with what is being shown. Storytellers may play with the audience journey and how the story is presented, but they never surrender control of the constituent elements, and they do not offer alternative and equally valid branches. halucid_ have had to wrestle with the challenge of making the fabula and syzhuet work together while also giving up a degree of creative control.

The fabula and syzhuet of the authored experience

In the case of Philip 21, the fabula could be described as being broadly linear. The audience arrives for a date with Philip; they engage in conversation with him and are ultimately asked if they would like a second date or not. However, this simple sequence is not what is received by the audience. What does take place is a fragmented series of scenes where progress can only be made through user choices and engagement. halucid_ plays with the fabula and utilises the narrative setting, the conversational structure and the first-person perspective to drive the experience forward. Philip 21 takes the narrative setting, that of a date, and uses it to establish the boundaries of the world and to inform us on how we should behave. Since many of us will be familiar with this experience from our own lives, halucid_ leans on the understanding of social norms to get audiences to participate in the way that they desire. Building on this, halucid_ uses the codes and conventions of conversations to create an internal metre that demands our engagement. It is only through responding to Philip’s questions and internalising his responses that the narrative can advance. In so doing, it bids the viewer to suspend their disbelief and enter into the story world. Finally, the first-person perspective means that the audience is always focused on the subject, unable to look away, and the fixed camera position creates a sense of intensity, intimacy and immediacy, which is further heightened by the one-to-one interaction enjoyed with Philip.

These creative decisions help move the narrative forward and straddle the line between the fabula and how the authored experienced is presented. This is particularly important to the narrative OBM experience because both content creators and audiences are jointly responsible.

Philip 21 can be navigated in several different ways, with each choice offering a different route through the experience. These routes have been created by halucid_, but audiences have the freedom to select which paths to follow. They can choose a path from the outset or change course at any point, meaning that the syzhuet presented is unique to each viewer. Philip 21 has no primary path, and as a result, all routes through the experience and all outcomes received are equally valid.

The dual narrative

The second interesting element worthy of discussion about Philip 21 is how it goes about creating a dual narrative. On the one hand, Philip 21 is an authored experience, a story that halucid_ is seeking to tell, and on the other, there is the audience experience and what the audience bring and take away from the experience. The audience is integral to delivering Philip 21, and by taking part, they are positioned not as passive watchers but are co-protagonist alongside Philip. The viewer becomes a character in the story and must decide how to approach the situations in the story.

(Jason Dodd Photography)

The viewer must decide if they will approach the work sincerely as their authentic self or assume a persona/play a role that goes against type. This choice, whether conscious or unconscious, determines where the story goes. This way, what is presented back to the audience is a reflection of choices made. Philip 21 could be considered as having two narratives. The authored story and one reflected to the audience based on how they interact with the experience.

What comes next

Narrative OBM experiences are still in their infancy, and we are only beginning to understand the impact of content creators giving over control to audiences. Altering the syzhuet of a story presents a wide array of creative opportunities for creators and audiences, but these choices will need to work in tandem with the fabula and not distract from the story. We are unsure of what works best and are eager to see further experiments in this area.

Likewise, the interplay between the authored experience and the one reflected back at audiences is something we are keen to explore in more detail. What would happen if additional choices were offered to audiences? What would occur if a story was told episodically and not in one session? How would audiences experience this? The only way to find out is to build and test these kinds of experiences.

]]>
0
Beat the Bot - use your voice to challenge our sport bot Mon, 05 Jul 2021 11:10:05 +0000 /blogs/internet/entries/e17af97c-925b-4526-ab38-e9d79c9d02c4 /blogs/internet/entries/e17af97c-925b-4526-ab38-e9d79c9d02c4 Prabhjit Bains Prabhjit Bains

For two years, we've been creating the Ö÷²¥´óÐã's first synthetic voice. Computer-generated, it's helping us as a public service broadcaster to dip our toe in this new technological space. The voice is designed to be used across a wide variety of Ö÷²¥´óÐã outlets, reflecting our core editorial and brand values.

Once we made the voice, we began looking for opportunities to test it with our audiences. Not only did we want to showcase our synthetic voice, we also wanted to explore whether we could use it to begin conversations with audiences. How does speech recognition fare with the wide range of accents across the UK? Can we see a future where audiences could have a conversational relationship with the Ö÷²¥´óÐã? A quiz was the perfect opportunity to start to test these questions out.

Play Beat the Bot! Name relegated Premier League teams using speech recognition.

The Ö÷²¥´óÐã's brilliant line-up of presenters and on-air talent will always be at the heart of our content. But we think there's also a role for a synthetic voice to augment them. A synthetic voice could power interactive quizzes with almost limitless questions and challenges. It could improve the accessibility of existing content. And it could help create new content individually personalised to our users.

James Fletcher, Editorial Lead, Synthetic Media and Conversational AI

Sports Quizzes

Quizzes are participation experiences in their purest form. And we know our Ö÷²¥´óÐã Sport audiences love doing really obscure and competitive quizzes, the harder the better...

The surge in DIY Zoom quizzes during the pandemic may have fizzled out, but a whole host of TV quiz shows with high production values have taken their place. Amidst quiz fever, we started to think about making a quiz that showcased our new synthetic voice and allowed audiences to participate using their own voice too.

Beat The Bot

So we created Beat the Bot, a web-based voice quiz where you have to guess the names of all the Premier League teams that have ever been relegated. You play in turn against the bot, with no room for error. The bot is never wrong.

A screenshot from Ö÷²¥´óÐã Sport's Beat the Bot voice game, available on Ö÷²¥´óÐã Taster. We've pixelated the answers, so no cheating!

Beat the Bot is a testbed for launching the first of many voice-enabled experiences that audiences can engage with through their browser on their desktop or smartphone using their in-built microphones. We also made sure that audience privacy is un-compromised, which is key in creating a safe environment for more experiences like this in the future.

Jamie Chung, Executive Product Manager

Does using your voice make a quiz more engaging?

We wanted to test a hunch that using your voice would give the quiz more jeopardy and deepen engagement. When it works well, using your own voice provides a frictionless experience. By reducing the effort needed to type answers and correct spellings, gameplay can happen at a natural pace. However, if the speech recognition doesn't understand your accent and you are saying the right answer, a voice quiz can be more frustrating than a text-based one. Using your voice to complete a quiz may be a novel experience for many of our users; given that this is the first voice web quiz for the Ö÷²¥´óÐã, we had to overcome some design challenges.

One of the biggest UX challenges when designing Beat The Bot was indicating to the user when it was their turn to speak. If a user isn't sure when the microphone is listening and speaks too soon or too late, it can spoil their chances of winning. So we used visual clues in the interface to alert the user when it's their turn to speak and a circular countdown timer that slows ebbs away, telling the user how much time they have until the microphone will close.

Paul Jackson, UX Designer

What did people think?

After two weeks of being live on Ö÷²¥´óÐã Taster, we had a completion rate of 67%, and 65% of people played it more than once. The mixed success of speech recognition has had an impact on playability for some people; we're aware this is an area that needs improving before voice quizzes can be rolled out on a larger scale. But the numbers of users retrying the game demonstrate that the format works. Once we can improve the speech recognition for a broader range of British accents, the format could be repeated for a wide range of quizzes across the Ö÷²¥´óÐã.

]]>
0
New look subtitles and playback for Ö÷²¥´óÐã iPlayer on TV Thu, 08 Apr 2021 08:00:32 +0000 /blogs/internet/entries/bea5fa67-fd72-40df-acce-2966cf499ae2 /blogs/internet/entries/bea5fa67-fd72-40df-acce-2966cf499ae2 Andrew White Andrew White

From today, we’re rolling out a new look for Ö÷²¥´óÐã iPlayer’s playback on TVs. It’s a cleaner, sleeker and more pared-back interface, with some changes to how things appear during playback and new, improved subtitles you can customise and control.

The first thing most viewers will notice is the playback bar along the bottom. You will now see a simple, elegant bar that shows how far through the programme you are.

Gone is the play/pause button - play and pause icons are now briefly displayed in the centre of the screen when pausing and resuming, whilst rewinding and fast-forwarding brings up visual stills from the programme, so you can easily see when to press play again.

All the extra controls for more episodes, subtitles and settings and the button to add a programme to your list to watch later have all been moved to the top left of the screen.

As part of these changes, we’ve also made significant improvements to the way viewers can control subtitles on iPlayer. The new position of the subtitles and settings menu makes it easier than ever to turn subtitles on or off, as well as making it easier to choose the audio described and signed versions where available; plus, we’ve also added the ability to change and control the size of the subtitles.

Previously subtitles on iPlayer were automatically displayed as a larger size than we use on broadcast, so as part of these changes, we’ve made the default setting a smaller size. For those who need larger or, indeed, even smaller text, they can now choose from a range of five options. That choice is remembered for other programmes they watch in the future.

These changes follow some other recent improvements we’ve made to subtitles on iPlayer on TV. Previously subtitles would appear as coloured sans serif text with a black outline, always at the bottom-middle of the screen. This was far from ideal as, for example, it could be difficult to read the white text if the video image behind it was also white or was patterned. And if the part of the video image behind the subtitles contained something that viewers needed to see to understand the programme – for example, the clues on Only Connect – they could only see it by switching subtitles off.

The improvements we’ve made recently mean when you’re watching iPlayer on a TV, subtitles are now clearly readable, in the Ö÷²¥´óÐã Reith Sans typeface, with a black background behind the text, and the correct colours to show who is talking. They are also now positioned to take account of what’s on-screen, so they will no longer be covering important information, and mean our viewers who use subtitles can play along with Only Connect and enjoy Victoria Coren-Mitchell’s witty and withering jokes at the same time.

Currently, the new size controls are only available on our on-demand content but will be coming to live channels on iPlayer in the coming weeks. Let us know your feedback on the new look playback interface, the new subtitle controls or anything else at bbc.co.uk/contact.

> Ö÷²¥´óÐã iPlayer - Accessibility

> Ö÷²¥´óÐã Technology + Creativity - Accessibility

> Ö÷²¥´óÐã R&D - Casualty - Accessible and enhanced audio trial

]]>
0
Quality engineering for a shared codebase Mon, 22 Mar 2021 13:39:37 +0000 /blogs/internet/entries/c3bfeca9-88b5-4930-8be0-d7ca77ac6ea6 /blogs/internet/entries/c3bfeca9-88b5-4930-8be0-d7ca77ac6ea6 Abigael Ombaso Abigael Ombaso

The ‘You might have missed’ section showing featured content at the bottom of the Ö÷²¥´óÐã homepage

The Ö÷²¥´óÐã is developing a shared platform for building its digital products to reduce development complexity and duplication as much as possible. The aim being to enable quicker and more efficient software development processes resulting in quicker delivery of digital content to our audiences. Read more about the technology changes.

A key aspect of this project has been having a shared repository for the Presentation layer code with different teams working on this platform. This blog will be sharing our experiences so far through the lens of quality engineering by answering three commonly occurring questions that pop up before, during, and after product development — who is going to use the product, how will we ensure quality, and what have we learned so far?

Who will be using the product?

Engineers across different teams working on the platform directly and our digital products consumers are the main product users. We want to keep making great digital products (quality, usability and design), even as we change technology platforms, while also minimising bugs in our software as much as possible.

In order to reduce bugs and issues raised, the testing is integrated into the development workflow, and team members across disciplines have ownership of the product quality. Having a consistent approach to testing features in the platform and having a quick feedback loop for spotting and fixing defects early, helps in minimising the risks and impact across different teams. This is an ongoing process with fine tuning based on feedback from the development teams.

Solution: The users’ needs, (in our case digital products users and engineering teams building on the shared platform) help to define the product requirements that influence the test process.

How do we do the testing?

One of the key things Test engineers and other project stakeholders consider are the risks. The impact of different code merges and changes cascading to different teams was one such risk in the shared repo. Having a shared platform meant sharing other infrastructure (besides a GitHub repo), such as deployment pipelines, communication channels in Slack, documentation, etc.

A consequence of this is that deployments are now visible to multiple teams or stakeholders, with the notifications in our Slack channels flagging failing builds. Bugs get flagged up quickly and when needed, different development team members are able to ‘swarm’ (even while working remotely) to collaboratively debug and resolve these issues. This has led to more frequent and better communication across teams and we think this has been a beneficial and worthwhile project just for getting more people talking and working together more often.

There has been consistency planned into the project as a whole from the start, for example with the . Similarly, it was important to have consistency across teams when it came to testing the features developed in the platform, as we simultaneously worked on this shared code space, in order to minimise bugs, regressions and other product risks. Having an overarching Test strategy considering approaches to manual and automated testing (guided by the and ) has informed our testing.

Automated tests form part of pull request checks and before deployment to Live. We have consistency in the automated test tools we use and engineers across teams are able to know what the expectations for testing are. This is by no means a finished endeavour, but a continuous work in progress so having forums like the Test Guild and team knowledge sharinghelp with communication, continuous learning, and further improvements.

Because of the scale of the project we rely on automated test tooling for regression testing. We also began to use fairly new test tools for visual regression testing like Storybook and Chromatic. Alternatives were Percy, Nightwatchjs and Browserstack. For other types of automated tests we use Puppeteer and formerly Cypress. We had communication channels with the test tool makers to feed back issues encountered and to request new features as we scaled and grappled with using the different test tools.

Solution: Have a test strategy and plan early to mitigate against identified project risks by including quick and early feedback during the development process.

A diagram showing factors influencing quality engineering cycle in the project - strategy and planning, product users, communication, technology and continuous learning.

What have we learned?

One of the benefits of a brand-new project is that there is no legacy code or technical debt at the start (this changes pretty quickly though!). Mature products have gone through the growth pains. There are known unknowns and workarounds for known problems or pain points which the development teams, (and Test engineers in particular) come to know and understand fairly well.

The challenge however, with new projects, is that there are lots of unknowns with the new technology stack. As the project has been growing we have also been dealing with and learning from the scaling challenges such as pipeline issues from multiple deployments taking place at the same time, improving monitoring of traffic and website status errors, as well as optimising our stack’s performance as more product features have been built. Being able to identify such issues early on has been important. Manual testing by different team members helps with identifying such issues that may not be covered by the automated processes initially.

Solution: Continuously learn and iterate as issues are identified and fixed.

Conclusion

Building quality engineering into a shared repository requires similar considerations to that of single-team projects but on a bigger scale and with a wider focus. These considerations are; who is the product being made for and by whom; what are the product risks, and what is the test approach or plan to reduce the impact from these risks. The aim is to provide quick feedback and monitoring for regressions during the software development process. Test automation and tooling are important for facilitating this. Continuously learning about our product, (including from our product users) by regular communication, exploring, and working collaboratively. This has helped with iterating on our quality processes based on our findings and has been important for our quality engineering.

]]>
0
Building a WebAssembly Runtime for Ö÷²¥´óÐã iPlayer and enhanced audience experiences Mon, 01 Mar 2021 10:19:41 +0000 /blogs/internet/entries/39f42525-77db-43b0-81bb-70a0d5b1f062 /blogs/internet/entries/39f42525-77db-43b0-81bb-70a0d5b1f062 Juliette Carter Juliette Carter

At Ö÷²¥´óÐã Research & Development, we are investigating how we evolve our current multimedia applications to move beyond video by using object-based media (OBM). OBM allows us to develop future audience experiences which are immersive, interactive and personalised.

There is an ever-increasing number and range of audience devices capable of playing back OBM experiences. The challenge we now face is universal access - How can we get all members of the audience to enjoy OBM experiences on any device, and how do we do this sustainably and at minimal cost?

Our Render Engine Broadcasting (REB) project is investigating new technologies that will allow the Ö÷²¥´óÐã to deliver these OBM experiences at scale to all of our audiences, no matter what device they use. Our ultimate goal is to deliver real-time and fully rendered experiences on any device or platform and write the software to do it only once. We have been investigating the use of WebAssembly as a cross-platform technology for this.

What is WebAssembly?

(wasm) is a Universal Binary format designed as a sandboxed environment and a portable compilation target, which means that the same wasm module can run securely on multiple platforms. A number of strongly typed languages such as C/C++, Rust or AssemblyScript can compile to WebAssembly, making it language agnostic. This makes it an attractive option for adoption in the industry as it enables developers to use languages they already know to produce wasm binaries.

When WebAssembly was first developed a few years ago, its target platform was the web. The aim was to compile fast and efficient system-level code and have it run in the browser. Compute intensive applications, such as real-time interactive rendered graphics, could be run in a web browser at near-native performance. This also enabled some native applications to be ported to the web, increasing their reach and usage. These include , which renders 3D representations of satellite image in the browser, and , which now offers a WebApp to create and edit CAD drawings.

In the last couple of years, WebAssembly outside of the browser has been gaining traction. A number of native wasm runtimes have been developed, which has enabled the use of WebAssembly for microservices and server applications. In 2018, the website security company announced the use of WebAssembly on their edge workers, allowing users to deploy secure and fast serverless code compiled to wasm. And the edge cloud platform provider  offers new wasm-based edge computation using their native runtime Lucet.

The portability of WebAssembly across multiple platforms and its security model are the key reasons for Ö÷²¥´óÐã R&D’s interest in using this technology as a compilation target for media experiences. As a public service broadcaster, we need to deliver value to all of our audiences, regardless of the device they use. Where traditionally, a codebase for each target platform and a different team to maintain each codebase would be required, the use of WebAssembly potentially allows for a much more sustainable developer ecosystem. It enables media software applications to be created once, from a single codebase, compiled to WebAssembly and deployed on any client or server platform depending on the capabilities required. It also offers numerous advantages compared to previous multimedia or cross-platform technologies (such as Flash or Java Runtime Environment). Indeed, it is language agnostic, security-focused, has predictable performance, and works inside and outside the browser. WebAssembly is also an open standard, which encourages its adoption.

How have we used WebAssembly?

We wanted to demonstrate how we could use WebAssembly to deliver media experiences that can run on many target platforms built from a single codebase. To do that, we implemented an example media application written in C++, which we compile to WebAssembly, giving us a wasm module. We designed this application to look like a version of Ö÷²¥´óÐã iPlayer, allowing users to select content, watch video programmes, AND play OBM experiences. We call this application the Single Service Player (SSP).

An example of how object-based media experiences could appear within Ö÷²¥´óÐã iPlayer.

To run our SSP wasm module, we needed a wasm runtime. The SSP makes use of some low-level media functionality, which isn’t scoped by the WebAssembly specification. To enable wasm modules to make use of these low-level multimedia capabilities, they need to be implemented in the runtime and made available to the wasm module through a set of imports. Examples of such capabilities include:

  • Windowing and rendering — In most cases, a multimedia application will have some graphical elements to it, which requires things to be drawn in a window (such as video frames or a UI screen).
  • User inputs — An interactive multimedia experience expects user inputs, such as keyboard or mouse events.
  • Media encoding and decoding — To efficiently encode and decode media (such as video frames or audio packets), it is preferable to use the host’s hardware resources where possible.

As there is currently no WebAssembly runtime that offers these media capabilities, we've decided to create our own.

There are already some efforts in specifying ways a wasm module can talk to the host. proposes a set of standardised POSIX-like syscalls (the programmatic way in which a computer programme communicates with the host system) for libc functionality, mainly file handling and networking. These are called from the wasm module and implemented in the runtime.

We decided to use a similar approach to allow our SSP wasm module to communicate with the host, enabling it to have access to low-level media functionality. This involved identifying all the platform-specific media capabilities that could not be compiled to wasm and implementing them in the runtime. These capabilities were then made accessible to the wasm module through a set of platform-independent syscalls passed as imports.

This figure illustrates the whole process, from writing a media experience as software (such as the SSP) to running it as a wasm module on any device. The steps are detailed below.

The first step was to design the multimedia sys-call API behind which we would implement our cross-platform multimedia capabilities in the runtime. It needed careful consideration to ensure it was thread-safe and honoured the wasm security requirements around memory access. In the figure above, we use reb_decode_video() as an example syscall, which our SSP application can use to access low-level multimedia functionality, such as utilising the system’s hardware for video decoding.

Our SSP code was compiled to wasm using the clang compiler and the wasi-sdk toolchain, and the required syscalls are added as imports to the wasm module.

We then built the multimedia wasm runtime, consisting of two parts. The first one is the execution environment for wasm modules, which allows us to load and run a wasm module. For this, we embedded , a project based on , which generates the machine code for the target platform from the wasm binary.

The second part of our runtime is the implementation of the low-level multimedia functionality. For this, we created a cross-platform C++ library with input detection, networking, windowing, graphical rendering, and media decoding, which sits behind our carefully designed syscall APIs. We compiled our library for several target platforms, such as Linux, macOS, Windows, Raspberry Pi and Android. We also wrote some glue code to connect the two parts.

Where do we go from here?

A wasm runtime capable of executing multimedia applications opens a lot of possibilities, principally around flexible compute. Flexible compute allows us to run computationally demanding applications by dividing up the workload between available resources. These resources could be located locally (a laptop, games console or phone in your house), in the edge, or the cloud.

As we move towards delivering fully rendered real-time interactive experiences, the flexible compute approach becomes an attractive solution to the computational demands of such applications. We could, for example, consider segmenting a rendered frame into several tiles or objects, each of those rendered on a separate available compute resource. Many systems approach this problem by running specific compute tasks in containers across the available devices and platforms. We hope to use our work and accrued knowledge in developing the wasm multimedia runtime to investigate a viable alternative to the container approach for distributed media applications. We are looking into using wasm modules to perform secure and fast computation on any remote compute nodes.

Our runtime, capable of performing media services such as rendering and decoding or encoding of rendered video frames, can be used to display the final experience to the user on a client device and to execute the remote computational tasks as wasm modules. Using WebAssembly combined with a flexible compute approach, we hope to develop technology that allows the audience to access any future experience, regardless of their devices at home.

]]>
0